On Thursday, Dec 5, 2002, at 03:21 US/Pacific, Daniel Fagerstrom wrote:
Christopher Oliver wrote:
Ovidiu,
I think the below would also work, without changing system.js or any
Java code by using Rhino with continuations extended JavaScript
syntax:
[code snippet removed]
Interesting!! Could
Hi Daniel
Daniel Fagerstrom wrote:
Interesting!! Could you tell a litle bit more about how this construct
works? What corresponds to the try block in ordinary exception handling
There is no corresponding try block in this case. See section 2.2 in
http://marc.theaimsgroup.com/?l=xml-cocoon-de
Christopher Oliver wrote:
Ovidiu,
I think the below would also work, without changing system.js or any
Java code by using Rhino with continuations extended JavaScript syntax:
catch (continue) {
// The continuation I'm part of is about to be restored
// code to handle that goes here.
}
catch (
On Wednesday, Dec 4, 2002, at 22:50 US/Pacific, Christopher Oliver
wrote:
Ovidiu,
I think the below would also work, without changing system.js or any
Java code by using Rhino with continuations extended JavaScript > syntax:
catch (continue) {
// The continuation I'm part of is about to be
Ovidiu,
I think the below would also work, without changing system.js or any
Java code by using Rhino with continuations extended JavaScript syntax:
catch (continue) {
// The continuation I'm part of is about to be restored
// code to handle that goes here.
}
catch (break) {
// I'm about
Hi Torsten,
[Cc-ed Daniel and [EMAIL PROTECTED] as it might be an interesting
topic as well]
Sorry it took so long for me to find some more time to think about this
problem.
I believe the use case you mentioned is certainly a valid one, and a
very important one. One way to solve this problem
