HTTP/2 200 cache-control: max-age=43200 server: Combust/Plack (Perl) vary: Accept-Encoding content-encoding: gzip content-length: 1797 content-type: text/html; charset=utf-8 last-modified: Sun, 12 Oct 2025 04:36:16 GMT date: Sun, 12 Oct 2025 04:36:16 GMT strict-transport-security: max-age=15768000 Front page | perl.perl5.porters | Postings from December 2014

Re: Is the warning fatalization mechanism in fact safe (specificaly FATAL => 'ununitialized')

Thread Previous | Thread Next

Peter Rabbitson wrote:
> Over the years I have heard several off-the-record remarks that the
> FATAL warning mechanism is in fact rather broken and can not be relied
> upon. Problems described ranged from "both warning and exception will
> disappear in the ether" to "will corrupt the callstack in cases of
> DESTROY-unwind FATAL warnings".
My previous response only addressed the latter.  In all stable
releases of perl, fatals warnings will cause errors and warnings to
disappear at compile time.  This is because the perl compiler likes to
be rather garrulous and emit several warnings before the actual error.
Hence the first warning becomes fatal and the rest is skipped.  We
have fixed this in bleadperl.
The examples you posted are not subject to any of the drawbacks I have
pointed out, as far as I can tell.

Thread Previous | Thread Next

• Is the warning fatalization mechanism in fact safe (specificaly FATAL=> 'ununitialized') by Peter Rabbitson
• Tally of issues with FATAL warnings / RFC to explicitly discouragetheir use by Peter Rabbitson
• Re: Tally of issues with FATAL warnings / RFC to explicitlydiscourage their use by Zefram
• Re: Tally of issues with FATAL warnings / RFC to explicitlydiscourage their use by Jesse Luehrs
• Re: Tally of issues with FATAL warnings / RFC to explicitlydiscourage their use by David Golden
• Re: Is the warning fatalization mechanism in fact safe (specificaly FATAL => 'ununitialized') by Father Chrysostomos
• Re: Is the warning fatalization mechanism in fact safe (specificaly FATAL => 'ununitialized') by Father Chrysostomos
• Re: Is the warning fatalization mechanism in fact safe (specificalyFATAL => 'ununitialized') by Peter Rabbitson
• Re: Is the warning fatalization mechanism in fact safe (specificaly FATAL => 'ununitialized') by Father Chrysostomos
• Re: Is the warning fatalization mechanism in fact safe (specificalyFATAL => 'ununitialized') by bulk88
• Re: Is the warning fatalization mechanism in fact safe (specificalyFATAL => 'ununitialized') by demerphq
• Re: Is the warning fatalization mechanism in fact safe (specificalyFATAL => 'ununitialized') by Peter Rabbitson
• Re: Is the warning fatalization mechanism in fact safe (specificalyFATAL => 'ununitialized') by Rafael Garcia-Suarez
• Re: Is the warning fatalization mechanism in fact safe (specificalyFATAL => 'ununitialized') by Peter Rabbitson
• Re: Is the warning fatalization mechanism in fact safe (specificaly FATAL => 'ununitialized') by Father Chrysostomos