Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Getters ought to be present to provide access to well defined attributes of an object. If, for example, the object measures something, I may provide a getter to allow a user of that object to extract the specific value that has been measured. One should always be stingy in offering getters. After all, once you have put it in your public contract, it's a whole lot harder to remove it.

When an attribute is a collection, it gets more "interesting". Fowler, in "Refactoring", describes one called Encapsulate Collection. In that refactoring, you don't return the raw collection with a getter. You return a read-only version, if you must return the collection, and provide add and remove options (as appropriate) to permit modifications. That keeps changes under the control of the object.

Now, Fowler speaks specifically to a Java audience, but the concept here is worth keeping in mind. The key is to contract to provide data in a particular format and then to keep that contract. Try to choose a format that gives you the flexibility to do what you may need to do on the inside without having to go through extra contortions to keep that contract.

I've been doing some Java programming to help firm up the knowledge I gained in a recent class. It's been usefully interesting. I expect my Java experience to inform my Perl programming in useful ways. On the other hand, there are things Perl makes so much easier. I have not yet sorted out if and how to say "foreach my $f (fn_returning_list()){do stuff}" without the structural overhead of creating an iterator and explicitly walking it.


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

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others examining the Monastery: (3)
    As of 2021-01-23 07:51 GMT
    Find Nodes?
      Voting Booth?