Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #30043
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: C-to-stack, and locals versus global stacks? |
| Date | 2014-05-01 12:12 -0700 |
| Organization | Nightsong/Fort GNOX |
| Message-ID | <7xeh0dl3e2.fsf@ruckus.brouhaha.com> (permalink) |
| References | <ea3af6a9-d126-40bf-b597-48ed49c0a420@googlegroups.com> |
jacko <jackokring@gmail.com> writes: > "However, to achieve this the virtual machine design has local > variable support." - This in an incorrect fact. As I remember, the code generated by that compiler (if it's the one I remember) made extensive use of PICK or equivalent, to reach deeply into the stack interior. I figured that was what was meant by "locals".
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
C-to-stack, and locals versus global stacks? jacko <jackokring@gmail.com> - 2014-05-01 10:46 -0700 Re: C-to-stack, and locals versus global stacks? Paul Rubin <no.email@nospam.invalid> - 2014-05-01 12:12 -0700 Re: C-to-stack, and locals versus global stacks? Stefan Mauerhofer <smauerhofer@androsoft.ch> - 2014-05-01 21:25 -0700
csiph-web