Revision as of 19:54, 18 April 2013 edit Loadmaster (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 13,248 edits →As information hiding mechanism: Oops ← Previous edit		Revision as of 15:38, 6 June 2013 edit undo Edward (talk \| contribs) Administrators 94,541 edits m link name mangling using Find link Next edit →
Line 15: Hiding the internals of the object protects its integrity by preventing users from setting the internal data of the component into an invalid or inconsistent state. A benefit of encapsulation is that it can reduce system complexity, and thus increases [[robustness (computer science)\|robustness]], by allowing the developer to limit the interdependencies between software components. Almost always, there is a way to override such protection – usually via reflection API (Ruby, Java, C#, etc.), sometimes by mechanism like [[name mangling]] ([[Python (programming language)\|Python]]), or special keyword usage like <code>friend</code> in C++. Below is an example in [[C Sharp (programming language)\|C#]] that shows how access to a data field can be restricted through the use of a <code>private</code> keyword:

Encapsulation (computer programming): Difference between revisions