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


Groups > gnu.bash.bug > #14141

Re: Variables can’t contain NUL

Path csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From L A Walsh <bash@tlinx.org>
Newsgroups gnu.bash.bug
Subject Re: Variables can’t contain NUL
Date Thu, 24 May 2018 17:55:15 -0700
Lines 29
Approved bug-bash@gnu.org
Message-ID <mailman.445.1527209727.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> <1346a7f6-33b5-43f5-3bd5-7db40cda34f5@case.edu>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding 7bit
X-Trace usenet.stanford.edu 1527209728 12982 208.118.235.17 (25 May 2018 00:55:28 GMT)
X-Complaints-To action@cs.stanford.edu
To bug-bash <bug-bash@gnu.org>
Envelope-to bug-bash@gnu.org
User-Agent Thunderbird
In-Reply-To <1346a7f6-33b5-43f5-3bd5-7db40cda34f5@case.edu>
X-detected-operating-system by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] [fuzzy]
X-Received-From 173.164.175.65
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.21
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <http://lists.gnu.org/archive/html/bug-bash/>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref csiph.com gnu.bash.bug:14141

Show key headers only | View raw



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! ;-)




Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

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

csiph-web