[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue with Bash-4.3 Official Patch 27

From: Lorenz . Bucher . ext
Subject: Re: Issue with Bash-4.3 Official Patch 27
Date: Fri, 17 Oct 2014 17:22:30 +0200

No, I can't. 
$ foo%%="bar"
foo%%=bar: command not found

Or better said not in the normal way
$ set foo%%=bar

Mit freundlichen Grüßen

Lorenz Bucher
TechConnect GmbH

Im Auftrag der/on behalf of
Rohde & Schwarz GmbH & Co. KG

Postfach 80 14 69   •   81614 München
Mühldorfstraße 15   •   81671 München
Telefon:        (089) 4129-15684
Mail: address@hidden
Internet: www.rohde-schwarz.com

Von:    Chet Ramey <address@hidden>
An:     address@hidden, address@hidden, 
Kopie:  address@hidden, "Eduardo A. Bustamante López" 
<address@hidden>, address@hidden
Datum:  10/16/2014 03:09 PM
Betreff:        Re: Issue with Bash-4.3 Official Patch 27
Gesendet von:   

On 10/15/14, 1:49 PM, address@hidden wrote:

> But anyway.
> In my opinion I should trust a shell not violating their own rules and 
> able to import their own variables.

That's not the issue.  The shell can import variables like that just fine,
as evidenced by exported functions actually working.  The question is
whether or not `export' lets you set and export non-identifiers.  It does
and should not.

> So the % character should be allowed to be used in variable names.

No, shell variable names should continue to be shell identifiers.  You
can already use `%' (any character, really) in environment variable

``The lyf so short, the craft so long to lerne.'' - Chaucer
                                  ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    

reply via email to

[Prev in Thread] Current Thread [Next in Thread]