in reply to
Changing Modules in Bad Code
I'll also throw out a vote for option 1.
Option 2 could lead to *very* interesting situations on down the road. Say you do end up wrapping the module, or rewriting it's methods. Someone else comes along later, and upgrades the module. oops!
MMMMM... Chocolaty Perl Goodness.....
A Programming Language, 1962
Programming the 1900 series in COBOL, 1974
Algorithms + Data Structures = Programs, 1976
The C Programming Language, 1978
System V - Interface definition, 1986
Z80 Assembly Language Programming, 1979
TheSOURCE User's Manual, 1979
The C Primer, 1983
Interactive Fortran 77, A Hands on Approach, 1984
Perl.1 man page, 1991
Results (68 votes),