At 8:15 PM +0200 6/8/02, Jerome Vouillon wrote:
>On Sat, Jun 08, 2002 at 12:30:36PM -0400, Melvin Smith wrote:
>> Right now all it [ret] does is pop the return address from the global
>> interpreter control stack, but continuations, etc. will have their own
>> control stack, so they must restore the caller's before returning.
>
>Continuations never return. I don't see what other kind of functions
>may have their own stack.
Co-routines.
>[...]
>> 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".
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
