At 02:50 PM 6/1/2002 -0400, Dan Sugalski wrote: >At 2:17 PM -0400 6/1/02, Melvin Smith wrote: >>Now there are a dozen ways to handle this. Using flags, keeping args on the >>stack until return, yada yada yada... >>Since extensions are supposed to be isolated from the interpreter >>internals, I'm just fine with them not knowing about stacks, registers, >>and suchlike things. We
When you say, "not knowing about stacks" does that you mean you don't want the idiom I had as an example of: int ival = PXS_shifti(interp); ? I thought it was Perl-ish. Would you rather say PXS_arg(0) or something? >> can work some thunking magic here to make it work out. Yeah, it'll be a >> little slower, but that's fine. If people want fast they can write >> opcode functions and have to deal with all the gory details themselves. Which brings up another question. When do we know what goes in as an op and what goes in as a native API? From the little knowledge I have, I think JVM does all their "system" type stuff as JNI native classes. -Melvin
