comment on

In general, I find that when using an OO approach with a granularity that is not too large I seldomly run into problems when I want to change the code later.

Classes should map as closely as possible to the "objects" involved in the problem you're trying to solve (that's what I mean by the "right" level of granularity).

Altering functionality can be done by using the typical OO techniques like inheritance or composition.

For me, the threshold to introduce classes is very low, but opinions on this topic differ widely.

Just my 2 cents, -gjb-

In reply to Re: Multilevel flexibillity by gjb
in thread Multilevel flexibillity by zby

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.


We don't bite newbies here... much
	PerlMonks