Keep It Simple, Stupid | |
PerlMonks |
Re^3: How's My Style Now?by TGI (Parson) |
on Feb 08, 2010 at 19:22 UTC ( [id://822065]=note: print w/replies, xml ) | Need Help?? |
I understand the tension between too-much modularity and not enough. It's a continuing part of self-aware coding. Moving more of your code into modules with POD documentation will help make subroutines less burdensome. Using modules lets you group your code into specific name spaces, and when you use explicit imports, you have an instant reminder where the sub came from. Using POD lets you use perldoc to read about your code. Consider this code:
I know that foo() comes from MyMod, so I can simply do a perldoc MyMod, to read about foo(). This beats the heck out of: Escpecially since if I refactor MyMod or mylib, and move foo() to another file, failure to update the location info in my code causes a fatal error for the module. With library requires, I can easily get stuck with comments that lie.
In Section
Seekers of Perl Wisdom
|
|