Unfortunately, this is the sort of question that can only be answered with experience. Do you have some sort of model where you can separate data and behavior into discrete objects? Do you find yourself passing the same kind of information in and out of your functions?

There's nothing wrong with using Exporter sanely. If you can split things up into modules, and some of them don't immediately lend themselves to object orientation, don't force it.

Hmm, this doesn't seem like a very helpful answer. I guess my rule of thumb is, "Use OO when it makes things easier." You can certainly accomplish the same kinds of things in a purely-procedural language as with a functional or an object oriented language. The question is one of relative ease.

In reply to Re: OO code split by chromatic
in thread OO code split by melguin

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.