When would you use OO Perl?

If the module/library needs to retain state, then OO is the natural way to provide for that.

However...

When would you use OO Perl?

Only if the module/library needs to retain state, and, performance is not a consideration for that module/library.

If performance is a consideration, and the functional requirements are such that moving (the critical parts) to C or C++ would be laborious relative to a native Perl implementation; then I will eschew OO and go with a procedural design, manually passing a 'handle' (aka: a dynamically allocated memory address), returned by the 'initialisation' function, to subsequent calls to allow internal state to be retained .

In all coding, in all languages, the functional requirements should drive the design semantics; not the other way around.

OO for its own sake is as destructive as any other dogma.

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.

In reply to Re: Right job for the tool. by BrowserUk
in thread Right job for the tool. by AltGrendel

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.