Copy Fatal.pm into autodie.pm? [rt.cpan.org #99778]

[toddr]

Migrated from rt.cpan.org#99778 (status was 'open')

Requestors:

• @karenetheridge

From @karenetheridge on 2014-10-24 17:08:56 : I've been receiving a bunch of failing cpantesters reports like this:

"Incorrect version of Fatal.pm loaded by autodie..."

http://www.cpantesters.org/cpan/report/09903146-5ad1-11e4-97a5-44010a8c9ca5

I'm wondering whether the time has come to simply copy the code in Fatal.pm into autodie.pm, and add a big deprecation warning into Fatal.pm?

From @toddr on 2020-01-08 07:02:11 : I don't know the history here but I think this can be closed as complete, right?

From @karenetheridge on 2020-01-08 17:36:18 :

Fatal.pm still has a lot of guts in it, but it's unknown how many things are still dependent on it. I would still add a '(DEPRECATED)' into Fatal's ABSTRACT (line 3), and add some deprecation metadata though (since you're using dzil, [Deprecated] can do this).

Depending on how ugly Fatal's code is, it could even print a runtime warning when it is used (like Any::Moose and other obsolete things do).

[toddr]

@karenetheridge I'm closing this out since Fatal.pm is now shipped with autodie.

[karenetheridge]

since Fatal.pm is now shipped with autodie

It always was... that wasn't the issue, but rather that the code was in two separate files. I still think that Fatal.pm should be more clearly marked as deprecated and not suitable for direct use.

[toddr]

Sorry. I was processing tickets too fast after the import to github and didn't notice we'd interacted on this.

How would you recommend we change the code?