In article <[EMAIL PROTECTED]>, Jeff
'Japhy' Pinyan wrote:
> On Sep 29, Kevin Pfeiffer said:
[...]
>>My working copy is now called AliasFilePlus.
>>
>>What do I do with this if I try to share it? The changes to the module
>>seemed too great (and too complex) for me to place them in the main
>>program and too little for a submodule. I've updated the docs and wrote
>>"...based on version xxx of Unix::AliasFile by Steve Snodgrass...", etc.
>
> Typically, you create a sub-module.
>
> package Unix::AliasFile::Extended;
> use base 'Unix::AliasFile';
>
> sub changed_method { ... }
> sub new_method { ... }
>
> 1;
>
> Then you just use Unix::AliasFile::Extended in any program where you would
> have used Unix::AliasFile.
Hmmm... I'll take a look at doing this (maybe my change.
>>(After I clean up a couple things I'll post a link to it in case anyone is
>>interested in sharing critique).
>
> I'd be happy to do that for you.
Thanks, will give a holler. I'm in the "refactoring" mode right now (the
jargon one picks up). One thing that has influenced me is a comment from
the author of the "Objects First" book, who said that on the day
assignments are due he likes to throw a curve at his students ("okay, now
the game has multiple players") and give them an hour to incorporate their
changes. :-0
So I go through my code thinking, what if the program name changes, what if
someone wants to add a new language for the command prompts, etc. -- helps
a lot (it seems to me) and makes my subroutines more 'focussed'.
-K
--
Kevin Pfeiffer
International University Bremen
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
