I realized that it's not that accessors and mutators are problems in themselves, but ones that return primitives
(strings, integers, etc.) are. Returning complex objects is something you do all the time, and it doesn't matter if the method happens
to have the word 'get' or 'set' in it
Just a point of clarification: Get/Set methods are a short way of labelling
methods that access an objects attributes, that is, methods that are only
concerned with reading or writing object state directly. It has
nothing to do with whether the value of that slot is a primitive or an
object, but whether it represents object-state. Objects should rarely
provide methods to the outside world that are only concerened with
accessing state.
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, 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, 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.
|
|
