| 1 | =head1 NAME |
1 | =head1 NAME |
| 2 | |
2 | |
| 3 | AnyEvent - events independent of event loop implementation |
3 | AnyEvent - events independent of event loop implementation |
| 4 | |
4 | |
| 5 | EV, Event, Glib, Tk, Perl, Event::Lib, Qt and POE are various supported |
5 | EV, Event, Glib, Tk, Perl, Event::Lib, Irssi, IO::Async, Qt and POE are |
| 6 | event loops. |
6 | various supported event loops/environments. |
| 7 | |
7 | |
| 8 | =head1 SYNOPSIS |
8 | =head1 SYNOPSIS |
| 9 | |
9 | |
| 10 | use AnyEvent; |
10 | use AnyEvent; |
| 11 | |
11 | |
| … | |
… | |
| 47 | |
47 | |
| 48 | There is a mailinglist for discussing all things AnyEvent, and an IRC |
48 | There is a mailinglist for discussing all things AnyEvent, and an IRC |
| 49 | channel, too. |
49 | channel, too. |
| 50 | |
50 | |
| 51 | See the AnyEvent project page at the B<Schmorpforge Ta-Sa Software |
51 | See the AnyEvent project page at the B<Schmorpforge Ta-Sa Software |
| 52 | Respository>, at L<http://anyevent.schmorp.de>, for more info. |
52 | Repository>, at L<http://anyevent.schmorp.de>, for more info. |
| 53 | |
53 | |
| 54 | =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) |
54 | =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) |
| 55 | |
55 | |
| 56 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
56 | Glib, POE, IO::Async, Event... CPAN offers event models by the dozen |
| 57 | nowadays. So what is different about AnyEvent? |
57 | nowadays. So what is different about AnyEvent? |
