Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ncar!gatech!mcnc!uvaarpa!haven!mimsy!nocusuhs!nmrdc1!minixug!uwalt!waltje
From: waltje@uwalt.nl.mugnet.org (Fred 'The Rebel' van Kempen)
Newsgroups: comp.os.minix
Subject: Re: fopen() access modes
Message-ID: <9103211994@uwalt.nl.mugnet.org>
Date: 21 Mar 91 17:00:44 GMT
References: <2041@Terra.cc.brunel.ac.uk>
Organization: MicroWalt Corporation, for MINIX Software Development
Lines: 22

eesrajm@cc.brunel.ac.uk (Andrew J Michael) wrote:
> 
> Would one of the POSIX police please let me know what the current state of
> thinking is with regard to the access mods for fopen() ?
I am just a programmer, but:

Estdio(3) does it correctly.  Use it, and Be Happy :-)

> I am particularly interested in the use of the 'b' flag.  This is obviously
> meaningless to MINIX/UNIX, but what should be done with it ?  Should it
> be silently ignored, or flagged as an error ?
It means "binary open" (as you probably know), and it mainly causes the
stdio functions to:

- not treat byte 0xFF as EOF ( == -1 !)
- not perform any data conversion

Again, Estdio does the job well...

Fred.
--
MicroWalt Corporation, for MINIX Development	waltje@uwalt.nl.mugnet.org
Tel (+31) 252 230 205, Hoefbladhof  27, 2215 DV  VOORHOUT, The Netherlands