I find a few reasons to not oppose to this (considered evil) path:
- Using a module that is not maintained and nobody took over, several patches were proposed but nobody uploaded a fixed version.
Of course you can apply the patches locally before you install it, but that is no guarantee it is also fixed on other systems.
It is way more reliable to overrule the faulty sub or make a new one foced into the faulty package thereby making sure it works.
- The package owner/maint has explicitely said *not* to add the requested/required functionality (they might even have documented so),
so adding the desired method by forcing it into the package is relatively safe. (problematic would only be a new maintainer who disagrees
with the refusal and putting it in later anyway)
- When working in supporting a module that is evolving, adding methods that are not yet implemented or have been removed, all guarded by
version checks is a very fine way to make your module work for the end-users regardless of the changes in the underlying module(s). I do
this very regularly. (example)
- Overruling CORE::GLOBAL functions in test files to provide stubs.
Enjoy, Have FUN! H.Merijn
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
