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

No argument Kernel.raise must raise current exception within rescue clause #290

Open
junjis0203 opened this Issue Jun 15, 2012 · 2 comments

Comments

Projects
None yet
3 participants
@junjis0203
Contributor

junjis0203 commented Jun 15, 2012

I tried to fix this problem, but, I couldn't.
Because there is no way to determine whether within rescue clause or not.
Entering rescue clause can understand, but leaving rescue clause can't understand.

@carsonmcdonald

This comment has been minimized.

Member

carsonmcdonald commented Feb 10, 2013

I think @matz or someone with access to the ISO spec needs to clear this one up. The comment in the code says that raise with no arguments is supposed to raise a RuntimeException with no further information about location causing a different behavior.

@matz

This comment has been minimized.

Member

matz commented Feb 11, 2013

ISO describes this behavior. But I consider this as a limitation of mruby.

kou added a commit to groonga/groonga that referenced this issue Aug 15, 2018

mruby: fix a bug that real error is hidden
mruby doesn't support error propagation by no argument raise.

mruby/mruby#290
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment