| |||||||||||||
timerfd() and system call reviewtimerfd() and system call reviewPosted Aug 16, 2007 15:25 UTC (Thu) by mrfredsmoothie (subscriber, #3100)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. Hmmm. Another way would be to require someone to write a non-trivial program which uses the API to do something useful.
(Log in to post comments)
timerfd() and system call review Posted Aug 17, 2007 9:01 UTC (Fri) by addw (guest, #1771) [Link] Another way would be to require someone to write a non-trivial program which uses the API to do something useful. And make that non-trivial program part of the available documentation. One of the most frustrating things in working with FLOSS is that often (but by no means always) the documentation is awful. It is generally a set of notes written by the author (who entirely understands what it is all about), so someone coming new to the problem has a really hard time getting to see how everything fits together. A non-trivial program would be great for system calls; something similar needs to be available for other FLOSS components.
timerfd() and system call review Posted Aug 20, 2007 8:25 UTC (Mon) by mkerrisk (subscriber, #1978) [Link] I'm open to suggestions about specific pages in man-pages that need non-trivial example programs. (Over time an increasing number of example programs have been added.)
|
|||||||||||||