Subject: | Remnants of TRACE_STATISTICS found :( |
Hello,
While looking at POE::Loop::Glib and trying to get a new release out of the door (about time, ha!) I was futzing around with things and tried to enable POE_TRACE_DEFAULT=1 and, kaboom!
Can't locate object method "_data_stat_add" via package "POE::Kernel" at /usr/local/share/perl/5.18.2/POE/Loop/Glib.pm line 178.
I then investigated a bit and found out that POE::Loop::Glib was behind times! In commit cde579c3147bf4151a8454f0791f457d190bca84, rcaputo exorcised POE::Resource::Statistics from POE. While POE itself is bug-free, I decided to grep the rest of CPAN and found this:
http://grep.cpan.me/?q=_data_stat_add
distros with a hit: POE::XS::Loop::EPoll/Poll, POE::Loop::Prima/Event/Gtk/Glib/EV
http://grep.cpan.me/?q=TRACE_STATISTICS
distros with a hit: POE::XS::Loop::EPoll/Poll, POE::Loop::Prima/Glib/Gtk/EV/Event, POE::Component::SSLify, POE::Devel::ProcAlike, App::Context::POE::Server
You will note that POE itself got a hit for TRACE_STATISTICS in t/90_regression/tracing-sane-exit.t but that is to be expected...
This means anyone using those loops will not be able to run if tracing is enabled! I'll fix my dists (/me smacks myself!) and is it sensible for me to make tickets/pull requests for the rest of the loops/modules impacted? I probably missed something so I would prefer your approval before bothering other authors, ha! Thanks again for looking into this :)
--
~Apocalypse