Email List: Xaustin-group-lX
[All Lists]

Re: Invalid shell assignments in environment

To: austin-group-l@xxxxxxxxxxxxx
Subject: Re: Invalid shell assignments in environment
From: Geoff Clare <gwc@xxxxxxxxxxxxx>
Date: Thu, 2 Jul 2009 16:08:47 +0100
References: <200907012242.n61MgCCp020103@penguin.research.att.com> <4A4C2005.6030402@case.edu> <4a4c81a6.2tWl4Z9DpJUyvd+z%Joerg.Schilling@fokus.fraunhofer.de> <200907021327.n62DRe5k029384@penguin.research.att.com> <20090702143325.GA5491@squonk.masqnet> <4A4CCA35.6070009@cateee.net> <4A4CCBE1.7020801@case.edu>
Chet Ramey <chet.ramey@case.edu> wrote, on 02 Jul 2009:
>
> Giacomo A. Catenazzi wrote:
> > Geoff Clare wrote:
> > 
> >> The shell should complain about the variable name.  Quoting from
> >> my first mail in this thread:
> >>
> >> | There is a formal definition for "name" in this context:
> >> | |     3.230 Name
> >> |     In the shell command language, a word consisting solely of
> >> |     underscores, digits, and alphabetics from the portable character
> >> |     set. The first character of a name is not a digit.
> >>
> >> Note the phrase "from the portable character set".  Thus u-umlaut
> >> is not a valid character in shell variable names.
> > 
> > "from the portable character set", but in which locale?
> 
> The portable character set, by definition, is locale-independent.

Actually, there is a known issue about the possibility of
characters in the portable character set having different encodings
in different locales.  It was raised back in March in relation
to the slash in pathnames, but it applies to other cases as well,
including this one.

See https://www.opengroup.org/austin/mailarchives/ag/msg18089.html

-- 
Geoff Clare <g.clare@opengroup.org>
The Open Group, Thames Tower, Station Road, Reading, RG1 1LX, England

<Prev in Thread] Current Thread [Next in Thread>