Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14121
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Variables can’t contain NUL |
| Date | 2018-05-21 10:15 -0400 |
| Message-ID | <mailman.164.1526912158.1292.bug-bash@gnu.org> (permalink) |
| References | <564532BD.60801@tlinx.org> <20151113131735.GE27325@eeg.ccf.org> <e5ye6lts2mjn.ykx.xxuns.g6.gal_-_@galex-713.eu> <20180521123718.cumwnvmpt6x7urse@eeg.ccf.org> |
On 5/21/18 8:37 AM, Greg Wooledge wrote: > If you're looking for some deeper answer, like "Why did Stephen Bourne > write it this way back in 1977?" then I would hazard a guess along the > lines of "It is tightly coupled to the underlying C argument-passing > interface which uses NUL-terminated strings." As well as the majority of the libc API, which depends on null-terminated strings. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Variables can’t contain NUL Chet Ramey <chet.ramey@case.edu> - 2018-05-21 10:15 -0400
csiph-web