[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 0xFF and read -N

From: Chet Ramey
Subject: Re: 0xFF and read -N
Date: Mon, 02 Sep 2013 19:25:30 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5

On 8/31/13 3:13 PM, Stephane Chazelas wrote:

> Bash Version: 4.2
> Patch Level: 45
> Release Status: release
> When called with the -N option, "read" seems to consider the byte 0xFF
> as meaning EOF (well, not exactly since it doesn't set the exit status to
> non-zero)

Not quite: it interprets that as satisfying the delimiter, since the delim
is set to -1.  It needs to test an additional flag.  I've made that fix,
and the fix will be in bash-4.3.

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]