Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

Re: Getter and Setter Function Names

by Biker (Priest)
on Apr 10, 2003 at 14:14 UTC ( #249619=note: print w/replies, xml ) Need Help??


in reply to Getter and Setter Function Names

I dislike "getters" but like "setters".

A method called salary() indicates a "thing", a noun. Well, what is this "thing", you may ask. The logical (in my humble opinion) answer is that the salary() method tells you what the "salary thing" is. Implementation: salary() returns the salary. No need for a "get_salary()".

It all becomes different when we want to apply a verb to your "thing". This is when I start working with the method name. Like increase_salary(), set_salary() or (sob) decrease_salary().

As a result, I end up with one method that represents the thing and zero or more methods that affects the thing.


Everything went worng, just as foreseen.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://249619]
help
Chatterbox?
[Corion]: Muh. Maybe I should give a talk about how to program for auditors, as I find that this changes my approach to programs a bit ;)
[Corion]: (well, especially logging, as about everything about every decision a program makes could/should be logged :))

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (8)
As of 2017-05-23 15:56 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?