Re: Command substitution with null bytes generates warning

[Chet Ramey]

On 9/19/16 2:41 PM, Greg Wooledge wrote:

> Bash has only three choices that I can think of: it can silently drop the
> NUL bytes (4.3 behavior), it can drop ALL of the bytes and return an
> error, or it can drop the NUL bytes with a warning (4.4 behavior).

There is a fourth choice: terminate the string read from the command
substitution at the first NUL.  Pretty sure nobody wants that, even
though that's what would happen if bash didn't drop the NULs.

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