[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Scheme-reports] exception handling

Per Bothner scripsit:

> A typo in draft-3:
>   (merror message obj ...)
>    Message should be a string.  raise on a new created ...
> The sentence starting with "raise" is missing a verb.  Perhaps "Invokes"?

Fixed on trunk.

> The example listed after error does not make use of error.

It belongs with raise-continuable.  Editorial ticket filed.

> More fundamentally, the paradigm seems very awkward.  The classic
> exception-handling idiom in a language with non-continuable exception
> seems to require call-cc, which is rather painful:

See "guard" (4.2.7).  This unwinds the dynamic state while executing the
appropriate catch clause and then falls out the bottom of the guard.  But
if no catch clause applies, the state is rewound (except for the current
handler) and the next handler is tried.

John Cowan  cowan@x   http://ccil.org/~cowan
Assent may be registered by a signature, a handshake, or a click of a computer
mouse transmitted across the invisible ether of the Internet. Formality
is not a requisite; any sign, symbol or action, or even willful inaction,
as long as it is unequivocally referable to the promise, may create a contract.
       --Specht v. Netscape

Scheme-reports mailing list