Event::loop warning and Event-0.84

[email protected] (( Marc) (A.) (Lehmann ))
Newsgroups perl.loop
Message-ID <[email protected]>
three issue sin one mail, sorry, I feel dirty ;)

First of all, could I ask for an Event-0.84 release? I really think the
endless-loop bug warrants a new release, even if it's the only fix (yes,
it happens only with non-blocking I/O, but what use has event without
non-blocking I/O?).

Anyway, my problem: loop displays the warning:

   Event: loop without active watchers ...

when no watchers are active. When programming with coroutines this is a
very common case (it means all processes have ended), and I'd like a way
to catch this message (I provide my own "loop" function anyways). For
various reasons I don't want to overwrite SIG{__WARN__} (this should never
be done in a general-purpose library ;).

However, I can't see a way to do this shot of walking all watchers and
chekcing for active'ness.

And last not least, in Coro-0.13 (just released) it's possible to make LWP
and similar libraries 100% non-blocking (including connect) by overwriting
IO::Socket::INET::new (ok, it's the first release and I only tested it
with LWP and http-requests ;) like this:

   use Coro::Socket; use IO::Socket::INET;
   sub IO::Socket::INET::new { shift; new Coro::Socket @_ };

-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       [email protected]      |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.