I was meaning "what the code is currently doing" in the context of Adrian's suggestion that it could be safe to run a sub to know if it behaves correctly. That way I could always run the code after an upgrade to see if its behavior has changed. The problem with that is even if I know what the code is currently doing and therefore deem it safe to run, I don't know what it will be doing in the future, and thus I don't know if it will be safe to run. Thus, Adrian's solution can't work.

As for the problems with forking, you can google for that pretty easily. The pros and cons are numerous and well spelled out. To fork, you really need a compelling reason to but too many forks spoil the broth. Even a great fork can meet serious resistance. Look at Module::Build. Many people who didn't understand the problems with ExtUtils::MakeMaker were pretty vehement that Module::Build was a bad thing. Go figure. (well, there was that little matter of PREFIX. It's horribly broken but people want its broken behavior).

If you fork privately, you have to maintain it in-house. For small projects this is not so bad. For large projects, it gets hairy. If you want to fork it publicly, you might get community support. You might get ingnored. You might get community derision. Imagine if Module::Build was one of the offenders (it has bugs reported, but it's certainly not one of the offenders in question since it's being so actively developed). Could you reasonably fork that and expect it to work on the hundreds of different platforms it's supposed to work on? Could you expect the community to help with a fork they may not see the merit of?

That's not to say that forking is always bad. I'm just pointing out that forking is a very serious issue and if the code isn't trivial, it shouldn't be done on a whim.

Cheers,
Ovid

New address of my CGI Course.

In reply to Re^6: Upgrade-proofing overridden subroutines by Ovid
in thread Upgrade-proofing overridden subroutines by Ovid

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.