I wanted to build an awesome place for people to discuss module specific issues, but I don't have any more time for this, and there are much better places to discuss Perl-related issues. I'd recommend asking your question on Stack Overflow or on Perl Monks.
If you are looking for a Perl tutorial or Perl-related news, I hope these links will serve you well.
threads-shared
Posted on 2012-08-23 16:42:14.316951-07 by p120ph37
cond_timedwait's ABS_TIMEOUT is not explained well enough.
It is not explicitly stated that ABS_TIMEOUT is a value in unix epoch seconds - the reader is left to surmise this from the examples and the explanation about not recalculating it. I missed this distinction on first reading and instead assumed a behavior similar to the timeout of the "select" statement. It would be good to clarify the explanation a little.
Direct Responses: 13788 | Write a response
Posted on 2012-08-24 05:42:21.25547-07 by jdhedden in response to 13786
Re: cond_timedwait's ABS_TIMEOUT is not explained well enough.
Thanks for the feedback. I'm going to change the text to:
=item cond_timedwait CONDVAR, ABS_TIMEOUT, LOCKVAR In its two-argument form, C<cond_timedwait> takes a B<locked> variable and an absolute timeout in I<epoch> seconds (see L<time() in perlfunc|perlfunc/time> for more) as parameters, unlocks the variable, and blocks until the timeout is reached or another thread signals the variable. A false value is returned if the timeout is reached, and a true value otherwise. In either case, the variable is re-locked upon return.
This should make it more clear. This will go out with the next release of threads::shared (which will come not later than the release of Perl 5.18.0).
Direct Responses: Write a response