From: anton@mips.complang.tuwien.ac.at   
      
   peter  writes:   
   >On Sat, 20 Sep 2025 17:57:30 GMT   
   >anton@mips.complang.tuwien.ac.at (Anton Ertl) wrote:   
   >   
   >> peter  writes:   
   >> >It has been usefull when testing new recognizers.   
   >>   
   >> I have been doing that by directly calling the recognizer.  E.g.   
   >>   
   >> s" `dup" rec-tick . .   
   >> s" `fkjfd" rec-tick .   
   >> s" dup" rec-tick .   
   >   
   >I do that also.   
   >A bit difficult with the string recognizer!   
      
   In theory:   
      
   s\" \"abc\"" rec-string scan-translate-string = . type \ -1 "abc"   
      
   Trying to pass the result of the REC-STRING to INTERPRETING has   
   revealed interesting restrictions in Gforth's implementation of the   
   results of REC-STRING:   
      
   s\" \"abc\"" rec-string interpreting   
   *the terminal*:26:25: error: Scanned string not in input buffer   
      
   parse-name "abc" rec-string scan-translate-string = . type \ -1 "abc"   
   parse-name "abc" rec-string interpreting   
   *the terminal*:29:29: error: Invalid memory address   
   parse-name "abc" rec-string >>>interpreting<<<   
      
   - 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 2025 CFP: http://www.euroforth.org/ef25/cfp.html   
   EuroForth 2025 registration: https://euro.theforth.net/   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)