in reply to RFC: Devel::Deprecate

I'm with dragonchild, sounds fantastic. I already have a nickname for it: "the other coding by contract." It would be nice to have some facility to remind everyone that it should be removed eventually, no? Years after the issue is dead and buried the code might still be running for no reason. Have no idea how to approach that though.

Replies are listed 'Best First'.
Re^2: RFC: Devel::Deprecate
by Ovid (Cardinal) on Apr 23, 2008 at 16:56 UTC

    As mentioned to mr_mischief, I was thinking that (pseudocode):

    if today >= die_date if 'if' is present if 'if' returns true die reason else warn reason # they won't forget it now! endif else die reason # automatically die if no condition endif endif

    Thus, they get deprecation warnings even after the 'die' date, even if no code triggers the deprecation. I'm not sure if this is a good idea or not.

    I'm also thinking about aliases to the deprecation name: deprecation_XXX and deprecation_TODO. Programmers often embed XXX and TODO in their code and grep for them regularly. This will make it easier to find.

    Cheers,
    Ovid

    New address of my CGI Course.