Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14121 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2018-05-21 10:15 -0400 |
| Last post | 2018-05-21 10:15 -0400 |
| 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.
Re: Variables can’t contain NUL Chet Ramey <chet.ramey@case.edu> - 2018-05-21 10:15 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2018-05-21 10:15 -0400 |
| Subject | Re: Variables can’t contain NUL |
| Message-ID | <mailman.164.1526912158.1292.bug-bash@gnu.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 top | Article view | gnu.bash.bug
csiph-web