From: muta...@gmail.com   
      
   On Wednesday, October 13, 2021 at 5:49:35 AM UTC+11, Scott Lurndal wrote:   
      
   > "The character set for all NNTP commands is UTF-8 [RFC3629]. Commands   
   > in NNTP MUST consist of a keyword, which MAY be followed by one or   
   > more arguments. A CRLF pair MUST terminate all commands.   
      
   I'll be doing all that, given that I'm only interested in   
   ASCII messages from eternal-september.   
      
   > >This will get the 0200 line that eternal-september puts out.   
      
   > The first response you'll get from most NNTP servers   
   > will be a request for authentication after you send   
   > MODE READER. That will be a response code of "480"   
   > (see appendix C).   
      
   Ok, the important thing is that the protocol lets me know   
   when I need to switch to/from reading/writing. Because   
   I want to write C90 code.   
      
   > >There will be an fseek SEEK_CUR 0 as required by the C90   
   > >standard prior to then doing a write,   
      
   > Where, exactly, does C90 require an fseek on a non-seekable   
   > file like a UART?   
      
   7.9.5.3   
      
   When a file is opened with update mode ('+' as the second or third character   
   in the above   
   Iist of mode argument values), both input and output may be performed on the   
   associated stream.   
   However, output may not be directly followed by input without an intervening   
   call to the   
   fflush function or to a file positioning function (fseek, fsetpos, or rewind),   
   and input   
   may not be directly followed by output without an intervening call to a file   
   positioning function,   
   unless the input operation encounters end-of-file.   
      
      
   There is no exception for "unless the stream is associated   
   with a UART, of course!".   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)