Honestly, I feel this is an MXD bug. Florian might have a work around, but the real answer is for this odd behavior to be fixed.
On Tue, 25 Jan 2011 10:00:31 -0800 Buddy Burden <[email protected]> wrote: > Nick, > > > Bad news (well, not really bad news) next. You must take extra > > special care NOT to require/import/use the MXD class WHILE they are > > going through the compile stage. Basically you end up with a > > circular compile cycle of the class, through one of its use > > statements. The process is not "reentrant", so things get wonky > > (ie. half finished classes, etc). > > Ahhh ... that makes complete sense. Thanks for finding that! > > Now, my next question would be: isn't there some way we could _check_ > for that? Like, some bit of code that we can use to see if we're > entering a module for the second time and then throw an exception, or > at least spit out a warning, and that way this mistake can be easily > caught? I can _almost_ see in my head how to do it, but then ... not > quite. :) Anyone know of a way to do that off the top of their heads? > > > -- Buddy > -- Nicholas Perez XMPP/Email: [email protected] http://search.cpan.org/~nperez/ http://github.com/nperez
