How does C++ help with the tradeoff of safety vs. usability?
Answer Posted / abalonesoft
In C, encapsulation was accomplished by making things static
in a compilation unit or module. This prevented another
module from accessing the static stuff. (By the way, static
data at file-scope is now deprecated in C++: don't do that.)
Unfortunately this approach doesn't support multiple
instances of the data, since there is no direct support for
making multiple instances of a module's static data. If
multiple instances were needed in C, programmers typically
used a struct. But unfortunately C structs don't support
encapsulation. This exacerbates the tradeoff between safety
(information hiding) and usability (multiple instances).
In C++, you can have both multiple instances and
encapsulation via a class. The public part of a class
contains the class's interface, which normally consists of
the class's public member functions and its friend
functions. The private and/or protected parts of a class
contain the class's implementation, which is typically where
the data lives.
The end result is like an "encapsulated struct." This
reduces the tradeoff between safety (information hiding) and
usability (multiple instances).
Is This Answer Correct ? | 3 Yes | 0 No |
Post New Answer View All Answers
Do array subscripts always start with zero?
Who developed c language and when?
What is a shell structure examples?
What is the difference between test design and test case design?
What are near, far and huge pointers?
What is character set?
What is c language used for?
Why isnt any of this standardized in c?
What is oops c?
In the DOS enveronment, normal RAM that resides beyond the 1mb mark. a) expanded memory b) swapped memory c) Extended memory d) none
Can we compile a program without main() function?
What is an lvalue in c?
What are the standard predefined macros?
Can we replace the struct function in tree syntax with a union?
Synonymous with pointer array a) character array b) ragged array c) multiple array d) none