I particularly agree with
toma's comments above about the API. Once you know how to 'do' Perl OO, the hard part is designing the API.
My advice is to learn the basics of Perl OO, firstly from the docs
perlboot,
perltoot,
perltooc,
perlbot. I also found this
book by
TheDamian very good.
Then I suggest you try out using the techniques in a few
small projects. I know this goes against normal guidelines of when to use OO, but I think it's important to be able to experiment and not have to worry about making mistakes.
I think spending time designing the API before coding is vital, as there's nothing worse that working on a large project and having to make changes throughout when you realise the API is flawed.
Once you've go the API down, then you should be able to make changes to the object structure without having to change everything that uses it. It rewarding when you can do that and you know it's because you've got a good design.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.