🚀 go-pugleaf

In article <ig25.728085496@fg70> ig25@fg70.rz.uni-karlsruhe.de (Thomas Koenig) writes:
>Does the standard have anything to say about wether stdin and stdout
>are opened to a file stream opened in binary mode?

Almost.  It says that they're text streams.  It doesn't require text streams
to be different from binary streams, but of course on some implementations
they are different.

>Would a program which wrote binary data to standard output, or read it
>from standard input, be complying?

Under the weak definition of "conforming" (for programs) it could very well
do so.  Under the strong definition of "strictly conforming" it is possible,
but you'd have to be very restrictive in the data that you write, and in
other operations that you do.  I'd have to guess your purpose and guess no.

>The reason for asking is that many programs which were developed for
>UNIX, which do this, fail on systems where binary and text mode for file
>streams are not identical.  I'd like to know wether they fail in a
>standard - conforming or a non - standard - conforming way :-)

If the failure means that the output is different from what the output
would be when they succeed, then obviously they're not strictly conforming.
(Part of the definition of strictly conforming is that they do not produce 
output dependent on any unspecified, undefined, or implementation-defined
behavior.)
--
Norman Diamond                diamond@jit.dec.com
If this were the company's opinion, I wouldn't be allowed to post it.
Pardon me?  Or do I have to commit a crime first?