On Jul 03 2020, Paul Smith wrote: > This would be backward-incompatible, and also it would add some > complexity: we'd have to add a new state to variable storage to allow a > variable to be known to make (to hold the flag that says it's > exportable) but to actually not be considered defined (until/unless it > was set), so it wouldn't be added to the child's environment.
Note that this is how export works in the shell. `export FOO' only sets the export attribute, but keeps the variable unset (and does not appear in the environment of subsequent commands) if it doesn't have a value yet. Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
