hlovatt wrote: > Is it really necessary to have a new feature. I would of thought a > convention that you don't catch something derived from Jump was > sufficient. Much like you are highly advised not to catch something > derived from Error at the moment. I say this because inner classes > give sufficient power to make non-local jumps fast at present, e.g.:
The problem is that there's already code out there that catches Exception or Throwable, which will break any language implementation using RuntimeException subclasses to do non-local flow control. Scala opted to go with Error subclasses, but even here there's the possibility someone could be catching Error for other reasons. The fact that Jump would be new and that there would be no other valid reason for catching it other than intercepting non-local flow control is exactly the point. We're not overloading an existing feature in ways incompatible with current usage patterns. We're accepting that non-local flow control is a fact of life for many language implementations, and that a first-class construct is needed. - 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 -~----------~----~----~----~------~----~------~--~---
