We don't bite newbies here... much | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
well.. Learning Perl is followed by Intermediate Perl and Mastering Perl so you can read these book to find some hint you want.
That said Objected Oriented is not the only way to do serious things: see Damian Conway's ten rules for when to use OO but also I dislike object-oriented programming in general Maybe you are doing confusion between OOPerl and the modules ecosystem? I mean that if you want to start a big project, and you can abstract beahviours in modules your life will be better in long term. A module, a separate collection of behaviours, can be tested separately from the main application and this is good thing, it can be also documented separately, another good thing. See also a similar theme here and A brief question about testing/best practices for good testing habits (also see Testing methodology, best practices and a pig in a hut.). This does not means that your project MUST be OO. In addition OO in Perl is achievable in many ways: a big herd of Moose modules is on CPAN but you may find that drawbacks are bigger than advantages, using them: see How Large Does Your Project Have To Be to Justify Using Moose?
L*
There are no rules, there are no thumbs.. Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS. In reply to Re: Moving from scripting to programming
by Discipulus
|
|