Re: [PATCH] Improved source properties and errors; => within case

[Noah Lavine]

Hello,

> Hmm.  I don't know if this is what you meant, but it occurs to me that
> as I've currently implemented them, both (cond (else (define x 5) x))
> and (case 1 (else (define x 5) x)) are allowed.  I'll have to make sure
> that those raise errors.  I guess that means I'll have to insert a '#f'
> like I did for local-eval.  Do you see a better way?

This makes me think that we should have a macro called
expression-context for putting things in expression context. It's not
that it's hard to insert #f, but that makes the source code less clear
unless people know why a random `#f' would appear in the code. What
does everyone else think?

Noah