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: Similar Bash 3.1.18 CR/LF Problem


Dave Korn wrote:
On 04 October 2006 18:29, mwoehlke wrote:
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

Oh, I do beg your pardon, let me try that one again:


A piece of code will have the same impact, whether it's a
cygwin local patch surrounded by #ifdef __CYGWIN__, or
whether it's included directly in the upstream sources.

Are they in the right order now? ;)

(beginning of reply elsewhere) ...or you're just incorrigible. ;-)

"Sterilize..."
(Ok, I'm about out of things I can quote accurately)

--
Matthew
This message will self destruct in five millennia.


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