From: Matthias T. <mt...@we...> - 2013-01-13 18:10:15
|
Hi, > Thanks Matthias for clarifying those user deferred words. Well, at least I tried my best ;) I summarized the status quo under http://amforth.sourceforge.net/recipes/deferred-words.html > What I also found confusing is the mention of Udefer@ and Udefer! on > <http://amforth.sourceforge.net/words/> which are not really accessible > to the high level (i.e. to forth). They are factors that are used by the respective defining words. They should never be called directly (that they are exposed under http://amforth.sourceforge.net/words/ is simply a bug in the tool, that generates these pages.. > > I guess that in old Amforth versions the programmer had to be conscious > how to read deferred words -- Rdefer@, Udefer@, Edefer@ or simply defer@ > from the program memory. No, deferred word were already created with the generic defer@/defer!/is in mind. Only the defer itself is special (see recipe) It's all not that simple.. Matthias |