Linda Walsh wrote: > wrote: > > The change only affects environment variables **loaded as exported > > functions**. Bash won't forbid you from using / inside the name of an > > environment variables. > > > ---- > The below doesn't demonstrate bash doing anything with the variable you > declared. > > You declare an ENV var with 'env' (not part of bash), then you start a new > shell and use env to see that the original value is still there. It > should be. > > You are not demonstrating any interaction with BASH.
I was precisely trying to demostrate that bash wasn't doing anything. I got the impression that becker/Jon? was claiming that with Patch 27 (which removes those variable with a slash from loading as functions), variables with a / were removed from the environment. After rereading the subthread, I think I may have misunderstood them.
