DBI of event loop programming

Edit Package perl-AnyEvent

the AnyEvent manpage provides a uniform interface to various event loops.
This allows module authors to use event loop functionality without forcing
module users to use a specific event loop implementation (since more than
one event loop cannot coexist peacefully).

The interface itself is vaguely similar, but not identical to the the Event
manpage module.

Refresh
Refresh
Source Files
Filename Size Changed
AnyEvent-6.14.tar.gz 0000270405 264 KB
perl-AnyEvent.changes 0000009511 9.29 KB
perl-AnyEvent.spec 0000004597 4.49 KB
Revision 18 (latest revision is 35)
Stephan Kulow's avatar Stephan Kulow (coolo) accepted request 103773 from Stephan Kulow's avatar Stephan Kulow (coolo) (revision 18)
- updated to 6.14
     - AnyEvent::Impl::Tk was broken due to a mysterious "die" inside,
        probably an editing mistake (reported by Darin McBride).
     - AnyEvent::Util::fork_call checked for POSIX availability in the wrong way,
        causing it to fail if POSIX wasn't loaded already (analysed by Rock Power).
     - AnyEvent::Handle::push_read (line => did pass $1 directly, so
        regex-matching inside the callback would change the parameter, despite
        $1 being dynamically scoped per-block. this perl bug is now being
        worked around (testcase by Cindy Wang).
     - $! was clobbered by subsequent calls in tcp_connect, due to
        the postpone not saving/restoring it (analyzed by Richard Garnish).
     - Tk cannot create windows when tainted unless you set a title, so
        set a dummy title for AnyEvent's dummy mainwindow. How dummy.
     - escape any nonprintable/nonascii characters when stringifying
        backtraces.
      - log the reason loading an interface module fails to load at level debug.
Comments 0
openSUSE Build Service is sponsored by