Revision as of 00:34, 10 July 2016 edit 91.224.129.184 (talk) →An information-hiding mechanism: removed "older" from sentence. This falsely implied that lack of object-orientation is a trait of old proglangs. However, that trait is intentional in much newer proglangs as well - for example Lua (although it... Tags: Mobile edit Mobile web edit ← Previous edit		Revision as of 11:37, 21 July 2016 edit undo 197.211.56.5 (talk) No edit summary Tag: Visual edit Next edit →
Line 1: In [[programming ~~languages]], <!-- [~~languag[object-oriented programming language]]--> <!-- and related fields, like [[OODMBS]],--> '''encapsulation''' is used to refer to one of two related but distinct notions, and sometimes to the combination<ref>Michael Lee Scott, ''Programming language pragmatics'', Edition 2, Morgan Kaufmann, 2006, ISBN 0-12-633951-1, p. 481: "Encapsulation mechanisms enable the programme<sup></sup>r to group data and the subroutines that operate on them together in one place, and to hide irrelevant details from the users of an abstraction."</ref><ref name=Dale>Nell B. Dale, Chip Weems, ''Programming and problem solving with Java'', Edition 2, Jones & Bartlett Publishers, 2007, ISBN 0-7637-3402-0, p. 396</ref> thereof: * A language mechanism for restricting direct access to some of the [[object (computer science)\|object]]'s components.<ref>[[John C. Mitchell]], ''Concepts in programming languages'', Cambridge University Press, 2003, ISBN 0-521-78098-5, p.522</ref><ref name=Pierce>{{cite book\|last=Pierce\|first=Benjamin\|authorlink=Benjamin C. Pierce\|title=[[Types and Programming Languages]]\|publisher=MIT Press\|year=2002\|isbn=0-262-16209-1}} p. 266</ref>

Encapsulation (computer programming): Difference between revisions