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,657 of 117,927   
   Ruvim to albert@spenarnc.xs4all.nl   
   Re: VALUE and TO implementation   
   01 Aug 24 22:37:35   
   
   From: ruvim.pinka@gmail.com   
      
   On 2024-08-01 16:01, albert@spenarnc.xs4all.nl wrote:   
   > In article ,   
   > Ruvim   wrote:   
   >> On 2024-07-31 13:41, mhx wrote:   
      
   >>> I'm not sure that you can use a buggy program to test for an ambiguous   
   >>> condition (looks like a top job for an eager lawyer). It would be   
   >>> much better if the anomaly can be shown with a valid program.   
   >>   
   >> When we want to apply a parsing word to a calculated string, we can use   
   >> "execute-parsing" (that can be defined in a standard way [1]). For a not   
   >> parsing "to", this standard-compliant method will fail.   
   >>   
   >>   
   >> A testcase:   
   >>   
   >>    : apply-compiling(to) ( sd.name -- )   
   >>      [: postpone to ;] execute-parsing   
   >>    ;   
   >   
   > This is foreseen. The standard stipulates that is not allowed   
   > to POSTPONE TO   
      
   Yes, I know. That is why I pointed to a standard-compliant   
   implementation for "postpone" [2].   
      
   In Forth-2012, you can define a new "postpone" using "get-order",   
   "traverse-wordlist", "name>compile", "compile," and "literal".  And   
   nothing in the standard prohibits applying this word to "to".   
      
   [2]   
      
      
      
   --   
   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