Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14113
| From | "Garreau\, Alexandre" <galex-713@galex-713.eu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Variables can’t contain NUL |
| Date | 2018-05-20 04:56 +0200 |
| Message-ID | <mailman.122.1526823499.1292.bug-bash@gnu.org> (permalink) |
| References | <564532BD.60801@tlinx.org> <20151113131735.GE27325@eeg.ccf.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?
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Variables can’t contain NUL "Garreau\, Alexandre" <galex-713@galex-713.eu> - 2018-05-20 04:56 +0200
csiph-web