Answer Posted / 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].

What is the use of c language in real life?

1070

---

What is the difference between c &c++?

1208

---

How many keywords (reserve words) are in c?

1184

---

Using functions, write a program that multiplies two arrays. Use the following functions: - Function ReadArray - Function MultiplyArrays - Function DisplayArrays

2405

---

What is getche() function?

1088

---

What are register variables? What are the advantage of using register variables?

1231

---

What is a stream water?

1281

---

What is a pointer in c?

1695

---

Difference between macros and inline functions? Can a function be forced as inline?

1349

---

What are compound statements?

1238

---

Is that possible to add pointers to each other?

1425

---

What is C language ?

2018

---

write a program to print data of 5 five students with structures?

2089

---

number of times a digit is present in a number

2079

---

Describe the difference between = and == symbols in c programming?

1453

---