comment on

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

In reply to Re: Implementing an event-driven object model in Perl by demerphq
in thread Implementing an event-driven object model in Perl by jkva

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks