3 ms·
Any time anybody tells you that POSIX isn't terrible, the subject of this article is the sort of thing you need to bear in mind. (For a long time, I thought th
by to3m 10y ago
Any time anybody tells you that POSIX isn't terrible, the subject of this article is the sort of thing you need to bear in mind.
(For a long time, I thought that literally the only thing that POSIX didn't fuck up is the way they don't have any analogue to MAXIMUM_WAIT_OBJECTS. But then, after I gained more experience with POSIX, I realised that even if I don't understand how, this too was probably also something they got wrong.)
- temac 10y agoPosix is terrible. But I'm not sure we have anything better. MAXIMUM_WAIT_OBJECTS is also terrible of course, but even apart from that Win32 is not bright, at all. The doc contains so little details (or worse is sometime even false) that the real doc when you start to ask serious questions is ReactOS, Wine, or even the NT/2000 source leaks, and then IDA. Compared to that, Posix is actually documented and implemented mostly correctly by tons of OSes. Its easy to ship an API with basically no spec (so nobody can tell you that there is a bug when they find one - actually even if there were some real specs about Win32 I think there is public no way to report bugs in there to MS!), and that does not have to be compatible with any other implementation...