POE 1 / ActiveState Perl

avo has asked for the wisdom of the Perl Monks concerning the following question:

Hi, What would be the reason for POE to give these exceptions:

Prototype mismatch: sub POE::Kernel::F_GETFL vs () at (eval 14) line 1.
Prototype mismatch: sub POE::Kernel::F_SETFL vs () at (eval 15) line 1.

It happens simply when I type perl -MPOE

I am using ActiveState Perl. Recently updated POE to version 1.0 from a PPD found here: http://trouchelle.com/
I have the feeling I need a newer version of IO.pm. My one is 1.23

Comment on POE 1 / ActiveState Perl

Replies are listed 'Best First'.
Re: POE 1 / ActiveState Perl by Anonymous Monk on May 20, 2008 at 08:03 UTC
This bug already reported Try upgrading to POE-1.0002	[reply]
Re: POE 1 / ActiveState Perl by bingos (Vicar) on May 20, 2008 at 08:14 UTC
These are reasonably harmless warnings, but can be vaguely annoying. If you use a more modern version of ActiveState perl such as ActivePerl 5.10.0.1003, these warnings disappear. If you want a more up to date version of POE, I make PAR::Dist compatible packages available on my POE::Component::IRC page.	[reply]
Re: POE 1 / ActiveState Perl by moritz (Cardinal) on May 20, 2008 at 07:01 UTC
Such warnings usually occur if you use POE with some dependencies that are either older or newer than what the developers used. Or when the developers screwed up ;-) If nobody has a better idea, consider asking `poe-help@perl.org`.	[reply] [d/l]