[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: |
Andreas Schwab |
Subject: |
Re: bash 4.x filters out environmental variables containing a dot in the name |
Date: |
Fri, 26 Jun 2009 10:57:13 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (gnu/linux) |
Chet Ramey <chet.ramey@case.edu> writes:
> It's not a bug. Posix explicitly restricts environment variable names
> to consist of uppercase letters, lowercase letters, digits, and
> underscores.
POSIX only talks about their use in POSIX utilities. It does not say
anything about non-POSIX utilities and extensions (and using other
characters _is_ a proper extension).
> There is no provision for variables with invalid names that don't
> exactly exist and are just passed down to applications in their
> environment.
POSIX explicitly says that other characters may be permitted, and Unix
does permit them, just like Unix permits any character except / and NUL
in filenames.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."