That (managing the env "from the outside) is and always has been the "supposed" way of using it. Modifying _your own_ environment _at runtime_ is not. The corr

That (managing the env "from the outside) is and always has been the "supposed" way of using it. Modifying _your own_ environment _at runtime_ is not. The corresponding functions - setenv/getenv - and state - envp/environ - have in the UNIX standards "always" (since threads exist, really) been marked non-MT. "way back when" people were happy to accept that stated restrictions on use don't make bugs. Today, general sense of overentitlement makes (some) people say "but since whatever-trickery can remove this restriction... you're wrong and I'm entitled to my bugfix". I agree the damage is done, though.