Re: pdd23: closure vs. continuation

2006-07-01 Thread Allison Randal

Chip Salzenberg wrote:


Allison, if you give me the OK, I'll recast pdd23 in the alternative way I
had in mind, where:

 * exception handlers are closures,

 * the closures are called _inside_ the dynamic scope where the throw occurred,

 * a closure returning without executing Ccaught implies I didn't handle
   it, try the next handler,
 therefore obviating the rethrow opcode.


Thumbs up.


PS: caught will perhaps be better renamed handled.


Agreed.

Allison


pdd23: closure vs. continuation

2006-06-30 Thread Chip Salzenberg
Just before I committed pdd23 as it currently is, I asked Audrey whether it
was better to make handlers continuations or closures.  She said it was not
important, and to choose whichever is faster.  However, I think I erred in
choosing continuations.

In the continuation model (as in pdd23 at present), the exception handler
runs _outside_ the dynamic scope where the exception occurred, which means
that dynamically scoped state required to describe, diagnose, or fix the
exception is not available.

Oops.

Allison, if you give me the OK, I'll recast pdd23 in the alternative way I
had in mind, where:

 * exception handlers are closures,

 * the closures are called _inside_ the dynamic scope where the throw occurred,

 * a closure returning without executing Ccaught implies I didn't handle
   it, try the next handler,
 therefore obviating the rethrow opcode.

PS: caught will perhaps be better renamed handled.
-- 
Chip Salzenberg [EMAIL PROTECTED]