Re: What's the status of modules and macros?

[Rob Browning]

Marius Vollmer <address@hidden> writes:

> Ahh, because it has not been registered with `assert-defmacro?!' (what
> a strange name).  It can't be since it uses the ENV parameter of the
> procedure->memoizing-macro interface (to know whether it is at
> top-level).

So does anyone have any idea how many of the macros that will have to
be special cased in the compiler there are?  It makes sense that
eval-case would have to be a special case (functionally speaking), but
are there others, or should sc-expand and macroexpand expand pretty
much everything else?

Thanks

-- 
Rob Browning <address@hidden> PGP=E80E0D04F521A094 532B97F5D64E3930