From: mutazilah@gmail.com   
      
   On 21/02/24 22:20, Richard Kettlewell wrote:   
   > Paul Edwards  writes:   
   >> On 21/02/24 20:25, Richard Kettlewell wrote:   
   >>> Standard C doesn’t have open(), read() or write() either,   
   >>   
   >> Indeed - because PDPCLIB's implementation of fopen()   
   >> needs to do the open syscall (INT 80H EAX = 5H).   
   >>   
   >> fopen already knows whether the file is being opened as text or   
   >> binary, and I don't want that information lost when I do that   
   >> interrupt above.  Even though Linux (currently, and very likely   
   >> forever) won't use it, PDOS/386 has a use for it (in the short term).   
   >>   
   >>> but you seem to want to modify the behaviour of those.   
   >>   
   >> I don't think that is an accurate statement.   
   >>   
   >> What behavior, where?   
   >   
   > You’ve been talking about doing translation _somewhere_,   
      
   Yes - when run under PDOS/386.   
      
   Currently the only Linux ELF program that runs   
   under PDOS/386 is a "hello world".   
      
   And I don't think anyone cares if I change the   
   behavior of that.   
      
   And that program doesn't even use open(), so is   
   not subject to my proposed change.   
      
   I guess I am talking about changing FUTURE   
   behavior of a FUTURE program.   
      
   But I thought you were implying I was going   
   to break something.   
      
   > and cited   
   > Cygwin as an example in your first posting, and have been consistently   
   > using the flag name from Cygwin. Cygwin’s O_TEXT causes read() and   
   > write() to translate between newline conventions, so if you meant   
   > something else then it was a confusing decision to use Cygwin as an   
   > example.   
      
   Cygwin is a correct example, I believe.   
      
   And Cygwin doesn't change the behavior of Linux ELF   
   executables either.   
      
   Nor does it change the behavior of existing POSIX   
   source code.   
      
   > If, in fact, you don’t want to add translation to read() and write()   
      
   I do.   
      
   I guess it's just a semantic debate as to whether   
   this constitutes a change in behavior.   
      
   All existing Linux ELF programs are unchanged.   
      
   Even new Linux ELF programs won't change when   
   run under Linux.   
      
   The flag only takes effect when the ELF is run   
   on a competing system.   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)