Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

Re: Re: Why get() and set() accessor methods are evil

by Anonymous Monk
on Nov 25, 2003 at 18:13 UTC ( #309991=note: print w/replies, xml ) Need Help??


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

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.

  • Comment on Re: Re: Why get() and set() accessor methods are evil

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://309991]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (3)
As of 2022-05-24 22:55 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Do you prefer to work remotely?



    Results (84 votes). Check out past polls.

    Notices?