[ViewVC] Diff of: cvs/Coro/Event/Event.pm

Comparing Coro/Event/Event.pm (file contents):
Revision 1.35 by root, Wed Feb 1 23:59:41 2006 UTC vs.
Revision 1.38 by root, Mon Nov 20 20:14:02 2006 UTC

 watcher constructors from Event is that you do not specify a callback
 function - it will be managed by this module.
 Your application should just create all necessary coroutines and then call
 Coro::Event::loop.
+Please note that even programs or modules (such as
+L<Coro::Handle|Coro::Handle>) that use "traditional"
+event-based/continuation style will run more efficient with this module
+then when using only Event.
 =over 4
 =cut
 This is the version of C<loop> you should use instead of C<Event::loop>
 when using this module - it will ensure correct scheduling in the presence
 of events.
-=begin comment
-Unlike loop's counterpart it is not an error when no watchers are active -
-loop silently returns in this case, as if unloop(undef) were called.
-=end comment
-=cut
-# no longer do something special - it's done internally now
-#sub loop(;$) {
-#   #local $Coro::idle = $Coro::current;
-#   #Coro::schedule; # become idle task, which is implicitly ready
-#   &Event::loop;
-#}
 =item unloop([$result])
 Same as Event::unloop (provided here for your convinience only).
 =cut
 $Coro::idle = new Coro sub {
    while () {
+      Coro::schedule;
       Event::one_event; # inefficient
-      Coro::schedule;
    }
 };
 # provide hooks for Coro::Timer
    };
 }
 1;
+=back
 =head1 AUTHOR
  Marc Lehmann <schmorp@schmorp.de>
  http://home.schmorp.de/

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