This is the mail archive of the
mailing list for the cygwin project.
Re: Similar Bash 3.1.18 CR/LF Problem
- From: mwoehlke <mwoehlke at tibco dot com>
- To: cygwin-talk at cygwin dot com
- Date: Wed, 04 Oct 2006 12:29:26 -0500
- Subject: Re: Similar Bash 3.1.18 CR/LF Problem
- References: <4C89134832705D4D85A6CD2EBF38AE0F7B137A@PAUMAILU03.ags.agere.com> <01ff01c6e7d8$0f1367c0$a501a8c0@CAM.ARTIMI.COM>
- Reply-to: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
Dave Korn wrote:
On 04 October 2006 18:06, Williams, Gerald S (Jerry) wrote:
Seriously, I'd have a hard time believing that supporting
<CR><LF> endings would noticably impact performance if it
were done as part of upstream BASH. Special-casing Cygwin
(especially when you start doing things like checking for
DOS paths, examining the first line, etc.) would impact
performance, surely. So I agree--don't do that.
That's a total non-sequitur. A piece of code will have the same impact,
whether it's included directly in the upstream sources, or whether it's a
cygwin local patch surrounded by #ifdef __CYGWIN__.
"Your facts are out of order." :-D
This message will self destruct in five millennia.