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
Segfault when putting YOU_ARE_HERE marker in a pblock in Rakudo #2940
Comments
From @masak<masak> r: say -> {YOU_ARE_HERE} |
From @cokeOn Sat Oct 20 01:47:14 2012, masak wrote:
FYI, Doesn't die in the REPL, but does on the command line. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @usev6This doesn't segfault any longer. Instead, an exception is thrown because method 'push' was not found: $ perl6-p -e 'say -> {YOU_ARE_HERE}' ## X::Method::NotFound $ perl6-j -e 'say -> {YOU_ARE_HERE}' ## X::Method::NotFound $ perl6-m -e 'say -> {YOU_ARE_HERE}' ## no typed exception here Is that reasonable? If so, this ticket can be closed IMHO. If not, the test I added to S04-blocks-and-statements/pointy.t with commit Raku/roast@eae2dc7bb7 should be modified. |
1 similar comment
From @usev6This doesn't segfault any longer. Instead, an exception is thrown because method 'push' was not found: $ perl6-p -e 'say -> {YOU_ARE_HERE}' ## X::Method::NotFound $ perl6-j -e 'say -> {YOU_ARE_HERE}' ## X::Method::NotFound $ perl6-m -e 'say -> {YOU_ARE_HERE}' ## no typed exception here Is that reasonable? If so, this ticket can be closed IMHO. If not, the test I added to S04-blocks-and-statements/pointy.t with commit Raku/roast@eae2dc7bb7 should be modified. |
From @FROGGSThe previous message about push happened in Perl6::Actions, because rakudo was surprised to spot a {YOU_ARE_HERE} outside of a setting. So that was not what we wanted. Now the behaviour is: $ perl6 -e 'say {YOU_ARE_HERE}' $ perl6 -e 'sub YOU_ARE_HERE { 42 }; say {YOU_ARE_HERE}' Patch: rakudo/rakudo@322d01b696 |
@FROGGS - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#115372 (status was 'resolved')
Searchable as RT115372$
The text was updated successfully, but these errors were encountered: