Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

comment on

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

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.

yours,
Michael

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

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



  • 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.
Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (3)
As of 2022-12-05 07:04 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?