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.300 by root, Tue Dec 1 17:56:28 2009 UTC vs.
Revision 1.306 by root, Tue Dec 15 05:49:13 2009 UTC

… …
966You should check C<$AnyEvent::MODEL> before adding to this array, though: 966You should check C<$AnyEvent::MODEL> before adding to this array, though:
967if it is defined then the event loop has already been detected, and the 967if it is defined then the event loop has already been detected, and the
968array will be ignored. 968array will be ignored.
969 969
970Best use C<AnyEvent::post_detect { BLOCK }> when your application allows 970Best use C<AnyEvent::post_detect { BLOCK }> when your application allows
971it,as it takes care of these details. 971it, as it takes care of these details.
972 972
973This variable is mainly useful for modules that can do something useful 973This variable is mainly useful for modules that can do something useful
974when AnyEvent is used and thus want to know when it is initialised, but do 974when AnyEvent is used and thus want to know when it is initialised, but do
975not need to even load it by default. This array provides the means to hook 975not need to even load it by default. This array provides the means to hook
976into AnyEvent passively, without loading it. 976into AnyEvent passively, without loading it.
977
978Example: To load Coro::AnyEvent whenever Coro and AnyEvent are used
979together, you could put this into Coro (this is the actual code used by
980Coro 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 }
977 990
978=back 991=back
979 992
980=head1 WHAT TO DO IN A MODULE 993=head1 WHAT TO DO IN A MODULE
981 994
… …
1131package AnyEvent; 1144package AnyEvent;
1132 1145
1133# basically a tuned-down version of common::sense 1146# basically a tuned-down version of common::sense
1134sub common_sense { 1147sub common_sense {
1135 # from common:.sense 1.0 1148 # from common:.sense 1.0
1136 ${^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";
1137 # use strict vars subs 1150 # use strict vars subs - NO UTF-8, as Util.pm doesn't like this atm. (uts46data.pl)
1138 $^H |= 0x00000600; 1151 $^H |= 0x00000600;
1139} 1152}
1140 1153
1141BEGIN { AnyEvent::common_sense } 1154BEGIN { AnyEvent::common_sense }
1142 1155
1143use Carp (); 1156use Carp ();
1144 1157
1145our $VERSION = '5.21'; 1158our $VERSION = '5.22';
1146our $MODEL; 1159our $MODEL;
1147 1160
1148our $AUTOLOAD; 1161our $AUTOLOAD;
1149our @ISA; 1162our @ISA;
1150 1163
… …
2448it's built-in modules) are required to use it. 2461it's built-in modules) are required to use it.
2449 2462
2450That does not mean that AnyEvent won't take advantage of some additional 2463That does not mean that AnyEvent won't take advantage of some additional
2451modules if they are installed. 2464modules if they are installed.
2452 2465
2453This section epxlains which additional modules will be used, and how they 2466This section explains which additional modules will be used, and how they
2454affect AnyEvent's operation. 2467affect AnyEvent's operation.
2455 2468
2456=over 4 2469=over 4
2457 2470
2458=item L<Async::Interrupt> 2471=item L<Async::Interrupt>
… …
2524 2537
2525Most event libraries are not fork-safe. The ones who are usually are 2538Most event libraries are not fork-safe. The ones who are usually are
2526because they rely on inefficient but fork-safe C<select> or C<poll> 2539because they rely on inefficient but fork-safe C<select> or C<poll>
2527calls. Only L<EV> is fully fork-aware. 2540calls. Only L<EV> is fully fork-aware.
2528 2541
2542This means that, in general, you cannot fork and do event processing
2543in the child if a watcher was created before the fork (which in turn
2544initialises the event library).
2545
2529If you have to fork, you must either do so I<before> creating your first 2546If you have to fork, you must either do so I<before> creating your first
2530watcher OR you must not use AnyEvent at all in the child OR you must do 2547watcher OR you must not use AnyEvent at all in the child OR you must do
2531something completely out of the scope of AnyEvent. 2548something completely out of the scope of AnyEvent.
2549
2550The problem of doing event processing in the parent I<and> the child
2551is much more complicated: even for backends that I<are> fork-aware or
2552fork-safe, their behaviour is not usually what you want: fork clones all
2553watchers, that means all timers, I/O watchers etc. are active in both
2554parent and child, which is almost never what you want.
2532 2555
2533 2556
2534=head1 SECURITY CONSIDERATIONS 2557=head1 SECURITY CONSIDERATIONS
2535 2558
2536AnyEvent can be forced to load any event model via 2559AnyEvent can be forced to load any event model via

Diff Legend

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