3 ms·
But it should be. And we can make it thread safe very easily. Why the hell should we be limited by POSIX? Why can't we provide features beyond it? It's access
by quotemstr 10y ago
But it should be. And we can make it thread safe very easily. Why the hell should we be limited by POSIX? Why can't we provide features beyond it?
It's access to the environ global that's inherently unsafe. setenv and a modified getenv can be accommodated just fine.
- pjmlp 10y agoPortability across UNIX platforms.
- quotemstr 10y agoSo portability to you, means that the platform can't add features? I reject portability then.
- pjmlp 10y agoTo me? No, to everyone. Lets say GNU/Linux does that, what you would do for other UNIX flavours, #ifdef soup? The goal of standards is exactly to minimize that.
- quotemstr 10y agoIfdefs would be required. Or some kind of wrapper in gnulib. Or, like systemd, just non-portability. Your philosophy means stagnation forever. I reject that. Programs that use getenv today will not break. Objection to the existence of a getenv_s is absurd. The only way we move forward is by trying new things, and we can't possibly get everyone to try a new thing all at once. If the thing ends up being useful, we standardize it.