… | |
… | |
402 | correctly. |
402 | correctly. |
403 | |
403 | |
404 | Example: exit on SIGINT |
404 | Example: exit on SIGINT |
405 | |
405 | |
406 | 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 | |
|
|
410 | While restart behaviour is up to the event loop implementation, most will |
|
|
411 | not restart syscalls (that includes L<Async::Interrupt> and AnyEvent's |
|
|
412 | pure perl implementation). |
|
|
413 | |
|
|
414 | =head3 Safe/Unsafe Signals |
|
|
415 | |
|
|
416 | Perl signals can be either "safe" (synchronous to opcode handling) or |
|
|
417 | "unsafe" (asynchronous) - the former might get delayed indefinitely, the |
|
|
418 | latter might corrupt your memory. |
|
|
419 | |
|
|
420 | AnyEvent signal handlers are, in addition, synchronous to the event loop, |
|
|
421 | i.e. they will not interrupt your running perl program but will only be |
|
|
422 | called as part of the normal event handling (just like timer, I/O etc. |
|
|
423 | callbacks, too). |
407 | |
424 | |
408 | =head3 Signal Races, Delays and Workarounds |
425 | =head3 Signal Races, Delays and Workarounds |
409 | |
426 | |
410 | Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching |
427 | Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching |
411 | callbacks to signals in a generic way, which is a pity, as you cannot |
428 | callbacks to signals in a generic way, which is a pity, as you cannot |
… | |
… | |
949 | You should check C<$AnyEvent::MODEL> before adding to this array, though: |
966 | You should check C<$AnyEvent::MODEL> before adding to this array, though: |
950 | if it is defined then the event loop has already been detected, and the |
967 | if it is defined then the event loop has already been detected, and the |
951 | array will be ignored. |
968 | array will be ignored. |
952 | |
969 | |
953 | Best use C<AnyEvent::post_detect { BLOCK }> when your application allows |
970 | Best use C<AnyEvent::post_detect { BLOCK }> when your application allows |
954 | it,as it takes care of these details. |
971 | it, as it takes care of these details. |
955 | |
972 | |
956 | This variable is mainly useful for modules that can do something useful |
973 | This variable is mainly useful for modules that can do something useful |
957 | when AnyEvent is used and thus want to know when it is initialised, but do |
974 | when AnyEvent is used and thus want to know when it is initialised, but do |
958 | not need to even load it by default. This array provides the means to hook |
975 | not need to even load it by default. This array provides the means to hook |
959 | into AnyEvent passively, without loading it. |
976 | into AnyEvent passively, without loading it. |
|
|
977 | |
|
|
978 | Example: To load Coro::AnyEvent whenever Coro and AnyEvent are used |
|
|
979 | together, you could put this into Coro (this is the actual code used by |
|
|
980 | Coro to accomplish this): |
|
|
981 | |
|
|
982 | if (defined $AnyEvent::MODEL) { |
|
|
983 | # AnyEvent already initialised, so load Coro::AnyEvent |
|
|
984 | require Coro::AnyEvent; |
|
|
985 | } else { |
|
|
986 | # AnyEvent not yet initialised, so make sure to load Coro::AnyEvent |
|
|
987 | # as soon as it is |
|
|
988 | push @AnyEvent::post_detect, sub { require Coro::AnyEvent }; |
|
|
989 | } |
960 | |
990 | |
961 | =back |
991 | =back |
962 | |
992 | |
963 | =head1 WHAT TO DO IN A MODULE |
993 | =head1 WHAT TO DO IN A MODULE |
964 | |
994 | |
… | |
… | |
1114 | package AnyEvent; |
1144 | package AnyEvent; |
1115 | |
1145 | |
1116 | # basically a tuned-down version of common::sense |
1146 | # basically a tuned-down version of common::sense |
1117 | sub common_sense { |
1147 | sub common_sense { |
1118 | # from common:.sense 1.0 |
1148 | # from common:.sense 1.0 |
1119 | ${^WARNING_BITS} = "\xfc\x3f\xf3\x00\x0f\xf3\xcf\xc0\xf3\xfc\x33\x03"; |
1149 | ${^WARNING_BITS} = "\xfc\x3f\x33\x00\x0f\xf3\xcf\xc0\xf3\xfc\x33\x00"; |
1120 | # use strict vars subs |
1150 | # use strict vars subs |
1121 | $^H |= 0x00000600; |
1151 | $^H |= 0x00000600; |
1122 | } |
1152 | } |
1123 | |
1153 | |
1124 | BEGIN { AnyEvent::common_sense } |
1154 | BEGIN { AnyEvent::common_sense } |
1125 | |
1155 | |
1126 | use Carp (); |
1156 | use Carp (); |
1127 | |
1157 | |
1128 | our $VERSION = '5.202'; |
1158 | our $VERSION = '5.22'; |
1129 | our $MODEL; |
1159 | our $MODEL; |
1130 | |
1160 | |
1131 | our $AUTOLOAD; |
1161 | our $AUTOLOAD; |
1132 | our @ISA; |
1162 | our @ISA; |
1133 | |
1163 | |
1134 | our @REGISTRY; |
1164 | our @REGISTRY; |
1135 | |
|
|
1136 | our $WIN32; |
|
|
1137 | |
1165 | |
1138 | our $VERBOSE; |
1166 | our $VERBOSE; |
1139 | |
1167 | |
1140 | BEGIN { |
1168 | BEGIN { |
1141 | eval "sub WIN32(){ " . (($^O =~ /mswin32/i)*1) ." }"; |
1169 | eval "sub WIN32(){ " . (($^O =~ /mswin32/i)*1) ." }"; |
… | |
… | |
2433 | it's built-in modules) are required to use it. |
2461 | it's built-in modules) are required to use it. |
2434 | |
2462 | |
2435 | That does not mean that AnyEvent won't take advantage of some additional |
2463 | That does not mean that AnyEvent won't take advantage of some additional |
2436 | modules if they are installed. |
2464 | modules if they are installed. |
2437 | |
2465 | |
2438 | This section epxlains which additional modules will be used, and how they |
2466 | This section explains which additional modules will be used, and how they |
2439 | affect AnyEvent's operetion. |
2467 | affect AnyEvent's operation. |
2440 | |
2468 | |
2441 | =over 4 |
2469 | =over 4 |
2442 | |
2470 | |
2443 | =item L<Async::Interrupt> |
2471 | =item L<Async::Interrupt> |
2444 | |
2472 | |
… | |
… | |
2449 | catch the signals) with some delay (default is 10 seconds, look for |
2477 | catch the signals) with some delay (default is 10 seconds, look for |
2450 | C<$AnyEvent::MAX_SIGNAL_LATENCY>). |
2478 | C<$AnyEvent::MAX_SIGNAL_LATENCY>). |
2451 | |
2479 | |
2452 | If this module is available, then it will be used to implement signal |
2480 | If this module is available, then it will be used to implement signal |
2453 | catching, which means that signals will not be delayed, and the event loop |
2481 | catching, which means that signals will not be delayed, and the event loop |
2454 | will not be interrupted regularly, which is more efficient (And good for |
2482 | will not be interrupted regularly, which is more efficient (and good for |
2455 | battery life on laptops). |
2483 | battery life on laptops). |
2456 | |
2484 | |
2457 | This affects not just the pure-perl event loop, but also other event loops |
2485 | This affects not just the pure-perl event loop, but also other event loops |
2458 | that have no signal handling on their own (e.g. Glib, Tk, Qt). |
2486 | that have no signal handling on their own (e.g. Glib, Tk, Qt). |
2459 | |
2487 | |
… | |
… | |
2509 | |
2537 | |
2510 | Most event libraries are not fork-safe. The ones who are usually are |
2538 | Most event libraries are not fork-safe. The ones who are usually are |
2511 | because they rely on inefficient but fork-safe C<select> or C<poll> |
2539 | because they rely on inefficient but fork-safe C<select> or C<poll> |
2512 | calls. Only L<EV> is fully fork-aware. |
2540 | calls. Only L<EV> is fully fork-aware. |
2513 | |
2541 | |
|
|
2542 | This means that, in general, you cannot fork and do event processing |
|
|
2543 | in the child if a watcher was created before the fork (which in turn |
|
|
2544 | initialises the event library). |
|
|
2545 | |
2514 | If you have to fork, you must either do so I<before> creating your first |
2546 | If you have to fork, you must either do so I<before> creating your first |
2515 | watcher OR you must not use AnyEvent at all in the child OR you must do |
2547 | watcher OR you must not use AnyEvent at all in the child OR you must do |
2516 | something completely out of the scope of AnyEvent. |
2548 | something completely out of the scope of AnyEvent. |
|
|
2549 | |
|
|
2550 | The problem of doing event processing in the parent I<and> the child |
|
|
2551 | is much more complicated: even for backends that I<are> fork-aware or |
|
|
2552 | fork-safe, their behaviour is not usually what you want: fork clones all |
|
|
2553 | watchers, that means all timers, I/O watchers etc. are active in both |
|
|
2554 | parent and child, which is almost never what you want. |
2517 | |
2555 | |
2518 | |
2556 | |
2519 | =head1 SECURITY CONSIDERATIONS |
2557 | =head1 SECURITY CONSIDERATIONS |
2520 | |
2558 | |
2521 | AnyEvent can be forced to load any event model via |
2559 | AnyEvent can be forced to load any event model via |