This is the mail archive of the cygwin-talk mailing list for the cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Re: Similar Bash 3.1.18 CR/LF Problem


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__.

Non-sequiturs are my speciality. But see my response to CGF
on the main list. Sometimes there's a message behind the
message. :-)

gsw

P.S. Sometimes there's just static, too.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]