With more and more discussion about closures and non-local flow control
and various stack-manipulating events becoming part and parcel on the
JVM, it seems like we need to introduce a new exception type.
There's two reasons for this:
- catch (Throwable t) or catch (Error e) would break current non-local
flow control mechanisms based on exceptions or errors
- some of you whiners don't like us using exceptions or errors for
non-local flow control
So, what about a new type of exception-like feature: Jump
public class Jump {}
public class NonLocalReturn < Jump {
Object returnValue;
}
Jumps would not be catchable as either errors or throwables, though they
would still trigger finally blocks. Because they'd be a new class of
exception-like feature, no existing code would be incorrectly trying to
catch them. And they're explicitly stated to be used for these sorts of
"jump" events.
Thoughts?
- Charlie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "JVM
Languages" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/jvm-languages?hl=en
-~----------~----~----~----~------~----~------~--~---
