Dave Korn wrote:
On 27 September 2006 20:42, Malcolm Nixon wrote:
In my opinion a better solution would have been to err on the side of
compatibility and only use the new fast readline code if manually
enabled.
Then according to your opinion, everyone else in the world has to suffer
from crippled bash performance because you can't be bothered to fix your
systems. Better for /you/ maybe, but it's not always all about you. In MY
opinion, a better solution would be to err on the side of efficency, and only
use the old slow readline code if manually enabled.
Right; non-standard behavior (and any non-binary treatment of '\r'
certainly counts!) should - and I might dare even to say "must" - be
disabled by default. Although in this case I can't think of any reason
why you would ever have a '\r' in a shell script (other than as part of
a line ending). Although if we make any of this optional, then IMO it
needs to be done the right way, which is to just ignore '\r', at least
at the end of lines. That way we can ALWAYS read in binary mode, and it
isn't a major performance penalty.
I suppose this would mean if it is turned on, scripts on textmode mounts
will actually be faster because we can ignore the textmode.
--
Matthew
The hippo made me do it! What? What do you mean you can't see the hippo?
--
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/
