... actually coding \ than the normal/bright text examples I've seen. \ \ This will let me ... in it's current \ incarnation using the EDO structure package for the data references. \ ...1 constant Plane1 2 constant Plane2 0 [if] \ ---[ EDO Version of animation sequence ]--------------------------- \ Define the animation control structure \ [var] indicates that this value changes during ...

...: :: ( class "name" -- ) ' body @ + @ compile, ; \\ // \\ // \\ // \\ // \\ // \\ // \\ // \\ // \\ // \\ // \\ // \\ // ---[ An Example ]------ Nothing can be more confusing than a good...time with it. As far as Forth Structure packages in general go, they all have ... of the other Structure packages any more or less than the EDO system, but I'm used to ...

... been able to figure out - I haven't spent much time with it. As far as Forth Structure packages in general go, they all have something in common in comparision to what is available in Pascal and ..., for myself, I don't like or dislike any of the other Structure packages any more or less than the EDO system, but I'm used to using this one at this time. If...

...Man's" word set. \ It is really a bare-bones implementation and does...: S{ ( -- 0 ) 0 ; \ === Defines a structure component === : :: ( offset object-definition -- offset )...the first byte of the sub-structure \ we want to access \ \ Palette-OBJ...\ not going to give an example of here. \ \ So to access the... create the array using the EDO \ structure words. It is entirely ...

... to a very large number of systems. If we must have a fetish over minimalism, then let me present the following that actually works, unlike mini-oof which is seriously flawed. See example at end. Note that there is plenty of room for feature expansion of this code. mini-oof can only be seriously flawed by being not portable. Please explain. ***BEGIN CODE \ tested on ...

... over minimalism, then let me present the following that actually works, unlike mini-oof which is seriously flawed. That's a bit strong given that the example in your previous message misused mini-oof or do you have another reason for this statement. Apparently you don't see the required manual vocabulary management for different classes as a serious ...

... a fetish over minimalism, then let me present the following that actually works, unlike mini-oof which is seriously flawed. That's a bit strong given that the example in your previous message misused mini-oof or do you have another reason for this statement. Apparently you don't see the required manual vocabulary management for different classes as a serious problem and ...

Doug Hoffman wrote: <snip> If we must have a fetish over minimalism, then let me present the following that actually works, unlike mini-oof which is seriously flawed. That's a bit strong given that the example in your previous message misused mini-oof or do you have another reason for this statement. Gerry

.... ---[ Mini-OOF problem in gforth ]------ Worse, after loading Mini-OOF and the provided example using gforth, I tried the following: object class cell var z method draw ... bar s" fat bar" bar init 1 bar y ! bar draw ---[ moof-ex2.f -- your example ]--- \ namespace test case object class cell var z method draw end-class testClass :noname ( o ...

... will not compile on Carbon MacForth. I have no idea why. Everything else ANS-compatible I've tried seems to have no problems on CMF. Worse, after loading Mini-OOF and the provided example using gforth, I tried the following: object class cell var z method draw end-class testClass :noname ( o -- ) z @ . ." DRAW!" ; testClass defines draw...