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
Message-ID: <400EB21C.5090803@ieee.org>
Date: Wed, 21 Jan 2004 17:08:44 +0000
From: Jason Pearce <jason DOT pearce AT ieee DOT org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
CC: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
Subject: Re: Is PERLIO=crlf recommended for Perl 5.8.0-3 and up?
References: <400E8750 DOT 3060005 AT ieee DOT org> <93440042367 DOT 20040121174012 AT familiehaase DOT de>
In-Reply-To: <93440042367.20040121174012@familiehaase.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Gerrit P. Haase wrote:

>>I guess the alternative is to leave perl to access the files in binary
>>mode and then modify the perl scripts to detect and account for what 
>>ever line ends it finds. Is that the recommended approach rather than 
>>using PERLIO=crlf?
>>    
>>
>
>To get the most out of PERLIO the script should take care about the
>platform it is running on and define one or more PERLIO layers during
>runtime.  It may not always be correct to add CR to some output, e.g
>when processing binary files.
>
>
>Gerrit
>  
>
So the correct technique for this approach is to read up on PERLIO 
layers and use them to solve the problem (as opposed to "chomp" ing and 
appending CRs in an adhoc manner!).

Jason


--
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/