comment on

An object should have methods reflecting its external behavior. "Set your X value to 24" is rarely a nice reusable, maintainable external behavior.

People writing these kinds of objects generally haven't quite gotten in to "object thinking", and instead treat the object as a "smart record". Methods should instead be derived by understanding how the class might be used (including subclassing).

I think the Perl6 object approach where all variables are private to the class (and not even directly available to the subclasses) will make for some interesting designs, especially when thinking about reuse.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

In reply to •Re: Why get() and set() accessor methods are evil by merlyn
in thread Why get() and set() accessor methods are evil by synistar

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.


Clear questions and runnable code get the best and fastest answer
	PerlMonks