[ViewVC] Diff of: cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.173 by root, Mon Jul 21 03:47:22 2008 UTC vs.
Revision 1.180 by root, Sat Sep 6 07:00:45 2008 UTC

 The instrument to do that is called a "condition variable", so called
 because they represent a condition that must become true.
 Condition variables can be created by calling the C<< AnyEvent->condvar
 >> method, usually without arguments. The only argument pair allowed is
 C<cb>, which specifies a callback to be called when the condition variable
 becomes true, with the condition variable as the first argument (but not
 the results).
 =cut
 package AnyEvent;
 no warnings;
-use strict;
+use strict qw(vars subs);
 use Carp;
-our $VERSION = 4.22;
+our $VERSION = 4.233;
 our $MODEL;
 our $AUTOLOAD;
 our @ISA;
 package AnyEvent::Base;
 # default implementation for now and time
-use Time::HiRes ();
+BEGIN {
+   if (eval "use Time::HiRes (); time (); 1") {
+      *_time = \&Time::HiRes::time;
+      # if (eval "use POSIX (); (POSIX::times())...
+   } else {
+      *_time = \&CORE::time; # epic fail
+   }
+}
-sub time { Time::HiRes::time }
+sub time { _time }
-sub now  { Time::HiRes::time }
+sub now  { _time }
 # default implementation for ->condvar
 sub condvar {
    bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::
 # undocumented/compatibility with pre-3.4
 *broadcast = \&send;
 *wait      = \&_wait;
+=head1 ERROR AND EXCEPTION HANDLING
+In general, AnyEvent does not do any error handling - it relies on the
+caller to do that if required. The L<AnyEvent::Strict> module (see also
+the C<PERL_ANYEVENT_STRICT> environment variable, below) provides strict
+checking of all AnyEvent methods, however, which is highly useful during
+development.
+As for exception handling (i.e. runtime errors and exceptions thrown while
+executing a callback), this is not only highly event-loop specific, but
+also not in any way wrapped by this module, as this is the job of the main
+program.
+The pure perl event loop simply re-throws the exception (usually
+within C<< condvar->recv >>), the L<Event> and L<EV> modules call C<<
+$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and
+so on.
+=head1 ENVIRONMENT VARIABLES
+The following environment variables are used by this module or its
+submodules:
+=over 4
+=item C<PERL_ANYEVENT_VERBOSE>
+By default, AnyEvent will be completely silent except in fatal
+conditions. You can set this environment variable to make AnyEvent more
+talkative.
+When set to C<1> or higher, causes AnyEvent to warn about unexpected
+conditions, such as not being able to load the event model specified by
+C<PERL_ANYEVENT_MODEL>.
+When set to C<2> or higher, cause AnyEvent to report to STDERR which event
+model it chooses.
+=item C<PERL_ANYEVENT_STRICT>
+AnyEvent does not do much argument checking by default, as thorough
+argument checking is very costly. Setting this variable to a true value
+will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
+check the arguments passed to most method calls. If it finds any problems
+it will croak.
+In other words, enables "strict" mode.
+Unlike C<use strict>, it is definitely recommended ot keep it off in
+production. Keeping C<PERL_ANYEVENT_STRICT=1> in your environment while
+developing programs can be very useful, however.
+=item C<PERL_ANYEVENT_MODEL>
+This can be used to specify the event model to be used by AnyEvent, before
+auto detection and -probing kicks in. It must be a string consisting
+entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
+and the resulting module name is loaded and if the load was successful,
+used as event model. If it fails to load AnyEvent will proceed with
+auto detection and -probing.
+This functionality might change in future versions.
+For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
+could start your program like this:
+   PERL_ANYEVENT_MODEL=Perl perl ...
+=item C<PERL_ANYEVENT_PROTOCOLS>
+Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
+for IPv4 or IPv6. The default is unspecified (and might change, or be the result
+of auto probing).
+Must be set to a comma-separated list of protocols or address families,
+current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
+used, and preference will be given to protocols mentioned earlier in the
+list.
+This variable can effectively be used for denial-of-service attacks
+against local programs (e.g. when setuid), although the impact is likely
+small, as the program has to handle connection errors already-
+Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
+but support both and try to use both.  C<PERL_ANYEVENT_PROTOCOLS=ipv4>
+- only support IPv4, never try to resolve or contact IPv6
+addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
+IPv6, but prefer IPv6 over IPv4.
+=item C<PERL_ANYEVENT_EDNS0>
+Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
+for DNS. This extension is generally useful to reduce DNS traffic, but
+some (broken) firewalls drop such DNS packets, which is why it is off by
+default.
+Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
+EDNS0 in its DNS requests.
+=item C<PERL_ANYEVENT_MAX_FORKS>
+The maximum number of child processes that C<AnyEvent::Util::fork_call>
+will create in parallel.
+=back
 =head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
 This is an advanced topic that you do not normally need to use AnyEvent in
 a module. This section is only of use to event loop authors who want to
 provide AnyEvent compatibility.
 I<rxvt-unicode> also cheats a bit by not providing blocking access to
 condition variables: code blocking while waiting for a condition will
 C<die>. This still works with most modules/usages, and blocking calls must
 not be done in an interactive application, so it makes sense.
-=head1 ENVIRONMENT VARIABLES
-The following environment variables are used by this module:
-=over 4
-=item C<PERL_ANYEVENT_VERBOSE>
-By default, AnyEvent will be completely silent except in fatal
-conditions. You can set this environment variable to make AnyEvent more
-talkative.
-When set to C<1> or higher, causes AnyEvent to warn about unexpected
-conditions, such as not being able to load the event model specified by
-C<PERL_ANYEVENT_MODEL>.
-When set to C<2> or higher, cause AnyEvent to report to STDERR which event
-model it chooses.
-=item C<PERL_ANYEVENT_STRICT>
-AnyEvent does not do much argument checking by default, as thorough
-argument checking is very costly. Setting this variable to a true value
-will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
-check the arguments passed to most method calls. If it finds any problems
-it will croak.
-In other words, enables "strict" mode.
-Unlike C<use strict> it is definitely recommended ot keep it off in
-production.
-=item C<PERL_ANYEVENT_MODEL>
-This can be used to specify the event model to be used by AnyEvent, before
-auto detection and -probing kicks in. It must be a string consisting
-entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
-and the resulting module name is loaded and if the load was successful,
-used as event model. If it fails to load AnyEvent will proceed with
-auto detection and -probing.
-This functionality might change in future versions.
-For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
-could start your program like this:
-   PERL_ANYEVENT_MODEL=Perl perl ...
-=item C<PERL_ANYEVENT_PROTOCOLS>
-Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
-for IPv4 or IPv6. The default is unspecified (and might change, or be the result
-of auto probing).
-Must be set to a comma-separated list of protocols or address families,
-current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
-used, and preference will be given to protocols mentioned earlier in the
-list.
-This variable can effectively be used for denial-of-service attacks
-against local programs (e.g. when setuid), although the impact is likely
-small, as the program has to handle connection errors already-
-Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
-but support both and try to use both.  C<PERL_ANYEVENT_PROTOCOLS=ipv4>
-- only support IPv4, never try to resolve or contact IPv6
-addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
-IPv6, but prefer IPv6 over IPv4.
-=item C<PERL_ANYEVENT_EDNS0>
-Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
-for DNS. This extension is generally useful to reduce DNS traffic, but
-some (broken) firewalls drop such DNS packets, which is why it is off by
-default.
-Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
-EDNS0 in its DNS requests.
-=item C<PERL_ANYEVENT_MAX_FORKS>
-The maximum number of child processes that C<AnyEvent::Util::fork_call>
-will create in parallel.
-=back
 =head1 EXAMPLE PROGRAM
 The following program uses an I/O watcher to read data from STDIN, a timer
 to display a message once per second, and a condition variable to quit the

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.173 by root, Mon Jul 21 03:47:22 2008 UTC vs. Revision 1.180 by root, Sat Sep 6 07:00:45 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.173 by root, Mon Jul 21 03:47:22 2008 UTC vs.
Revision 1.180 by root, Sat Sep 6 07:00:45 2008 UTC