Revision as of 00:54, 2 December 2015 edit Mathieu ottawa (talk \| contribs) Extended confirmed users 1,741 edits moved a useful (but not defining) sentence from top of leader to end of leader ← Previous edit		Revision as of 01:03, 2 December 2015 edit undo Mathieu ottawa (talk \| contribs) Extended confirmed users 1,741 edits nuked the first paragraph: it said the same things as the next paragraph (or did, a couple revisions ago) but not as well, with the addition of an inaccurate statement about code corruption Next edit →
Line 1: In programming languages, <!-- [[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:▼ '''Encapsulation''' is the concealment of implementation: the normal position of the barrier is closed. It allows selective hiding of properties and methods in an object by building an impenetrable wall to protect the code from accidental corruption. ▲In programming languages, <!-- [[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 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