They are not "fake accessors", they are object-oriented accessors, as opposed to the usual method-oriented accessors (neither of which couples the interface to the implementation). Properties of an object are a legitimate part of the object model, not merely part of its implementation. They are conceptual objects. Method-oriented design (where the object name is embedded in the name of a parent object's method, or is passed to it) sweeps that under the rug. There is reason to do that; I'm not saying it shouldn't be done. I just think people should be aware of
why it's done. Because it rankles.
Accessors certainly can indicate poor design, but they don't always. Some objects are intended to be freely manipulated. The objects in a drawing program, for example. Or the accounting books at Enron. The object has to model the process, it can't dictate it.
Caution: Contents may have been coded under pressure.
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.