Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
For example, we have the class Man
If Man.age is protected, then I don’t see why chuckNorris (instance of class Man) can change the protected/private attribute age of the object jackBauer (another instance of class Man). He shouldn’t be able to do that (IMO).
In my mind, the value of a protected/private attribute is supposed to belong only to the object itself, not the class…
I need some explanation I think, I’m confused.
Matthieu is right. cuckNorris can do jackBauer.age
But there is no problem on that. If you are referencing Man instance attributes inside Man, that means you are coding Man class, so you know what you are doing.
The problem would be if you pass me that Man class and I could access the Man attributes with out knowing how Man class is coded.
Setters and getters may be doing some business logic that I don’t know and I don’t need to know. But the one who coded Mam does know.