|
|
|
| Come for the quick hacks, stay for the epiphanies. | |
| PerlMonks |
comment on |
| ( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
|
Indeed. There are always going to be some attributes that need to be queried. Further, there are some attributes that need to be set directly and in isolation. Eg. If you move the address need to be updated. If you change your pin. Etc. Of course, the former is likely a part of a Customer Class; and validation of the address is likely performed by a different processing application long before that information is wrapped up in a transaction and applied to the actual Customer record. And the latter is likely part of a CreditCard class; and again validation and verification checks performed outside of the process that updated the master records. But the point holds; accessor and mutator methods should be added deliberately as a designed requirement for those attributes that require them for the functional operation of the class; not generated automatically regardless of the need. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
In the absence of evidence, opinion is indistinguishable from prejudice.
In reply to Re^5: OOP's setter/getter method - is there a way to avoid them?
by BrowserUk
|
|