Even though its only indirectly related I thought it was worth making a minor point:
Dont get too caught up in the OO aspect of Design Patterns. Perls functional abilities bring an entirely different view to how things like this can work. For instance the observer pattern works just fine with closures as callbacks, and has the advantage of being much more flexible and powerful.
IMO it would be a good idea to read Higher Order Perl and then go back to Design Patterns. I think the insight youll gain from HOP will be very useful in "perlizing" the stuff in design patterns.
---
$world=~s/war/peace/g
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.