EMFORTH stacks.


As well as the usual data and return stacks SAM7 EMforth has a bunch of others.

It has...
An object stack.
A message stack.
A vocabulary stack.
A register stack - for the assembler.
An auxiliary stack - for the assembler to remember immediates which need to be done in a lookup table.

Data, return, object and message use registers as stack pointers for speed.

In future stacks may be defined as objects. This is hard to do for the kernel but easy for higher level code.

There would be one or more class of "Stack" and the individual stack would be instances of that class.

It would avoid have lots of similar words defined for every stack.

Now I have RP! DP! OP! MP! AUX! VP! to reset the various stack.

If they were instances of a class you'd have something like this.

reset AUXstack, reset Vstack etc. where "reset" is a message and AUXstack etc are instance of the class Stack.
The same chuck of code does the work for all stacks so space is saved.
You could still define the old style words by doing something like..
: VP!
   reset Vstack 

Created by System Administrator. Last Modification: Saturday 26 of January, 2008 21:53:15 AEDT by eddie.

Main Index

Switch Theme


eddie, 15:29 AEDT, Wed 02 of Jan, 2019: database failed. Reverted to an old version.
System Administrator, 20:46 AEST, Sat 06 of Aug, 2016: There will be some downtime tomorrow for an upgrade to 15.2
eddie, 23:33 AEDT, Mon 05 of Oct, 2015: This website is now served from Brisbane - in a Binarylane cloud.
System Administrator, 16:07 AEDT, Wed 06 of Mar, 2013: More f'n spam. No more anon posting from now on.
Anonymous, 18:44 AEDT, Mon 04 of Mar, 2013: deleted

Last-Visited Pages

Online Users

12 online users