New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Null PMC access when last statement of a sub is empty or a CATCH block #537
Comments
From @masak<ruoso> rakudo: sub foo { fail 'foo'; }; sub bar { foo(); 2; CATCH { |
From @masak<ruoso> rakudo: sub foo { fail }; sub bar { foo(); 2; CATCH { 1; } }; |
@masak - Status changed from 'new' to 'open' |
From @bacekOn Fri Dec 26 05:05:27 2008, masak wrote:
Actual summary should be "CATCH blocks eats return values from subs". $ ../../parrot perl6.pbc -e 'sub bar { 1; CATCH { } }; say bar()' -- |
From @bacekOn Sat Feb 14 21:22:35 2009, bacek wrote:
Even worse... Problem is in empty statement list. -- |
From @kylehaThis is an automatically generated mail to inform you that tests are now available in b/t/spec/S06-advanced_subroutine_features/return.t |
From @cokeOn Sat Feb 14 21:33:06 2009, bacek wrote:
This particular item now generates: 00:51 <[Coke]> rakudo: sub foo { 1;; }; say foo (but everything else still NPEs) -- |
From @cokeOn Sat Feb 14 21:22:35 2009, bacek wrote:
Note that it seems to be the implicit return that's a problem: 01:00 <[Coke]> rakudo: sub bar { return 1; CATCH { } }; say bar() -- |
From @moritzThe Null PMC Access is now gone, closing the ticket. |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#61732 (status was 'resolved')
Searchable as RT61732$
The text was updated successfully, but these errors were encountered: