Re: [PATCH] $SIG::UNSAFE

On 24 Feb 2003 20:19:09 +0100, Slaven Rezic wrote:
>Here's a suggestion. It works best if PERL_SIGNALS is renamed to
>PERL_UNSAFE_ISGNALS:
>
>To set all signals to pre-5.8.0 behavior use the ALL value (or
>__ALL__, if there are systems where ALL is a valid signal name, or
>another alternative would be "1"):
>
>	PERL_UNSAFE_SIGNALS=ALL
>
>For a restricted list of signals use a space separated value:
>
>	PERL_UNSAFE_SIGNALS="USR1 ALRM" 

I wouldn't do the per-signal interface through an environment
variable.

My suggestion for PERL_SIGNALS was only as a master switch for
all signal handling (similar to how PERLIO does it for all I/O
handles) to address the 5.8.1 need for the same.

Any finer grained (typically program-specific) controls really
belong within the script, and the hope is that we can discuss
the interface at length before introducing it into 5.10.


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