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.

use Perl

All the Perl that's Practical to Extract and Report

We call him "Dances with Halting Problem" More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

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: (Score:1)
  
  by Alias (5735)
  
  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
  - 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:Er, separate process? (Score:1)
      
      by Alias (5735) on 2006.10.05 3:22 (#50776) Homepage Journal
      
      You might be thinking of IPC::Run3, which is most certainly sane everywhere.
      
      Reply to This
      
      Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.