This is the mail archive of the
mailing list for the Cygwin project.
Re: How is textmode/binmode determined in Cygwin 1.1.0 net releas e for pipes?
- To: "'cygwin at sourceware dot cygnus dot com'" <cygwin at sourceware dot cygnus dot com>
- Subject: Re: How is textmode/binmode determined in Cygwin 1.1.0 net releas e for pipes?
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Fri, 28 Apr 2000 00:15:56 -0400
- References: <1DB8BA4BAC88D3118B2300508B5A552C0C8CDB@mail.fitlinxx.com>
- Reply-To: cygwin at sourceware dot cygnus dot com
On Thu, Apr 27, 2000 at 11:51:50PM -0400, David Bolen wrote:
>I suppose my question can be rephrased as whether or not 1.1.0 changed
>the default behavior for pipes from b20.1 (without any CYGWIN
>environment setting)? It was my understanding that the default should
>be binary, and that's how my previous b20.1 seemed to be working. But
>1.1.0 seems to instead be defaulting to text. This would be for pipes
>opened via the pipe() call, thus without any particular O_* flags.
The test below indicates that pipes are being opened in binmode by
And, here's another observation. The best way to answer a question like
"How does xxx work" is to write a test case which exercises 'xxx'. This
is even better than reading the source for 'xxx'.
main(int argc, char **argv)
write(pipes, "hello\r\n", 7);
printf ("%d = read(%d...)\n", read(pipes, buf, 80), pipes);
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org