Skip Menu |

This queue is for tickets about the POE CPAN distribution.

Report information
The Basics
Id: 13197
Status: rejected
Priority: 0/
Queue: POE

People
Owner: Nobody in particular
Requestors: Leolo [...] pied.nu
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 0.3101
Fixed in: (no value)



Subject: $kernel->quit_yer_yapping();
The "run method never called" message is annoying. I don't like the solutions suggested in the FAQ. http://poe.perl.org/?POE_FAQ/run_method_never_called How about adding to following code : sub quit_yer_yapping { ${$poe_kernel->[POE::Kernel::KR_RUN]} |= POE::Kernel::KR_RUN_CALLED; } This is a method, a class method and a function and can be called 3 different ways, no waiting.
I'm unconvinced that this method is necessary. There are four ways to avoid the warning, including exiting the program with POSIX::_exit(). Why isn't one of them suitable? On Fri Jun 10 16:09:16 2005, guest wrote: Show quoted text
> The "run method never called" message is annoying. I don't like the > solutions suggested in the FAQ. > > http://poe.perl.org/?POE_FAQ/run_method_never_called > > How about adding to following code : > > sub quit_yer_yapping { > ${$poe_kernel->[POE::Kernel::KR_RUN]} |= > POE::Kernel::KR_RUN_CALLED; > } > > This is a method, a class method and a function and can be called 3 > different ways, no waiting.
From: Leolo
The 4 methods in the wiki are all work-arounds. For example, $poe_kernel->run(); before any sessions are defined must be complemented with comments in 2 places; near that line, and near the code that forks and exits, so that a maintainer or cargo-culter will get a heads up. I'm much more a fan of explicit behaviour. $poe_kernel->not_run(); near the exit() is explicit and self-documenting.
"I don't like it" remains an unconvincing argument. Unless you have an uncontrived case where this warning cannot be worked around, I'm leaving it in.