Sat Apr 26 09:15:22 EDT 2008

giving up?

maybe time to see if this can be installed in the compile state. what
i need there is a stack to trace the dynamic context of macros. it
feels wrong though, to not have this coincide with the dynamic call
stack.. but maybe it is becase i'm messing that up, that i need it
stored explicitly somewhere else?

the problem is: what if macros don't exit? am i allowed to jump
outside of context? does it need dynamic-wind? hmm.. if a macro
doesn't exit, it probably also doesn't produce code.

on the other hand: having the mdyn stack available might be interesting.