HTTP/2 200 cache-control: max-age=43200 server: Combust/Plack (Perl) vary: Accept-Encoding content-encoding: gzip content-length: 1747 content-type: text/html; charset=utf-8 last-modified: Tue, 14 Oct 2025 01:18:17 GMT date: Tue, 14 Oct 2025 01:18:17 GMT strict-transport-security: max-age=15768000 Front page | perl.perl5.porters | Postings from January 2015

Re: Tally of issues with FATAL warnings / RFC to explicitlydiscourage their use

Thread Previous | Thread Next

On Thu, Jan 29, 2015 at 12:07 PM, Peter Rabbitson <rabbit-p5p@rabbit.us>
wrote:

> I therefore propose that an augmentation of 5e0ced9c[2] is needed
> amounting to an explicit discouragement of using the FATAL feature in CPAN
> libraries (end users should be free to keep the pieces). I also implore
> participants to limit the discussion to this (actionable) proposal, instead
> of venturing further afield as in "why don't we deprecate them outright for
> 5.22" (if anything this is a discussion for 5.23).
>
>
+1 → Seems like a reasonable documentation change for 5.22.

David

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