From: no.email@nospam.invalid   
      
   anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:   
   > "Might"?  If you have a concrete target with small RAM (say, one of   
   > the Mecrisp targets),   
      
   I was thinking Fuzix (fuzix.org) doesn't have a Roff or a Forth that I   
   know of, but it might be an interesting target.  It runs on the   
   Raspberry Pi Pico (256K of ram and 2MB of flash) which is enough for   
   most Forth purposes.   
      
   > If you have a machine where you run a WYSIWYG editor, you also have   
   > enough RAM for keeping one line (and probably the whole text).   
      
   The idea is to format files that came from other people and other   
   machines.  Though that's maybe kind of dumb because nobody cares about   
   Roff any more.  It interests me because I used to use it for my school   
   papers.  IDK if I have any of those files around any more though.   
      
   > READ-LINE and the case where u1=line length have been discussed   
   > several times, so apparently it's not so clear to some how a system   
   > should behave,   
      
   That sounds like a deficiency in the standard, but anyway yes, there are   
   ways to get around it.   
      
   > Alternatively, you could go for using READ-LINE.  In that case I would   
   > treat too-long lines as errors   
      
   Yeah I think that's the sanest approach.  Another idea is to abandon   
   Roff syntax altogether, and go for an HTML subset or similar.  I hate   
   Markdown but that's yet another possibility.   
      
   > That means going through INCLUDE, EVALUATE, EXECUTE-PARSING, or   
   > EXECUTE-PARSING-FILE at some point.   
      
   I see.  That can still can be ok of course.  It's in the Forth spirit, I   
   think, to just do something hacky to detect whether the token read by   
   PARSE-NAME is at the beginning of a line.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)