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].

Explain what are reserved words?

1041

---

Synonymous with pointer array a) character array b) ragged array c) multiple array d) none

1011

---

How can I send mail from within a c program?

983

---

What is the use of volatile?

1043

---

What is the use of sizeof?

969

---

How main function is called in c?

1072

---

How to delete a node from linked list w/o using collectons?

2721

---

What is keyword with example?

1012

---

Which operators cannot be overloaded a) Sizeof b) .* c) :: d) all of the above

1095

---

What was noalias and what ever happened to it?

979

---

Write a simple code fragment that will check if a number is positive or negative.

1100

---

What is the difference between functions getch() and getche()?

1035

---

Explain what is operator promotion?

1024

---

What is the significance of c program algorithms?

1098

---

What is openmp in c?

968

---