Re: [PATCH] $SIG::UNSAFE

FWIW, I do not care about the name as such.
$SUPERCALIFRAGISTILISTIEXPIALIDOCIOUS would work for me equally well.
The point being is that the idea was that with as minimal as possible
changes to "old legacy" (pre-5.8.0) code people could get back the old
signal behaviour during runtime.

-- 
Jarkko Hietaniemi <jhi@iki.fi> http://www.iki.fi/jhi/ "There is this special
biologist word we use for 'stable'.  It is 'dead'." -- Jack Cohen

• [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