Dan Sugalski <[EMAIL PROTECTED]> wrote: > Okay, aesthetics and making up for a flaw in the implementation of > how IMCC tracks opcodes and registers.
That flaw is caused by the assymmetry of opcodes, or by indirect register usage if opcodes like bare C<invoke>. But as that shall not be fixed now, lets' keep all these ugly hacks. > Neither of those are sufficient, individually or together. Your code is spilling ... ;) leo
