How can I prevent other programmers from violating
encapsulation by seeing the private parts of my class?
Answer / abalonesoft
Not worth the effort — encapsulation is for code, not people.
It doesn't violate encapsulation for a programmer to see the
private and/or protected parts of your class, so long as
they don't write code that somehow depends on what they saw.
In other words, encapsulation doesn't prevent people from
knowing about the inside of a class; it prevents the code
they write from becoming dependent on the insides of the
class. Your company doesn't have to pay a "maintenance cost"
to maintain the gray matter between your ears; but it does
have to pay a maintenance cost to maintain the code that
comes out of your finger tips. What you know as a person
doesn't increase maintenance cost, provided the code you
write depends on the interface rather than the implementation.
Besides, this is rarely if ever a problem. I don't know any
programmers who have intentionally tried to access the
private parts of a class. "My recommendation in such cases
would be to change the programmer, not the code" [James
Kanze; used with permission].
Is This Answer Correct ? | 0 Yes | 0 No |
what is difference between #include<stdio.h> and #include"stdio.h"
What is %d called in c?
what are the advantage and disadvantage of recursion
What is use of bit field?
What's wrong with "char *p; *p = malloc(10);"?
Why do we need volatile in c?
Why is main function so important?
how to print "hai" in c?
In which area global, external variables are stored?
the portion of a computer program within which the definition of the variable remains unchanged a) mode b) module c) scope d) none
What is data structure in c language?
How can I manipulate strings of multibyte characters?