tags 490868 fixed-upstream thanks Fixed for upstrream 3.04.
Andreas. thanks for your bug report. On Mon, Jul 14, 2008 at 10:56 PM, Andreas Mohr <[EMAIL PROTECTED]> wrote: > Package: manpages-dev > Version: 3.02-1 > Severity: wishlist > > Hello all, > > man 2 select states: > > " > timeout is an upper bound on the amount of time elapsed before select() > returns. It may be zero, causing select() to return immediately. (This is > useful for polling.) If timeout is NULL (no timeout), select() can block > indefinitely. > " > > This... is... confusing. > aka "what the heck is the difference between timeout zero and timeout NULL!?!?" > > > "It may be zero" should thus definitely be changed into something like > "the timeout value represented by the timeval struct may be zero" > to make sure that people grok the difference between a NULL _pointer_ and a > zero _representation_ of a struct. > > This all considering that this is indeed how select(2) works (haven't > actually verified it myself recently). It is / your understanding is correct. I've changed the wording to be something pretty similar to what you suggest. the changes will be in upstream 3.04. Cheers, Michael
