develooper Front page | perl.perl5.porters | Postings from February 2011

Re: inherent problem with fatal warnings

Thread Previous | Thread Next
From:
Nicholas Clark
Date:
February 22, 2011 07:19
Subject:
Re: inherent problem with fatal warnings
Message ID:
20110222151902.GP24189@plum.flirble.org
On Tue, Feb 22, 2011 at 08:14:45AM -0700, Tom Christiansen wrote:
> Nicholas Clark wrote:
> 
> >Woah. use warnings is lexical, right?
> >So why is the fatality leaking?
> 
> It's not leaking out of the lexical scope.
> It's leaking into the compilation phase.

But surely it's doing *exactly* what it's documented to do.

If you want to change what "ALL" means, what do you propose that the name is
for "compilation *and* runtime" fatality?

I can see that runtime-only fatality has a use.
Likewise, I suspect that compile-time only fatality has a use
("I can watch to see if my server starts OK, but once it's running, I'd
prefer it not to bomb out when it might recover")

I think a better proposal is to have two new things akin to "ALL", one for
runtime, one for compile time, and a way to select either independently
(with ALL continuing to mean what it always did)

Nicholas Clark

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About