timerfd() and system call review
Posted Aug 15, 2007 1:24 UTC (Wed) by mkerrisk
In reply to: timerfd() and system call review
Parent article: timerfd() and system call review
"one of the best ways to find shortcomings in an API is to attempt to document it comprehensively"
True. However it's not nearly as good when the person involved in writing the code implementing the API also writes the documentation -- that does not strain underlying assumptions in the way that thorough review and proper documentation processes tend to.
Agreed. However, I've been trying to encourage kernel developers to supply the beginnings of a man page that I then review. Even that is a very fruitful process, when it happens. But the ideal is of course as you suggest a much better review and documentation process involving kernel developers.
So perhaps once the API is in glibc and documented by another party it could be considered "stable".
There are many problems with this idea: some APIs never make it to glibc; sometimes glibc provides a wrapper that modifies the API; sometimes documentation does not arrive for a very long time...
to post comments)