I am probably getting in trouble here, being only a scribe, but I would like to express my feelings on these very worthy questions.

I end up using OO-Perl:
When I find that the structures that I am using in my program have inherent subroutines (methods) associated with them, or when the structures build on substructures in a logical way. I also have found that I will rewrite some procedural hack as a module (OO prefered here) when the hack looks like it might actually be useful to several applications or to other folks.

Question 2: I do whole lot of precedural hacks, maybe 1-100 lines of code. I wouldn't use objects on these, unless, of course, I am using a Perl Module that lends itself to an object/method model. (Most do!)

In reply to Re: To use or not to use OO Perl by perlcapt
in thread To use or not to use OO Perl by monkfan

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.