On 15 May 2000 10:20:45 -0400, [EMAIL PROTECTED] (David S. Rosinger)
wrote:
>I see the FAQ for Perl 5.6 does say that signal handling is
>unsupported, but Jan had this to say back in January:
>
> |Date: Thu, 20 Jan 2000 18:50:17 -0800
> |From: Jan Dubois <[EMAIL PROTECTED]>
> |To: "Perl-Win32-Users Mailing List" <[EMAIL PROTECTED]>
> |Subject: Re: I cannot get $SIG's to work on WinNT...
> |
> |On Thu, 20 Jan 2000 15:10:42 -0800, "Wilson, Brent"
> |<[EMAIL PROTECTED]> wrote:
> |
> |>I cannot get $SIG's to work on WinNT... here is my test code (this
> |>is right out of the documentation)... I run it and hit Ctrl-C and
> |>expect to see: "Somebody sent me a SIGINT".
> |
> |%SIG doesn't work at all in the ActivePerl 5xx builds due to
> |incompatibility with the C++ runtime. This limitation will be removed in
> |ActivePerl 5.6, where signals will revert back to the same broken state
> |they are in on UNIX. Pressing Cntrl-C while a Perl program is running
> |(and not in a blocking state) will crash the signal handler about 10% of
> |the time. This is a long known "limitation" that cannot be removed
> |without slowing down Perl considerably.
> |
> |-Jan
>
>Jan, now that 5.6 has been released, can you update us on this matter?
It *should* "work", but I see that it doesn't. This is a bug (signals
don't seem to be virtualized by the USE_IMP_SYS layer). So I guess the
update is: "This *should* work in the next release." :-)
-Jan
---
You are currently subscribed to perl-win32-users as: [archive@jab.org]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
