Recent Features
| |||||||||||||
When the programmer is forced to handle return codesWhen the programmer is forced to handle return codesPosted Dec 5, 2009 21:37 UTC (Sat) by nix (subscriber, #2304)In reply to: When the programmer is forced to handle return codes by hppnq Parent article: On the importance of return codes
Yeah, sorry, my attitude about people doing file I/O in many threads at
once is that they deserve everything they get.
I much prefer using processes and explicit IPC to threads.
(Log in to post comments)
When the programmer is forced to handle return codes Posted Dec 6, 2009 11:31 UTC (Sun) by hppnq (guest, #14462) [Link] I think the point is that close() will always render the file descriptor unusable: if it doesn't you really cannot close() it again safely, because you've bumped into a kernel bug.
|
|||||||||||||