Joshua N Pritikin wrote:
>Note: There is no implicit check for unreified asynchronous events.
>There is an obscure situation where this can make a difference. If
>you are starting additional signal watchers for the same signal then
>such watchers may see signals which were actually received prior
On Mon, 2004-11-29 at 09:51 +, Zefram wrote:
> #!/usr/bin/perl
> use warnings;
> use strict;
> use Event;
> my $w;
> $w = Event->signal(signal => "USR1", cb => sub {
> print "handler got hits=", $_[0]->hits, "\n";
> kill "USR1" => 0;
> $w->stop;
> $w->start;
> });
> kill
Joshua N Pritikin wrote:
>Huh? Can you prove this? If so then it's a bug.
It's something we discussed some months ago. You said it wasn't a
bug, though I said it was. I also said that the similar problem with
$w->pending() was a bug. You pointed at Event::_queue_pending() as the
way for me to
On Sun, 2004-11-28 at 16:45 +, Zefram wrote:
> @@ -166,10 +217,16 @@
>
> Activate the watcher. Watchers refuse to C without
> sufficient configuration information to generate events. Constructors
> -always invoke C unless the C1> option is requested.
> +always invoke C unless the C<< park
