Related articles |
---|
[2 earlier articles] |
Re: Optimizing stack access for a stack based VM blog@rivadpm.com (Alex McDonald) (2007-09-13) |
Re: Optimizing stack access for a stack based VM lkrupp@pssw.com (Louis Krupp) (2007-09-13) |
Re: Optimizing stack access for a stack based VM DrDiettrich1@aol.com (Hans-Peter Diettrich) (2007-09-13) |
Re: Optimizing stack access for a stack based VM DrDiettrich1@aol.com (Hans-Peter Diettrich) (2007-09-13) |
Re: Optimizing stack access for a stack based VM jvorbrueggen@not-mediasec.de (=?ISO-8859-1?Q?Jan_Vorbr=FCggen?=) (2007-09-14) |
Re: Optimizing stack access for a stack based VM blog@rivadpm.com (Alex McDonald) (2007-09-14) |
Re: Optimizing stack access for a stack based VM kenney@cix.compulink.co.uk (2007-09-14) |
Re: Optimizing stack access for a stack based VM jeffrey.kenton@comcast.net (Jeff Kenton) (2007-09-16) |
Re: Optimizing stack access for a stack based VM dot@dotat.at (Tony Finch) (2007-09-16) |
Re: Optimizing stack access for a stack based VM anton@mips.complang.tuwien.ac.at (2007-10-01) |
From: | kenney@cix.compulink.co.uk |
Newsgroups: | comp.compilers |
Date: | Fri, 14 Sep 2007 17:48:22 -0500 |
Organization: | Compilers Central |
References: | 07-09-049 |
Keywords: | storage |
Posted-Date: | 15 Sep 2007 15:14:15 EDT |
DrDiettrich1@aol.com (Hans-Peter Diettrich) wrote:
> Forth has no local variables (for recursive calls),
Local variables are in the Forth Standard, optional word set IIRC.
Ken Young
Return to the
comp.compilers page.
Search the
comp.compilers archives again.