use Perl

• Er, separate process? (Score:1)

  by jjore (6662)

  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."
  • Re:Er, separate process? (Score:1)

    by Alias (5735) on 2006.10.04 19:10 (#50769) Homepage Journal

    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.
    
    

    Reply to This

    Parent

    • Re: (Score:1)

      by jjore (6662)

      IPC::Open3 isn't sane everywhere? Drat. People have been recommending it in my presence lately and I figured it was ok.
      
      Oh well. :-/
      • Re: (Score:1)

        by Alias (5735)

        You might be thinking of IPC::Run3, which is most certainly sane everywhere.