| |||||||||||||
Third-party librariesThird-party librariesPosted Aug 28, 2009 1:44 UTC (Fri) by giraffedata (subscriber, #1954)In reply to: Third-party libraries by Los__D Parent article: In brief
Besides "prepare_for_exec()" being a horrible interface, do you really think that programmers that doesn't care to close unknown fds, would care to call it? That's beside the point. I was responding to a claim that there is no way to write a correct multithread program involving a third party library that opens files without O_CLOEXEC. And that that distinguishes O_CLOEXEC from the proposed O_NOSTD. If on the other hand you just want to argue that O_CLOEXEC is convenient, with or without threads, then you're putting it in the same class as O_NOSTD.
(Log in to post comments)
Third-party libraries Posted Aug 28, 2009 5:39 UTC (Fri) by Los__D (guest, #15263) [Link]
There is no other way for the library author to make sure that his library opened fds are safe.
It is hardly "convenience", but good library programming style, to make sure that internal data stays internal.
I would go so far as argue, that the naïve library user that doesn't close the fds, isn't entirely an idiot for expecting not to be responsible for library data.
|
|||||||||||||