From: do-not-use@swldwa.uk   
      
   On 04/10/2025 17:53, Anton Ertl wrote:   
   > Gerry Jackson  writes:   
   >> I would suggest that you start with mini-oof & xmini_oof to see how they   
   >> can be used as these are much simpler than Anton's object.fs which is a   
   >> more complete OO system. Once you see how mini_oof can be used in LexGen   
   >> and/or Krishna's epr-sim.4th you can move on to object.fs.   
   >   
   > But given that so many people found mini-oof good enough to work with   
   > it, or to base their own extension on it, maybe the "more complete"   
   > part of object.fs as actually not needed that often.   
   >   
   > One thing that Bernd Paysan found missing in mini-oof is THIS, i.e., a   
   > handle for the current object.  He added it into (the Gforth-specific)   
   > mini-oof2.  Interestingly, mini-oof is based on the internal OO system   
   > of Gray , but that   
   > system has a THIS.  So the removal of THIS in mini-oof probably was   
   > one simplification too far.   
   >   
   > - anton   
      
   I agree about THIS, if I'd thought of it I would probably have added it.   
   Also if mini-oof2 had been available at the time I would have used that.   
      
   I suppose mini-oof is a good example of the Forth philosophy: a few   
   lines of code giving the basics of OO yet powerful, easily extendable to   
   add more features, easy to understand (and abuse if you need to!). And   
   like Forth itself a careless mistake can easily crash the system.   
      
   --   
   Gerry   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)