Your skill will accomplish what the force of many cannot |
|
PerlMonks |
Re: Class::MethodMaker, workplace politics, and patchesby BrowserUk (Patriarch) |
on Feb 11, 2005 at 18:13 UTC ( [id://430196]=note: print w/replies, xml ) | Need Help?? |
You ain't gonna like the suggestion but... You are using a dynamic language, apply the patches dynamically. That is, c&p the smallest replaceable piece of code that the patch effects, into your code. Apply the patch to the c&p and dynamically replace the sub/method at runtime. Make that dynamic patch dependant upon the version number of the module you are patching. Add a testcase and/or in-line test for that will detect if the pre-patched code has been fixed in a later version and if it has, disable the code and issue a warning to the logfile noting that the dynamic patch code can be removed.
Get on with the job using the patches and give the document to your supervisor--once you have a sufficient body of work & tests to demonstrate the benefits. You should probably include an example of what extra work would be required or what benefits would be lost were the patch not applied. Examine what is said, not who speaks.
Silence betokens consent.
Love the truth but pardon error.
In Section
Seekers of Perl Wisdom
|
|