| Name : perl-AnyEvent
| |
| Version : 5.271
| Vendor : openSUSE Build Service
|
| Release : 3.1
| Date : 2013-05-28 17:22:59
|
| Group : Development/Libraries/Perl
| Source RPM : perl-AnyEvent-5.271-3.1.src.rpm
|
| Size : 0.71 MB
| |
| Packager : (none)
| |
| Summary : AnyEvent - the DBI of event loop programming
|
Description :
AnyEvent provides an identical interface to multiple event loops. This
allows module authors to utilise an event loop without forcing module
users to use the same event loop (as only a single event loop can coexist
peacefully at any one time).
The interface itself is vaguely similar, but not identical to the Event
module.
During the first call of any watcher-creation method, the module tries
to detect the currently loaded event loop by probing whether one of the
following modules is already loaded: EV,
Event, Glib, AnyEvent::Impl::Perl, Tk, Event::Lib, Qt,
POE. The first one found is used. If none are found, the module tries
to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl
adaptor should always succeed) in the order given. The first one that can
be successfully loaded will be used. If, after this, still none could be
found, AnyEvent will fall back to a pure-perl event loop, which is not
very efficient, but should work everywhere.
Because AnyEvent first checks for modules that are already loaded, loading
an event model explicitly before first using AnyEvent will likely make
that model the default. For example:
use Tk;
use AnyEvent;
The *likely* means that, if any module loads another event model and
starts using it, all bets are off. Maybe you should tell their authors to
use AnyEvent so their modules work together with others seamlessly...
The pure-perl implementation of AnyEvent is called
\"AnyEvent::Impl::Perl\". Like other event modules you can load it
explicitly and enjoy the high availability of that event loop :)
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/home:/csbuild:/Perl/SLE_10_SDK/noarch |
