Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #11915

Re: redirecting a file descriptor to an array variable? Possible? How? RFE?

Show all headers | View raw

On Thu, Nov 19, 2015 at 4:29 AM, Linda Walsh <bash@tlinx.org> wrote:
> However one cannot
> categorically say that a NUL byte can't be used as an argument.

Likely only in an escaped format, or just as a single byte or character.

> Solving
> other places where it doesn't work might make it so that it *would* work...

Most parts of bash interpret, store and handle parameters (internal
data; not shell arguments) as C-strings (null-terminated) (as an
example, see make_variable_value() in variables.c, or savestring() in
general.h).  It's the key to understanding why NUL bytes doesn't work
most of the time in bash.  If you would want it to interpret them as
strings like C++ strings or Ruby strings, it would need a big
overhaul.  You would also think about possible compliance issues,
compatibility issues, complexities and vulnerabilities.  It's great
but not easy.

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: redirecting a file descriptor to an array variable? Possible? How? RFE? konsolebox <konsolebox@gmail.com> - 2015-11-19 19:01 +0800

csiph-web