RE: Having trouble porting an application to MS-Windows - corrected

2007-06-18 Thread Bob McConnell
> -Original Message- > From: Chas Owens [mailto:[EMAIL PROTECTED] > Sent: Friday, June 15, 2007 7:43 PM > To: Bob McConnell > Cc: beginners@perl.org > Subject: Re: Having trouble porting an application to MS-Windows > > On 6/15/07, Bob McConnell &

RE: Having trouble porting an application to MS-Windows

2007-06-18 Thread Bob McConnell
> -Original Message- > From: Chas Owens [mailto:[EMAIL PROTECTED] > Sent: Friday, June 15, 2007 7:43 PM > To: Bob McConnell > Cc: beginners@perl.org > Subject: Re: Having trouble porting an application to MS-Windows > > On 6/15/07, Bob McConnell &

Re: Having trouble porting an application to MS-Windows

2007-06-15 Thread Chas Owens
On 6/15/07, Bob McConnell <[EMAIL PROTECTED]> wrote: > -Original Message- > From: Chas Owens [mailto:[EMAIL PROTECTED] > Sent: Friday, June 15, 2007 11:33 AM > To: Bob McConnell > Cc: beginners@perl.org > Subject: Re: Having trouble porting an application to M

RE: Having trouble porting an application to MS-Windows

2007-06-15 Thread Bob McConnell
> -Original Message- > From: Chas Owens [mailto:[EMAIL PROTECTED] > Sent: Friday, June 15, 2007 11:33 AM > To: Bob McConnell > Cc: beginners@perl.org > Subject: Re: Having trouble porting an application to MS-Windows > > On 6/15/07, Bob McConnell <[EMAIL PROTE

Re: Having trouble porting an application to MS-Windows

2007-06-15 Thread Chas Owens
On 6/15/07, Bob McConnell <[EMAIL PROTECTED]> wrote: snip Or have I found a bug in the ActiveState implementation? snip Are you currently paying for ActiveState support? If so, I would suggest filing a ticket with them. In the mean time, try modifying my code to do a sysread from a socket. -

RE: Having trouble porting an application to MS-Windows

2007-06-15 Thread Bob McConnell
> -Original Message- > From: Chas Owens [mailto:[EMAIL PROTECTED] > Sent: Friday, June 15, 2007 10:55 AM > To: Bob McConnell > Cc: beginners@perl.org > Subject: Re: Having trouble porting an application to MS-Windows > > On 6/15/07, Bob McConnell <[EMAI

Re: Having trouble porting an application to MS-Windows

2007-06-15 Thread Chas Owens
On 6/15/07, Bob McConnell <[EMAIL PROTECTED]> wrote: snip eval { local $SIG{ALRM} = sub { die "alarm\n" }; # NB: \n required alarm $timeout; $nread = sysread PORT, $line, 1; alarm 0;

RE: Having trouble porting an application to MS-Windows

2007-06-15 Thread Bob McConnell
> -Original Message- > From: Chas Owens [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 14, 2007 12:10 PM > To: Bob McConnell > Cc: beginners@perl.org > Subject: Re: Having trouble porting an application to MS-Windows > > On 6/14/07, Chas Owens <[EMAIL PROTEC

Re: Having trouble porting an application to MS-Windows

2007-06-14 Thread Chas Owens
On 6/14/07, Chas Owens <[EMAIL PROTECTED]> wrote: On 6/14/07, Bob McConnell <[EMAIL PROTECTED]> wrote: snip > Can I also send it a signal to > wake it up from another process? In theory you should be able to use kill to send the ALRM signal to another process. I have not tried it. snip Look

Re: Having trouble porting an application to MS-Windows

2007-06-14 Thread Chas Owens
On 6/14/07, Bob McConnell <[EMAIL PROTECTED]> wrote: snip Assuming I can update to ActivePerl 5.8.8.820, if I set an alarm in one forked process (thread?) before calling sysread() or sleep() on Win32, will the same process receive the wakeup? Looks like yes: #!/usr/bin/perl use strict; use war

RE: Having trouble porting an application to MS-Windows

2007-06-14 Thread Bob McConnell
> -Original Message- > From: Chas Owens [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 14, 2007 12:10 PM > To: Bob McConnell > Cc: beginners@perl.org > Subject: Re: Having trouble porting an application to MS-Windows > > On 6/14/07, Chas Owens <[EMAIL PROTEC

Re: Having trouble porting an application to MS-Windows

2007-06-14 Thread Chas Owens
On 6/14/07, Chas Owens <[EMAIL PROTECTED]> wrote: On 6/14/07, Bob McConnell <[EMAIL PROTECTED]> wrote: > In "perlport - Writing portable Perl" in the Alphabetic list of Perl > Functions: > > alarm SECONDS > alarm > Not implemented. (Win32) > > I couldn't find anything in the ActiveState relea

Re: Having trouble porting an application to MS-Windows

2007-06-14 Thread Chas Owens
On 6/14/07, Bob McConnell <[EMAIL PROTECTED]> wrote: In "perlport - Writing portable Perl" in the Alphabetic list of Perl Functions: alarm SECONDS alarm Not implemented. (Win32) I couldn't find anything in the ActiveState release notes that contradicted that. snip > the latest version of

RE: Having trouble porting an application to MS-Windows

2007-06-14 Thread Bob McConnell
Owens [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 14, 2007 11:15 AM > To: Bob McConnell > Cc: beginners@perl.org > Subject: Re: Having trouble porting an application to MS-Windows > > On 6/14/07, Bob McConnell <[EMAIL PROTECTED]> wrote > snip > > On the Win32

Re: Having trouble porting an application to MS-Windows

2007-06-14 Thread Chas Owens
On 6/14/07, Bob McConnell <[EMAIL PROTECTED]> wrote snip On the Win32 platform, this form of select is only implemented for sockets, and alarm() is not implemented at all. snip What makes you think the alarm function is not implemented? Running the following code with the latest version of Act

Having trouble porting an application to MS-Windows

2007-06-14 Thread Bob McConnell
Good morning, The code listed below is part of a link level serial protocol that doesn't port to Win32. A framed message with a checksum is sent and then a single character response (ACK or NAK) is expected in return. On the Win32 platform, this form of select is only implemented for sockets, and