On Mon, Feb 17, 2003 at 07:02:41PM -0500, Wiggins d'Anconia wrote:
>
> Rocco Caputo wrote:
> >On Wed, Feb 12, 2003 at 08:38:25AM +1100, [EMAIL PROTECTED] wrote:
> >
>
> >
> >It's a valid interpretation of ErrorEvent, but it's not the way
> >POE::Wheel::Run was written.
> >
> >StdoutEvent, StderrE
Rocco Caputo wrote:
On Wed, Feb 12, 2003 at 08:38:25AM +1100, [EMAIL PROTECTED] wrote:
It's a valid interpretation of ErrorEvent, but it's not the way
POE::Wheel::Run was written.
StdoutEvent, StderrEvent, and ErrorEvent refer to the pipes that
attach the parent and child processes. The f
On Wed, Feb 12, 2003 at 08:38:25AM +1100, [EMAIL PROTECTED] wrote:
> > That output indicates ErrorEvent has been triggered twice. The first
> > time when the child process closes STDERR, and the second time when it
> > closes STDOUT. I added some extra output to the sample code:
>
> Based upon y
sential and Direct Mail Development
Hermes Precisa Australia (Victoria)
Phone : (03) 9217-5501
Email : [EMAIL PROTECTED]
-Original Message-
From: Rocco Caputo [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 12:10 AM
To: [EMAIL PROTECTED]
Subject: Re: POE::Wheel::Run ErrorEvent
On Tue, Feb 11, 2003 at 02:05:55PM +1100, [EMAIL PROTECTED] wrote:
> > 2. I am surprised that ErrorEvent is not triggered in that case. Are
> > you using POE 0.25? If there is a problem in Wheel::Run, it would
> > help greatly if you could submit a test case that reproduces it.
>
> I was running
workspace/dev/perllibs"
PERL5LIBS="/users/rc6286/workspace/dev/perllibs"
@INC:
/users/rc6286/workspace/dev/perllibs/sun4-solaris
/users/rc6286/workspace/dev/perllibs
/usr/perl5/5.00503/sun4-solari
On Tue, Feb 11, 2003 at 11:05:48AM +1100, [EMAIL PROTECTED] wrote:
> I seem to be having an ErrorEvent triggered within POE::Wheel::Run upon the
> end of the input from STDERR and STDOUT. eg.
>
> sub _error {
> my ( $syscall, $errno, $error, $id, $handle ) = @_[ ARG0 .. ARG4 ];
> print Du
