On 8/15/07, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > This optimization reaches likely back to times, when the opcode engine was > designed. It's saving one interpreter push statement [1] per JIT calling one > external function, and I've always thought of it as a very cool (and valid) > thingy, when I first realized, why the interpreter is the second argument in > opcode functions ;) > aha! now i know why interp is the second arg for opcode functions. that always bothered me, and i couldn't figure out why it was against the norm. leo++ for bringing it up. now, to make sure it's documented somewhere....
~jerry
