Dear Monks, The small set of scripts that began my initiatiation into to the world of perl have grown up. They now encompass a couple thousand lines of code covering many, many files.

There have been several stages throughout this creeping development where I've had the urge to go back and redo everything from the ground up... implementing all the new skills I've accumulated throughout the experience and rebuilding the project in an object oriented manner... but under the pressure of that unavoidable villain, the clock, I haven't had time to spare.

In it's current form I find myself spending enough time tracking bugs related to the complexity of the code that I think an object-oriented rebuild is a necessity, and luckily I've been granted a bit of reprieve from deadlines.

Anyway, irrelevant back-story aside, I'm about to delve into OO Perl research. I have a copy of the Panther (Advanced Perl Programming) handed down to me by a friend along with a recently purchased copy of the Camel (Programming Perl). From other nodes I have read, I gather that the Panther is more tutorial based, while the Camel is more of a reference. From the brief bit of reading I've done in both books, I do find the Panther much easier to follow. So, I was planning on familiarizing myself with OO Perl using the Panther, and then work with those skills to rebuild my scripts. After this I would probably be familiar enough with the concepts to tackle the more in-depth material of the Camel.

The only concern I have is with the age of the Advanced Perl Programming book. OO Perl seems like a topic that could have evolved quite a bit over the last few years. Are there any caveats I should look out for? Or can I rely on the Panther for sound, up-to-date working knowledge of OO Perl?

In reply to The Camel and the Panther by tombmbdil

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.