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
'undo' won't fire unless the block is a 'try' block in Rakudo #2678
Comments
From @masak<moritz> r: ENTER { say 1 } So far, so good. But: <moritz> r: UNDO { say 'undone' }; die 'foo' |
From @masakOn Tue Mar 20 02:03:58 2012, masak wrote:
Also: <moritz> n: do { UNDO say "undone"; die "foo" } |
@masak - Status changed from 'new' to 'open' |
From @diakopterOn Tue Mar 20 02:59:11 2012, masak wrote:
the first complaint now works, but the rest still don't. 19:22 <diakopter> r: UNDO { say 'undone' }; die 'foo' |
From @usev6Currently things are as follows: Moar get's all of this right: $ perl6-m -e 'UNDO { say "undone" }; die "foo"' Parrot has trouble with the first two commands (without block and "do" block), the other two run fine ("try" block and sub): $ perl6-p -e 'UNDO { say "undone" }; die "foo"' JVM has trouble with the second and third command ("do" block and "try" block), the other two run fine (without block and sub): $ perl6-j -e 'UNDO { say "undone" }; die "foo"' I'll add tests later (after this month's Rakudo release). |
1 similar comment
From @usev6Currently things are as follows: Moar get's all of this right: $ perl6-m -e 'UNDO { say "undone" }; die "foo"' Parrot has trouble with the first two commands (without block and "do" block), the other two run fine ("try" block and sub): $ perl6-p -e 'UNDO { say "undone" }; die "foo"' JVM has trouble with the second and third command ("do" block and "try" block), the other two run fine (without block and sub): $ perl6-j -e 'UNDO { say "undone" }; die "foo"' I'll add tests later (after this month's Rakudo release). |
From @usev6Tests added to S04-phasers/keep-undo.t with commit Raku/roast@933059b19f |
Migrated from rt.perl.org#111866 (status was 'open')
Searchable as RT111866$
The text was updated successfully, but these errors were encountered: