Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 4 Nov 2004 17:00:56 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Perl binmode problem on text mount
Message-ID: <20041104220056.GG16067@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <41897FF4 DOT 1080501 AT agilent DOT com> <418A9BF3 DOT 5010903 AT familiehaase DOT de> <20041104212608 DOT GC16067 AT trixie DOT casa DOT cgf DOT cx> <418AA3FA DOT 7080905 AT familiehaase DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <418AA3FA.7080905@familiehaase.de>
User-Agent: Mutt/1.4.1i

On Thu, Nov 04, 2004 at 10:49:46PM +0100, Gerrit P. Haase wrote:
>Christopher Faylor wrote:
>>Pipes are binmode by default.
>
>That means they are just as pipes are ought to be, "what goes in comes
>out again, not more and not less"?
>
>Or does it mean that a pipe always strips \r?  Then the cat example of
>the OP doesn't count at all.

binmode means there is no extra processing on the fd.  It is handled
just like linux.  Linux doesn't add or subtract any characters when
it is doing I/O.

You're right, though.  The cat example really doesn't provide any useful
details.  In fact, cat will output in text mode in some cases.

The definitive test would be to run the older and newer versions of
perl on the newest version of cygwin.  If the output using 'binmode'
differs between the two then perl is doing something wrong.  If it
is the same then cygwin is doing something wrong.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/