And, when Damian Conway (Perl Best Practices) suggests offer oo as 'option' not a default.. this is not what he's talking about?
Actually Damian says 'make it a choice, not a default'. I don't think he's referring to the user of the module/class, but the developer of it. So he's suggesting that you don't assume that every module you implement should inherently be a class, but that a non-OO implementation may just as good or a better choice in a given scenario.
perl -e 'split//,q{john hurl, pest caretaker}and(map{print @_[$_]}(joi +n(q{},map{sprintf(qq{%010u},$_)}(2**2*307*4993,5*101*641*5261,7*59*79 +*36997,13*17*71*45131,3**2*67*89*167*181))=~/\d{2}/g));'
In reply to Re^3: coding a subroutine as both method and regular function
by agianni
in thread coding a subroutine as both method and regular function
by leocharre
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |