ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent/lib/AnyEvent.pm
(Generate patch)

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.291 by root, Thu Sep 3 13:59:20 2009 UTC vs.
Revision 1.298 by root, Tue Nov 24 05:48:06 2009 UTC

… …
363might affect timers and time-outs. 363might affect timers and time-outs.
364 364
365When this is the case, you can call this method, which will update the 365When this is the case, you can call this method, which will update the
366event loop's idea of "current time". 366event loop's idea of "current time".
367 367
368A typical example would be a script in a web server (e.g. C<mod_perl>) -
369when mod_perl executes the script, then the event loop will have the wrong
370idea about the "current time" (being potentially far in the past, when the
371script ran the last time). In that case you should arrange a call to C<<
372AnyEvent->now_update >> each time the web server process wakes up again
373(e.g. at the start of your script, or in a handler).
374
368Note that updating the time I<might> cause some events to be handled. 375Note that updating the time I<might> cause some events to be handled.
369 376
370=back 377=back
371 378
372=head2 SIGNAL WATCHERS 379=head2 SIGNAL WATCHERS
… …
395correctly. 402correctly.
396 403
397Example: exit on SIGINT 404Example: exit on SIGINT
398 405
399 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 }); 406 my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
407
408=head3 Restart Behaviour
409
410While restart behaviour is up to the event loop implementation, most will
411not restart syscalls (that includes L<Async::Interrupt> and AnyEvent's
412pure perl implementation).
413
414=head3 Safe/Unsafe Signals
415
416Perl signals can be either "safe" (synchronous to opcode handling) or
417"unsafe" (asynchronous) - the former might get delayed indefinitely, the
418latter might corrupt your memory.
419
420AnyEvent signal handlers are, in addition, synchronous to the event loop,
421i.e. they will not interrupt your running perl program but will only be
422called as part of the normal event handling (just like timer, I/O etc.
423callbacks, too).
400 424
401=head3 Signal Races, Delays and Workarounds 425=head3 Signal Races, Delays and Workarounds
402 426
403Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching 427Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching
404callbacks to signals in a generic way, which is a pity, as you cannot 428callbacks to signals in a generic way, which is a pity, as you cannot
… …
1116 1140
1117BEGIN { AnyEvent::common_sense } 1141BEGIN { AnyEvent::common_sense }
1118 1142
1119use Carp (); 1143use Carp ();
1120 1144
1121our $VERSION = '5.12'; 1145our $VERSION = '5.21';
1122our $MODEL; 1146our $MODEL;
1123 1147
1124our $AUTOLOAD; 1148our $AUTOLOAD;
1125our @ISA; 1149our @ISA;
1126 1150
1127our @REGISTRY; 1151our @REGISTRY;
1128
1129our $WIN32;
1130 1152
1131our $VERBOSE; 1153our $VERBOSE;
1132 1154
1133BEGIN { 1155BEGIN {
1134 eval "sub WIN32(){ " . (($^O =~ /mswin32/i)*1) ." }"; 1156 eval "sub WIN32(){ " . (($^O =~ /mswin32/i)*1) ." }";
… …
1386our ($SIG_COUNT, $SIG_TW); 1408our ($SIG_COUNT, $SIG_TW);
1387 1409
1388sub _signal_exec { 1410sub _signal_exec {
1389 $HAVE_ASYNC_INTERRUPT 1411 $HAVE_ASYNC_INTERRUPT
1390 ? $SIGPIPE_R->drain 1412 ? $SIGPIPE_R->drain
1391 : sysread $SIGPIPE_R, my $dummy, 9; 1413 : sysread $SIGPIPE_R, (my $dummy), 9;
1392 1414
1393 while (%SIG_EV) { 1415 while (%SIG_EV) {
1394 for (keys %SIG_EV) { 1416 for (keys %SIG_EV) {
1395 delete $SIG_EV{$_}; 1417 delete $SIG_EV{$_};
1396 $_->() for values %{ $SIG_CB{$_} || {} }; 1418 $_->() for values %{ $SIG_CB{$_} || {} };

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines