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.