This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: igncr vs text mode mounts, performance vs compatibility
- From: Eric Blake <ebb9 at byu dot net>
- To: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
- Date: Thu, 26 Oct 2006 19:07:41 -0600
- Subject: Re: igncr vs text mode mounts, performance vs compatibility
- References: <000701c6f95f$5300ab80$020aa8c0@DFW5RB41>
- Reply-to: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Gary R. Van Sickle on 10/26/2006 6:31 PM:
>
> No no no Korns, you've misunderstood Eric's statement and my question based
> thereupon. Eric made a statement about "those of us who WANT literal \r as
> required by POSIX" being able to circumvent the correct,
> non-speed-compromised, "do-the-right-thing" behavior that he is
> (re-)implementing.
The numbers showed that bash was slower with igncr turned on. Yes, igncr
is a faster option than bash-3.1-6, but still slower than straight reading.
> My question was, to paraphrase, "Why would anybody want
> the old, broken behavior?"
Because it is identical to the behavior you would get for the same script
on Linux. Cygwin emulates Linux, and until Linux ignores \r on binary
files, you should not expect cygwin to go out of its way to do so either.
- --
Life is short - so eat dessert first!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFQVvd84KuGfSFAYARAvMnAKDKLB6/JBUeuikDMC7tYVAnF/asPQCfX7G3
tYC+oVHfy2VyF+j4irDRCHE=
=t6CM
-----END PGP SIGNATURE-----