From: Erik Max Francis <max AT alcyone DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: tmpfile() and binary mode in DJGPP
Date: Fri, 30 May 1997 19:51:20 -0700
Organization: Alcyone Systems
Lines: 25
Message-ID: <338F9228.56BA179B@alcyone.com>
References: <01IJHT6V95V6001VQJ AT cc DOT uab DOT es>
NNTP-Posting-Host: newton.alcyone.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

X DOT PONS AT UAB DOT ES wrote:

>   - My 1989 book of ANSI C states that the file opened using
>     tmpfile() is always a binary file.
>   - The help of TC and BC compilers also states this and really
>     create the file in "w+b" mode, never in text mode.

You are correct.  The ANSI C standard dictates that "the file is opened
for update with `wb+' mode" (7.9.4.3).

> If you, DJGPP gurus, do not agree with us (and with our colleagues
> that love a lot the DJ compiler, but that have wasted a lot of time
> trying to understand a problem derived from this "characteristic"
> of the tmpfile() function), at least, please include this asymmetry
> on the FAQ.

DJGPP should certainly conform to ANSI C.

-- 
       Erik Max Francis, &tSftDotIotE / email / max AT alcyone DOT com
                     Alcyone Systems /   web / http://www.alcyone.com/max/
San Jose, California, United States /  icbm / 37 20 07 N  121 53 38 W
                                   \
     "Covenants without the sword / are but words."
                                 / Camden