[e-lang] Trinary-define syntax, and ejector behavior (was Re: Atomic expansion of MatchBindExpr ...)

[Mark Miller]

On 5/15/06, Kevin Reid <kpreid at mac.com> wrote:
> (E-on-Java throws the match failure problem with a note in the stack
> trace. E-on-CL throws a new exception reporting that the 'ejector'
> returned. MarkM, have we discussed this behavior?

Not that I remember.

> Is there a reason E-on-CL's is inappropriate?)

Since the payloads of thrown exceptions are diagnostic info to help
humans diagnose and repair problems, it would be good to include some
indication of the original match failure. So long as such diagnostic
info is included, E-on-CL's way seems fine. Could you post a bit of
updoc script demonstrating the relevant behavior? Thanks.

-- 
Text by me above is hereby placed in the public domain

    Cheers,
    --MarkM