Re: POE::XS::Loop::Poll (again)

David Davis (Mon 08/04/08 12:31):
>    Look at $poe_kernel->poe_kernel_loop();
> 
>    David Davis
>    a** Software Engineer
>    http://xant.us/
> 
>    On Mon, Aug 4, 2008 at 08:24, hideo <[email protected]> wrote:
> 
>      Tony Cook (Mon 08/04/08 22:39):
>      > In the spirit of POE::XS::Queue::Array, I've released
>      > POE::XS::Loop::Poll, an implementation of POE's event loop written in
>      > C.
>      >
>      > I haven't done any speed benchmarks (or found any), but I expect it to
>      > be slightly lower overhead than the built-in POE::Loop::Select.
>      >
>      > Of course, without a benchmark it can only be a guess.
>      >
>      > Unfortunately, due to an apparent limitation with Darwin's poll(2)
>      > implementation you can't use this loop with ttys under Darwin.[1]
>      >
>      > The nopaste bot on irc.perl.org has been using POE::XS::Loop::Poll
>      > since the 0.005 release.
>      >
>      > Tony
>      >
>      > [1] From poll(2):
>      >   BUGS
>      >      The poll() system call currently does not support devices.
>      > which is kind of vague, but calls result in POLLNVAL set for the tty
>      fds.
> 
>      Does API::Peek report this loop properly?  I can't seem to verify that
>      POE is using XS::Loop::Poll or not.
> 
>      Zach

Found the problem. I had use'ed POE::API::Peek before the recommended 
POE::Kernel statement.  Reversing them produces the correct output in
both your statement as well as which_poll().

Zach