home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.lang.forth      Forth programmers eat a lot of Bratwurst      117,927 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 116,664 of 117,927   
   Ruvim to dxf   
   Re: VALUE and TO implementation   
   05 Aug 24 20:08:58   
   
   From: ruvim.pinka@gmail.com   
      
   On 2024-08-05 19:07, dxf wrote:   
   > On 5/08/2024 10:38 pm, mhx wrote:   
   >> On Mon, 5 Aug 2024 12:26:26 +0000, dxf wrote:   
   >>   
   >>> On 4/08/2024 5:17 pm, mhx wrote:   
   >>>>> However, as I showed earlier, a parsing "TO" has several advantages over   
   >>>>> a non-parsing "TO".   
   >>>>   
   >>>> Am I the only one that thinks parsing words are an incredible nuisance?   
   >>>   
   >>> Don't know but to this day Mitch Bradley (ANS, Open Firmware) still uses   
   >>> parsing words to interpret hex, double, float numbers.   
   >>   
   >> "de gustibus non disputandum est."   
   >>   
   >>> He also uses state-smart words.   
   >>   
   >> Show me a Forther *without* strong opinions *and* unfathomable   
   >> inconsistencies.   
   >   
   > I'm more interested in knowing how parsing words can be a nuisance?  Do they   
   > possess a life of their own?   
      
   > We've been told state-smart words are evil.   
      
   The only reason for that evil is that `POSTPONE` in a classic   
   implementation behaves incorrectly for them.   
      
   See "About POSTPONE semantics in edge cases"   
      
      
   Nobody have pointed out any logical error in my reasoning.   
      
      
   --   
   Ruvim   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca