Bruce Rennie wrote:
Has there been any attempt to restructure the UnIcon/Icon virtual
machine so that there are separate data and processor(return) stacks?
The model that I'm comparing to is the FORTH virtual machine - data
stack and return stack.
..
What I am interested in is whether any research has been done into the
separation of the stack and what problems were found in doing so. It
seems to me that some of the difficulties in the VM implementation would
be alleviated by doing the separation, possibly allowing co-expressions
to become full fledged processes/threads within the VM - just a thought.
Hi Bruce,
This is an intriguing idea, but not one I fully understand. Can you
give a simple example of what is meant by separating the data and
return stacks? I'm guessing that this means keeping the control flow
information (return points, generator resumption information, etc.)
on a stack and allocating parameter/local variable storage blocks in
the heap. Is that at all close? I'm not sure I see the advantage
of using two separate stacks instead of a stack + heap storage
blocks.
Thanks!
Steve
(others: is this the type of discussion that should be moved to the
'other' Unicon mailing list?)
--
--
Steve Wampler [EMAIL PROTECTED]
The gods that smiled upon your birth are laughing now. -- fortune cookie
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Unicon-group mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unicon-group
