🚀 go-pugleaf

In <4fbfno$7f@noc.tor.hookup.net> Rajendra_Singh@msn.com (Rajendra Singh) writes:

>gclind01@starbase.spd.louisville.edu (George C. Lindauer) wrote:
>
>>The only reason I know of is UNIX portability.  Whenever I run across a
>>unix program that uses the old-style open instead of fopen I usually
>>end up rewriting it anyway though; I've had so many problems with
>>the unix-style stuff I just rather would deal with the ANSI style.
>
>That's incorrect.  fopen() is used for buffered I/O!  open() is not a
>UNIX specific function nor is it non-ANSI!

That's incorrect.  open() is a Unix-specific function (even if it was
emulated on other systems) and it IS non-ANSI!

BTW, in Unix both open() and fopen() are used for buffered I/O!  fopen()
adds an _additional_ level of buffering in order to minimize the number 
of read/write system calls.  The kernel is doing its own buffering
for read/write operations.

Dan
--
Dan Pop
CERN, CN Division
Email: danpop@mail.cern.ch 
Mail:  CERN - PPE, Bat. 31 R-004, CH-1211 Geneve 23, Switzerland