2 ms·
> I don't think any library should be calling setenv() It’s already a problem if the library is calling getenv(), because this could happen concurrently to the
by layer8 3y ago
> I don't think any library should be calling setenv()
It’s already a problem if the library is calling getenv(), because this could happen concurrently to the main program calling setenv(). The only universally safe solution is to not use setenv()/putenv() at all.
Which I think is actually reasonable. But yes it makes those functions broken in a multithreaded program.