>Why wouldn't you want to just get rid of the whole construct? Is there any
>need for it?
It seems safer to kill it.
--tom
>My statement: this shouldn't be the programmer's responsibility. If
>you're using other people's modules that depend on eval, you're in
>trouble anyway. The "local $SIG{__DIE__};" statement should be implicit
>at the start of the eval block.
Why wouldn't you want to just get rid of the whole co
On Thu, 24 Aug 2000 17:57:55 -0700, Peter Scott wrote:
>>I've read 151 a few times, and I don't understand how it can impact
>>the implementation of RFC 88 as a module. Please explain.
>
>If $@ and $! are merged, then in code like
>
> try {
> system_call_that_fails();
>
Watch the behaviour of this code snippet in a current Perl (5.6):
eval {
print STDERR "Testing...\n";
warn "Oops!";
print STDERR "Still going...\n";
die "Argh!!!";
print STDERR "I died, didn't I?\n";
};
print STDE
Peter Scott wrote:
>
> At 06:48 PM 8/24/00 -0600, Tony Olekshy wrote:
> >
> >I've read 151 a few times, and I don't understand how it can
> >impact the implementation of RFC 88 as a module. Please explain.
>
> If $@ and $! are merged, then in code like
>
> try {
> sys
