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

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

Re: Variables can’t contain NUL

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

  Re: Variables can’t contain NUL L A Walsh <bash@tlinx.org> - 2018-05-24 17:55 -0700

#14141 — Re: Variables can’t contain NUL

Chet Ramey wrote:
> 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.
>   
---
    And so many bugs happen because of it.
    Maybe the C++ string class would would be more robust...
   
Wouldn't have to be all at once, but getting it to compile under C++ as
legacy C code might be a useful first step.

    Then specific features or areas could be targeted for rework
or what's the buzzword these days... oh yeah... refactoring! ;-)

[toc] | [standalone]

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

csiph-web