Re: [PATCH] $SIG::UNSAFE

On Sun, 23 Feb 2003 19:15:49 +0200, Jarkko Hietaniemi wrote:
>> I don't see why that is a showstopper.  Pending a fix for the bug,
>
>Huh?  Pending for fixing the bug?

I thought you were saying that the __ALL__ entry being left behind
after scope exit was a problem for implementing the new semantics.

How exactly is it a problem in old perls?  This did not produce
any warnings/errors in 5.00503:

    local $SIG{XYZ} = 'foo' if $^V;

>> If that is still unworkable for some reason, I would prefer
>> adding this stuff via an extension module/pragma, maybe even
>> via sigtrap.pm:
>> 
>>     use sigtrap;
>>     ...
>>     {
>>         sigtrap::set_local(ALARM => 'IMMEDIATE') if $] > 5.008;
>>         ...
>>     }
>
>Lexical scope does not make that much sense for this feature.

Agree.  I didn't say it was lexically scoped.


Sarathy
gsar@ActiveState.com

• [PATCH] $SIG::UNSAFE by Jarkko Hietaniemi
• Re: [PATCH] $SIG::UNSAFE by Gurusamy Sarathy
• Re: [PATCH] $SIG::UNSAFE by Nicholas Clark
• Re: [PATCH] $SIG::UNSAFE by Gurusamy Sarathy
• Re: [PATCH] $SIG::UNSAFE by Jarkko Hietaniemi
• Re: [PATCH] $SIG::UNSAFE by Jarkko Hietaniemi
• Re: [PATCH] $SIG::UNSAFE by Gurusamy Sarathy
• Re: [PATCH] $SIG::UNSAFE by Jarkko Hietaniemi
• Re: [PATCH] $SIG::UNSAFE by Gurusamy Sarathy
• Re: [PATCH] $SIG::UNSAFE by Jarkko Hietaniemi
• Re: [PATCH] $SIG::UNSAFE by Gurusamy Sarathy
• Re: [PATCH] $SIG::UNSAFE by Jarkko Hietaniemi
• Re: [PATCH] $SIG::UNSAFE by Slaven Rezic
• Re: [PATCH] $SIG::UNSAFE by Gurusamy Sarathy
• Re: [PATCH] $SIG::UNSAFE by Jarkko Hietaniemi
• Re: [PATCH] $SIG::UNSAFE by Jarkko Hietaniemi
• Re: [PATCH] $SIG::UNSAFE by Tim Bunce