http://qs321.pair.com?node_id=11139999

parv has asked for the wisdom of the Perl Monks concerning the following question:

(Also on Twitter: https://twitter.com/_parv/status/1476073995598323714)

In Define the Dancer2 Deprecation Policy #1635, could somebody tell me how "hard deprecation" of some code ...

Hard Deprecation

After 12 months or two major releases (whichever comes first), the code is considered to be hard deprecated. An error will continue to be thrown, but unlike soft deprecation, continued usage of the deprecated code will cause the application to die. ...

... is effectively not "removal" if an application would die after "hard deprecation" has been implemented? (earlier discussion referenced in there)

On top of that, there is another 6-month wait for the actual removal of the (hard) deprecated code.

  • Comment on Dancer2- "hard deprecation" of code same as "removal"?

Replies are listed 'Best First'.
Re: Dancer2- "hard deprecation" of code same as "removal"?
by Corion (Patriarch) on Dec 29, 2021 at 08:02 UTC

    I would guess that having the original code still there allows you to locally patch the module file, or monkeypatch the functionality...

Re: Dancer2- "hard deprecation" of code same as "removal"?
by ikegami (Patriarch) on Dec 29, 2021 at 14:50 UTC

    It means you get a nicer error message than "Undefined subroutine &f" for 6 months.