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: Roger Marquis <marquis@xxxxxxxxx>
Date: Thu, 2 Jul 2009 13:23:20 -0700 (PDT)
References: <200907012242.n61MgCCp020103@xxxxxx> <4A4C2005.6030402@xxxxxx> <4a4c81a6.2tWl4Z9DpJUyvd+z%Joerg.Schilling@xxxxxx> <200907021327.n62DRe5k029384@xxxxxx> <20090702143325.GA5491@xxxxxx> <4A4CCA35.6070009@xxxxxx> <4A4CCBE1.7020801@xxxxxx> <20090702150847.GA6190@xxxxxx> <090702183047.AA87319.SM@xxxxxx><4858.76.191.129.144.1246561262.squirrel@xxxxxx>
Don wrote:
Chet wrote:
Sure, but that will eventually get fixed.  The intent as I understand
it is that the portable character set be locale-independent (or at
least constant across "conforming locales").

... the intent was not to require that
the characters in the portable character set have the same
encoding in all locales even though that could simplify a lot
of code.
Still, as a standards body POSIX' assumes responsibility for a portable
character set, even if the original deliverables did not need it.

One question though, are we talking about a portable character set for
variable names, variable values, or both?   Don't know if there's a need to
ensure the portability of values but I see a substantial value in
standardizing the character set for variable names, to ASCII ideally.

Roger Marquis

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