At 02:36 PM 6/8/2002 -0400, Dan Sugalski wrote: >At 8:15 PM +0200 6/8/02, Jerome Vouillon wrote: >>On Sat, Jun 08, 2002 at 12:30:36PM -0400, Melvin Smith wrote: >>> The Java VM does this by popping values off of the local stack, and >>> onto the callee's stack upon return. >> >>I think this is a design mistake of the Java VM. It would have been >>more efficient to keep the local variables on the stack. > >Yeah, that's too much work for me. I'd rather do something simpler, even >if that boils down to "we return a single ParrotList with all the return >values in it, stuck in P0".
Thats fine by me. I was giving a real world example that we could relate to, not saying it was optimum. Implementing Parrot is new ground for me; I've worked on a VM before, but it wasn't capable of things like closures, continuations, etc. I feel like I'd be more productive if people would provide numbers, samples or some sort of reference for what they are proposing as an alternative to how I did it, so I can understand why the current way is less efficient. Otherwise, when someone says, "Thats not efficient." and leaves off, I have to go research and figure out why for myself. -Melvin
