in reply to Re^2: Professional development with Perl - how it's done?
in thread Professional development with Perl - how it's done?
I really don't think modifying CPAN code is good practise, unless it's to fix a serious bug that you then give back to the author.
If I really want to modify the behaviour of a CPAN module and it's not reasonable to subclass (or I couldn't be bothered ;) I usually inject my own subs/methods into the namespace from my own code. That way you don't need to carry around modified CPAN modules. And with any luck, minor upgrades to the cpan module won't break your addins (which are hopefully based on documented API anyway).
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^4: Professional development with Perl - how it's done?
by techcode (Hermit) on May 30, 2006 at 10:33 UTC |
In Section
Seekers of Perl Wisdom