in reply to Re: Unsafe signals are called "Unsafe" for a reason, you know
in thread Upgrading Perl in production environment
What you so blithely describe as "lala land" is undefined behavior. It could be anything, including something incredibly destructive. It could be jumping into &main::destroy_all_monsters. It could be calling system("rm -rf $HOME"). It could be anything. (Get the point yet? No?)
That is why it unsafe signal handling is called "unsafe", and that is why there is NO situation in this particular universe where it is acceptable. At all. Ever. No exceptions.
Got it? No? Oh well. I'm giving up on educating you. But I was serious about wanting to know where that financial program is that uses unsafe signals. I really don't my money there. I'm totally serious about that.
-- Chip Salzenberg, Free-Floating Agent of Chaos
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Re: Re: Unsafe signals are called "Unsafe" for a reason, you know
by jfroebe (Parson) on Mar 19, 2004 at 18:27 UTC |
In Section
Seekers of Perl Wisdom