--- AnyEvent/lib/AnyEvent.pm 2011/08/25 03:08:48 1.373 +++ AnyEvent/lib/AnyEvent.pm 2011/08/25 23:20:17 1.377 @@ -1055,11 +1055,17 @@ Log the given C<$msg> at the given C<$level>. -Loads AnyEvent::Log on first use and calls C - -consequently, look at the L documentation for details. +If L is not loaded then this function makes a simple test +to see whether the message will be logged. If the test succeeds it will +load AnyEvent::Log and call C - consequently, look at +the L documentation for details. + +If the test fails it will simply return. If you want to sprinkle loads of logging calls around your code, consider -creating a logger callback with the C function. +creating a logger callback with the C function, +which can reduce typing, codesize and can reduce the logging overhead +enourmously. =back @@ -1162,35 +1168,31 @@ the curious, IGS is the International Go Server and FCP is the Freenet Client Protocol). -=item L +=item L -Here be danger! +Truly asynchronous (as opposed to non-blocking) I/O, should be in the +toolbox of every event programmer. AnyEvent::AIO transparently fuses +L and AnyEvent together, giving AnyEvent access to event-based +file I/O, and much more. -As Pauli would put it, "Not only is it not right, it's not even wrong!" - -there are so many things wrong with AnyEvent::Handle::UDP, most notably -its use of a stream-based API with a protocol that isn't streamable, that -the only way to improve it is to delete it. - -It features data corruption (but typically only under load) and general -confusion. On top, the author is not only clueless about UDP but also -fact-resistant - some gems of his understanding: "connect doesn't work -with UDP", "UDP packets are not IP packets", "UDP only has datagrams, not -packets", "I don't need to implement proper error checking as UDP doesn't -support error checking" and so on - he doesn't even understand what's -wrong with his module when it is explained to him. +=item L + +AnyEvent is good for non-blocking stuff, but it can't detect file or +path changes (e.g. "watch this directory for new files", "watch this +file for changes"). The L module promises to +do just that in a portbale fashion, supporting inotify on GNU/Linux and +some weird, without doubt broken, stuff on OS X to monitor files. It can +fall back to blocking scans at regular intervals transparently on other +platforms, so it's about as portable as it gets. + +(I haven't used it myself, but I haven't heard anybody complaining about +it yet). =item L Executes L requests asynchronously in a proxy process for you, notifying you in an event-based way when the operation is finished. -=item L - -Truly asynchronous (as opposed to non-blocking) I/O, should be in the -toolbox of every event programmer. AnyEvent::AIO transparently fuses -L and AnyEvent together, giving AnyEvent access to event-based -file I/O, and much more. - =item L A simple embedded webserver. @@ -1201,7 +1203,19 @@ =item L -Has special support for AnyEvent via L. +Has special support for AnyEvent via L, which allows you +to simply invert the flow control - don't call us, we will call you: + + async { + Coro::AnyEvent::sleep 5; # creates a 5s timer and waits for it + print "5 seconds later!\n"; + + Coro::AnyEvent::readable *STDIN; # uses an I/O watcher + my $line = ; # works for ttys + + AnyEvent::HTTP::http_get "url", Coro::rouse_cb; + my ($body, $hdr) = Coro::rouse_wait; + }; =back @@ -1293,12 +1307,14 @@ } sub log($$;@) { - # only load the bug bloated module when we actually are about to log something - if ($_[0] <= $VERBOSE) { + # only load the big bloated module when we actually are about to log something + if ($_[0] <= $VERBOSE) { # also catches non-numeric levels(!) require AnyEvent::Log; # AnyEvent::Log overwrites this function goto &log; } + + 0 # not logged } if (length $ENV{PERL_ANYEVENT_LOG}) { @@ -1373,7 +1389,7 @@ AnyEvent::log 7 => "loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it."; $MODEL = $model; } else { - AnyEvent::log warn => "unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@"; + AnyEvent::log 5 => "unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@"; } } @@ -1561,18 +1577,17 @@ eval q{ # poor man's autoloading {} # probe for availability of Time::HiRes if (eval "use Time::HiRes (); Time::HiRes::time (); 1") { - AnyEvent::log 8 => "AnyEvent: using Time::HiRes for sub-second timing accuracy." - if $AnyEvent::VERBOSE >= 8; *time = sub { Time::HiRes::time () }; *AE::time = \& Time::HiRes::time ; + *now = \&time; + AnyEvent::log 8 => "AnyEvent: using Time::HiRes for sub-second timing accuracy."; # if (eval "use POSIX (); (POSIX::times())... } else { - AnyEvent::log critical => "using built-in time(), WARNING, no sub-second resolution!"; *time = sub { CORE::time }; *AE::time = sub (){ CORE::time }; + *now = \&time; + AnyEvent::log 3 => "using built-in time(), WARNING, no sub-second resolution!"; } - - *now = \&time; }; die if $@; @@ -1675,15 +1690,13 @@ eval q{ # poor man's autoloading {} # probe for availability of Async::Interrupt if (_have_async_interrupt) { - AnyEvent::log 8 => "using Async::Interrupt for race-free signal handling." - if $AnyEvent::VERBOSE >= 8; + AnyEvent::log 8 => "using Async::Interrupt for race-free signal handling."; $SIGPIPE_R = new Async::Interrupt::EventPipe; $SIG_IO = AE::io $SIGPIPE_R->fileno, 0, \&_signal_exec; } else { - AnyEvent::log 8 => "using emulated perl signal handling with latency timer." - if $AnyEvent::VERBOSE >= 8; + AnyEvent::log 8 => "using emulated perl signal handling with latency timer."; if (AnyEvent::WIN32) { require AnyEvent::Util; @@ -2035,14 +2048,15 @@ you should have a look at C, which allows much more complex specifications. -When set to C<5> or higher, causes AnyEvent to warn about unexpected +When set to C<5> or higher (warn), causes AnyEvent to warn about unexpected conditions, such as not being able to load the event model specified by -C. +C, or a guard callback throwing an exception - this +is the minimum recommended level. -When set to C<7> or higher, cause AnyEvent to report to STDERR which event -model it chooses. +When set to C<7> or higher (info), cause AnyEvent to report which event model it +chooses. -When set to C<8> or higher, then AnyEvent will report extra information on +When set to C<8> or higher (debug), then AnyEvent will report extra information on which optional modules it loads and how it implements certain features. =item C @@ -2055,6 +2069,9 @@ For the rather extensive details, see L. +This variable is evaluated when AnyEvent (or L) is loaded, +so will take effect even before AnyEvent has initialised itself. + Note that specifying this environment variable causes the L module to be loaded, while C does not, so only using the latter saves a few hundred kB of memory until the first message @@ -2082,7 +2099,7 @@ C<$$> by the process pid) and an C is bound on that port. The shell object is saved in C<$AnyEvent::Debug::SHELL>. -This takes place when the first watcher is created. +This happens when the first watcher is created. For example, to bind a debug shell on a unix domain socket in F<< /tmp/debug.sock >>, you could use this: