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

Groups > gnu.bash.bug > #14113 > unrolled thread

Variables can’t contain NUL

Started by"Garreau\, Alexandre" <galex-713@galex-713.eu>
First post2018-05-20 04:56 +0200
Last post2018-05-20 04:56 +0200
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Variables can’t contain NUL "Garreau\, Alexandre" <galex-713@galex-713.eu> - 2018-05-20 04:56 +0200

#14113 — Variables can’t contain NUL

From"Garreau\, Alexandre" <galex-713@galex-713.eu>
Date2018-05-20 04:56 +0200
SubjectVariables can’t contain NUL
Message-ID<mailman.122.1526823499.1292.bug-bash@gnu.org>
On 2015-11-13 at 07:17, Greg Wooledge wrote:
> Actually in the most general case, where those output streams may
> contain NUL bytes, it requires two temp files, because you can't store
> arbitrary data streams in bash variables at all.

Why do bash variables use 0-terminated arrays instead of arrays structure
with a length attribute?

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web