Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It has *got* to be easier to start your POE process in a child with IPC::Open3 or IPC::Run than this thing you've invented.

    Seriously. Or just do a "Oops! We're on Win32. Use CreateProcess() instead."
    • Sounds great, wrap all that platform abstraction up into something something simple that actually works everywhere, and then I'll look into it. It would be really nice if IPC::Open3 was finally sane everywhere.

      Further, how do you handle debugging?

      I mean, if you are just killing your process, what's the point?

      With Test::POE::Stopping, we only need to add a few minor enhancements and we can start getting it to not only say that it won't end, but spit out full diagnositics of the specifics of the POE resources (aliases, handles, alarms, etc) that are actually leaking.

      This takes it into another realm of usefulness entirely.

      Just killing off the process doesn't give you that.

      • IPC::Open3 isn't sane everywhere? Drat. People have been recommending it in my presence lately and I figured it was ok.

        Oh well. :-/