Skip to content
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

return statements in CATCH blocks cause infinite regress in Rakudo #718

Closed
p6rt opened this issue Feb 24, 2009 · 5 comments
Closed

return statements in CATCH blocks cause infinite regress in Rakudo #718

p6rt opened this issue Feb 24, 2009 · 5 comments

Comments

@p6rt
Copy link

p6rt commented Feb 24, 2009

Migrated from rt.perl.org#63430 (status was 'resolved')

Searchable as RT63430$

@p6rt
Copy link
Author

p6rt commented Feb 24, 2009

From @masak

<masak> rakudo​: sub s { try { return 1; CATCH { return 2 } } }; say s
<masak> OK, seems like the try block catches return exceptions.
<p6eval> rakudo 2a9382​: No output (you need to produce output to STDOUT)
* masak submits rakudobug

@p6rt
Copy link
Author

p6rt commented Jul 24, 2009

From @kyleha

This is an automatically generated mail to inform you that tests are now available in b/t/spec/S04-statements/try.t

@p6rt
Copy link
Author

p6rt commented Jul 24, 2009

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Oct 10, 2011

From @coke

On Mon Feb 23 22​:36​:18 2009, masak wrote​:

<masak> rakudo​: sub s { try { return 1; CATCH { return 2 } } }; say s
<masak> OK, seems like the try block catches return exceptions.
<p6eval> rakudo 2a9382​: No output (you need to produce output to STDOUT)
* masak submits rakudobug

19​:27 < [Coke]> rakudo​: sub s { try { return 1; CATCH { return 2 } } }; say s
19​:27 <+p6eval> rakudo 38907e​: OUTPUT«1␤»

Fixed, already has tests.

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Oct 10, 2011

@coke - Status changed from 'open' to 'resolved'

@p6rt p6rt closed this as completed Oct 10, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant