note xdg <p>How about "conditions" instead of "predicates"? Also, at the expense of changing your API, it might be clearer if the functions names themselves were less like perl functions and more intuitively descriptive. </p> <ul> <li>read -> readable</li> <li>write -> writeable</li> <li>sleep -> timeout</li> <li>etc</li> </ul> <p>My thought is that since these aren't actually executed immediately, it would be better to have names that describe the activating condition rather than names that sound like an imperative.</p> <p>For documentation, I'd strongly suggest separating the perl signature from the context arguments. E.g.</p> <c> read($callback) -- context stack: $filehandle, $deadline = undef </c> <div class="pmsig"><div class="pmsig-268515"> <p>-xdg</p> <p><small><i>Code written by xdg and posted on PerlMonks is [http://creativecommons.org/licenses/publicdomain|public domain]. It is provided <b>as is</b> with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.</i></small></p> </div></div> 733676 734362