Revision as of 09:59, 9 January 2015 edit 49.248.107.170 (talk) →As information hiding mechanism ← Previous edit		Revision as of 13:48, 25 January 2015 edit undo MadScientistX11 (talk \| contribs) Extended confirmed users 4,453 edits →In combination: Blanking section. No real substance here, the author seems to be trying to summarize the point but it makes no sense and adds no value. Next edit →
Line 178: This mechanism is not unique to object-oriented programming. Implementations of [[abstract data types]], e.g. [[module (programming)\|modules]], offer a similar form of encapsulation. This similarity stems from the fact that both notions rely on the same mathematical fundament of an [[existential type]].<ref>Pierce (2002), Section 24.2 "Data Abstraction with Existentials"</ref> ~~== In combination ==~~ ~~{{Expand section\|date=December 2009}}~~ ~~With regard to combination (or bundling) data, this is prevalent in any object that is created. An object's state will depend on its methods that do work on or with the object's internal data.~~ ~~An analogy can be made here with the notion of a [[Information hiding\|capsule]], which not only encloses its contents, but also protects it from the exterior environment.<ref name=Dale/>~~ == References ==

Encapsulation (computer programming): Difference between revisions