Re: win32 testers? [Re: child watch source (was: exception trap in key snooper callback)]

["spicy jack" <elspicyjack gmail com>]

Forgot to run the original script:

C:\camelbox\.cpan\build\Glib-1.183-d6CHhp>perl snooper-error.pl
snooper
snooper error

appears after about 20 or 30 seconds.

Thanks,

Brian

On Sun, Sep 7, 2008 at 11:45 PM, spicy jack <elspicyjack gmail com> wrote:
> On Sun, Sep 7, 2008 at 12:13 PM, muppet <scott asofyet org> wrote:
> > On Aug 26, 2008, at 8:29 PM, Kevin Ryde wrote:
> > > Below, with a couple of lines to hopefully skip if fork() isn't a real
> > > fork, but I've got no way to try that.
> >
> > Any win32 users willing to try out this patchset?
>
> When the fork() function is called, $pid is assigned 0, which causes
> the call to POSIX::_exit(42) to be run in test 9.t;
>
>  if ($pid == 0) {
>    # child
>    require POSIX;
>    POSIX::_exit(42);
>  }
>
> I don't know if this is by design.  I'm re-reading PERLWIN32 right now
> to see if it says anything about how fork()ing is done on Windows.
>
> Attached is the output of prove and perl t/9.t.  Let me know if you
> need something else/different.
>
> Thanks,
>
> Brian