Talking about shells and environment variables:
As they are not valid *variable names*, those strings should not be
imported as variables in the first place by a shell.
I would not want to see those showing up in my ksh namespace, and
neither would I want to debug any code
depending on
This was fixed a few years ago.
The posix says you do not touch what you don't understand so
definitely no curing. The only proper thing to do is to ignore.
The question here is whether to display such variables or not.
Ksh won't be able to print them, set them nor unset them. That's clear.
On 09/30/14 14:01, Michal Hlavinka wrote:
This was fixed a few years ago.
The posix says you do not touch what you don't understand so definitely no
curing. The only proper thing to do is to ignore.
I agree with that logic.
The question here is whether to display such variables or not.
On 9/30/14, 9:52 AM, Henk Langeveld wrote:
In my view, the environment (the structure pointed to by envp**) and the
shell's environment variables are two
different things.
Any entries that are valid variable names should be imported as environment
variables once the process starts.
Any
