🚀 go-pugleaf

In article <l85skiINN9vb@levelland.cs.utexas.edu> phil@cs.utexas.edu (Philip Smolen) writes:
>In article <1992Aug6.154146.11988@irscscm.UUCP> cwilkins@irscscm.UUCP (Charlie Wilkinson) writes:
>[Lots deleted]
>>You might want to consider using the low level I/O functions:
>>open()		>sopen()	>creat()	>dup() & dup2()	>lseek()
>>tell()		>read()		>write()	>eof()		>close()
>>
>>My book (The MSC Bible 2nd edition) says
>>that although none of these functions are ANSI compliant, almost all of them
>>can be used with every compiler.  The exception being that some are not
>>Unix and/or Xenix compatible.
>
>I thought these WERE the unix file utilities.  (as opposed to the ansi
>file utilities)  According the Borland C++ 3.1 online help, only eof()
>is not ANSI compliant.  eof() can be avoided with lseek() and tell().
>
>IMHO the Unix file utilities are easier to use than the corresponding
>ANSI ones.
>

For SOME applications, the UNIX I/O calls will be both faster and
easier to use than the ANSI calls that are built on top of them.
However, a program that uses these calls may not port to a non-Unix
system.  For operating systems with files systems are not organized
like they are in Unix, it it likely that these functions will not be
implemented.  Instead there will be functions like Q$DIO, _callio()
etc which give you the same low level access to the way that file
system is organized as creat() and friends give you on Unix.

Looking for "creat()" on other systems is about as sensible as looking
for Q$DIO on Unix.