News for hackers. Stuff that matters.
Re:The Sorry State of C++ Portability by udp on Wednesday October 24, 2012 @04:10PM (#4694821)
Now that's one area where Windows really differs. You can't write a high performance server for Windows without using IOCP, which couldn't be more different from what every other platform has for that kind of thing (epoll, kqueue, /dev/poll, ...)

It was interesting watching node/libuv face all the same problems I did when originally trying to abstract over this.

Re:The Sorry State of C++ Portability by eps on Wednesday October 24, 2012 @04:31PM (#4694921)
It is possible to wrap iocp api into a bsd-style socket interface compatible with epoll semantics. It ain't pretty, the socket int becomes an index into an internal map of per-socket support structs, there are ungodly edge cases and what not, but it's doable nonetheless.
Re:The Sorry State of C++ Portability by pjmlp on Wednesday October 24, 2012 @04:18PM (#4694852)
Solaris?
Re:The Sorry State of C++ Portability by udp on Wednesday October 24, 2012 @04:32PM (#4694925)
Interesting - I wasn't aware that any other platform implemented IOCP. I wonder how that performs vs. traditional I/O with /dev/poll?
Re:The Sorry State of C++ Portability by pjmlp on Thursday October 25, 2012 @03:15AM (#4696668)