undefined | Better HN

0 pointsgoeiedaggoeie1y ago0 comments

setenv and getenv have never been thread safe, why the concern with it now?

0 comments

The concern now is that, unlike when Posix was set in stone, threads exist.

loeg1y ago

The p in pthreads stands for Posix. I.e., uh, Posix is neither set in stone, nor entirely predates threads.

I am old enough to remeber when UNIX only had processes, and several thread designs were being discussed until eventually pthreads one design won.

POSIX predates adoption of threads in the UNIX world.

And when can we expect the version of Posix that fixes setenv to be MT-safe?

j / k navigate · click thread line to collapse

The concern now is that, unlike when Posix was set in stone, threads exist.

loeg1y ago

The p in pthreads stands for Posix. I.e., uh, Posix is neither set in stone, nor entirely predates threads.

pjmlp1y ago

I am old enough to remeber when UNIX only had processes, and several thread designs were being discussed until eventually pthreads one design won.

POSIX predates adoption of threads in the UNIX world.

And when can we expect the version of Posix that fixes setenv to be MT-safe?

j / k navigate · click thread line to collapse