From: anton@mips.complang.tuwien.ac.at   
      
   albert@spenarnc.xs4all.nl writes:   
   >In article <2024May5.170709@mips.complang.tuwien.ac.at>,   
   >Anton Ertl  wrote:   
   >>dxf  writes:   
   >>>On 4/05/2024 3:04 am, Anton Ertl wrote:   
   >>>> dxf  writes:   
   >>[...]   
   >>>> It means: Gforth does not provide (D.) and does not have factors that   
   >>>> correspond to (D.) or (.).  If it had such factors, you would have to   
   >>>> use them in the following way:   
   >>>>   
   >>>> ( d ) (D.)  ( do something with the string, and when you are done:) #>>   
   >>>   
   >>>Standard Forth makes no such instruction.   
   >>   
   >>Of course not, because standard Forth has no word (D.).   
   >   
   >Indeed, surprisingly, but every Forth made in the Netherlands   
   >apparently has at least (D.R) that was already present in figForth or   
   >an equivalent to (D.).   
      
   What every Forth made in the Netherlands has is not relevant for the   
   issue at hand.  fig-Forth does not have (D.R); see, e.g.,   
   .   
      
   >In my experience those words that leave a string and doesnot TYPE immediately   
   >are pretty essential.   
      
      
   >The fact that #> may refer to a static buffer   
   >cannot be concealed anyway.   
      
   The HOLD buffer has not been static in traditional Forth, and some of   
   the restrictions on its usage stem from there.  Moreover, in Gforth #>   
   refers to the top of a stack of HOLD buffers (managed with <<# and   
   #>>).   
      
   - anton   
   --   
   M. Anton Ertl  http://www.complang.tuwien.ac.at/anton/home.html   
   comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html   
        New standard: https://forth-standard.org/   
      EuroForth 2023: https://euro.theforth.net/2023   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)