Well, I wanted to follow up to my previous postings. I am now going through Meroon's sources in a proper manner, instead of trying to get it to work while being ignorant of how it actually works.
I was pretty ignorant. It looks like Meroon purposefully keeps track of state during macro expansion so that it can do a lot of weight- lifting and optimizations during macro expansion.
I'm pretty impressed. I'm still trying to figure out how to port it to a module system with a syntactic tower (or at least 2 different environments for expansion and runtime). This will take time. But if I learn how Meroon works, I should be able to do it properly.
Sent from my iPhone
On Mar 3, 2010, at 4:33 PM, James Long longster@gmail.com wrote:
On Wed, Mar 3, 2010 at 4:15 PM, James Long longster@gmail.com wrote:
Basically, there's a macro (CHECK-AND-PROCESS-CLASS-DEFINITION) which modifies *class-number*, but *class-number* is also modified in several functions.
Actually, looks like I was wrong. From some testing I was doing, that looked to be the case, and I misread the code. Luckily, this isn't the case, so maybe it is just a matter of separating out the code into more explicit layers that we can load as modules.