|P is for Practical|
Re^14: The Most Essential Perl Development Tools Today (negative)by BrowserUk (Pope)
|on Jan 13, 2013 at 18:44 UTC||Need Help??|
then the subroutine probably has almost no code in it at all, and the solution is to inline the tiny amount of code in the subroutine and remove the calling overhead entirely.
Sure, you could do that, but are you really going to allow all the callers of your objects to access their attributes directly rather than going through getters?
Little bits add up! Here a 25% penalty just to satisfy two pointless P::C rules:
And that is just one level deep. Imagine (or test) the affect of calling a method that itself needs to call 2 or 3 getter() from one of its sub objects.
The penalties, for what are purely cosmetic affectations, add up.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.