[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bash 4.x filters out environmental variables containing a dot in the
From: |
Christian Krause |
Subject: |
Re: bash 4.x filters out environmental variables containing a dot in the name |
Date: |
Sun, 19 Jul 2009 12:40:52 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090320 Fedora/2.0.0.21-1.fc10 Thunderbird/2.0.0.21 Mnenhy/0.7.5.0 |
Hi Chet,
Chet Ramey wrote:
> Posix also says that "variables" are inherited from the environment. That
> word has a very specific meaning, as was reiterated during the $@ and set -u
> discussion. The same "variables" language is used when Posix talks about
> creating the environment for shell execution environments.
>
> The question is whether "tolerant" just means that the shell doesn't display
> a warning message about the assignment, as it does when you use an invalid
> variable name in an assignment statement, or exit with a variable assignment
> error, or dump core with a seg fault, as in many historical versions of sh.
> It may or may not also mean that the shell passes inherited invalid variable
> names to child processes.
>
> It seems, though, that there might be enough use for me to try and make it
> work. While I'm not wild about creating yet another class of variable,
> there might be a way to do it simply.
What's the current status of this issue? I'd like to offer my help for
testing the fix since I have a strong interest to get the problem (linux
kernel (UML) can't be compiled properly with bash 4.x) resolved.
Thank you very much in advance!
Best regards,
Christian
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: bash 4.x filters out environmental variables containing a dot in the name,
Christian Krause <=