[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Portability of fopen (foo, "wb") (Was: bug in AC_COMPUTE_INT)

From: Guido Draheim
Subject: Re: Portability of fopen (foo, "wb") (Was: bug in AC_COMPUTE_INT)
Date: Thu, 16 Nov 2000 18:20:20 +0100

Peter Eisentraut wrote:
> Akim Demaille writes:
> > Does anybody know whether using fopen (foo, "wb") is portable?
> Extremely doubtful.

The "b" is an ansi-C requirement, however there may be some systems
that are simply not compliant. AFAICS these are quite old, somewhere
in the eighties or so - therefore, it is hard to find factual
information as the world wide web is considerably younger. I just
found second hand information that some DEC ultrix libc did barf
at "b". Any halfway sane implementation of a libc will simply
ignore trailing "garbage", so it is safe to put the b as the last.

I would leave it... the cries will be loud enough, - that is true for
quite some cases where there *is* an obvious error instead of 
silent bad behaviour, esp. when we speak about decades before the
autoconf was even invented... 

Anyone to give an example of a non-updated "b"-non-ansi-c-compliant 
system that is in actual use? I really really doubt that...

-- guido                                Edel sei der Mensch, hilfreich und gut
31:GCS/E/S/P C++$++++ ULHS L++w- N++@  d(+-) s+a- h.r(*@)>+++ y++ PS++PE 5++X-

reply via email to

[Prev in Thread] Current Thread [Next in Thread]