Programs that use POE may have their warnings suppressed by a couple
BEGIN blocks in POE::Session. These blocks globally set $^W=0, which
globally disables warnings. This may be happening right now in your
own code.
I've recently committed a fix, so please be prepared for new warnings
after upgrading to POE 1.004 (not released yet) or later.
You can get a jump on this by re-enabling warnings after loading
POE::Session and POE:
use POE;
BEGIN { $^W = 1 }
This should allow any warnings to surface now, so you can address them
before POE 1.004 is released. Please remember to remove the BEGIN
block when you're done.
Another option is to test the latest bleeding-edge POE from its
repository. This method has will also silence some warnings that were
found in POE itself after the $^W fix:
cd /home/me/dev
svn co https://poe.svn.sourceforge.net/svnroot/poe/trunk/poe poe
export PERL5LIB=/home/me/dev/poe/lib
/path/to/my/program
Sorry for the inconvenience.
--
Rocco Caputo - [email protected]
