At 12:26 PM 3/31/00 -0700, Joseph N. Hall wrote: >I'm not completely convinced that adding markers to the bytecode >stream to indicate when run-time interpolation is in effect is such >a bad idea. It might allow finer-grained control over interpolation >(with overload? or?) as well as more accurate Deparse, both of which >might turn out to be quite valuable. Just to resolve the problem >with the warning message, though, it's way too much work. An added field could be thrown into the opcodes, but the problem with that is the opcodes take even more memory than they used to. They keep getting bigger, and I think we're seeing slowdowns as it is from larger opcodes. (The bigger they are the fewer fit in a page or the processor cache, though we're pretty profligate with D-space as it is) It might be worth doing to opcodes what we do to SVs and make the opcode itself smaller with the 'extras' hanging off a secondary structure, but I don't know that it'd be a win overall. Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai dan@sidhe.org have teddy bears and even teddy bears get drunk