Revision as of 16:34, 27 August 2009 edit Pcap (talk \| contribs) Pending changes reviewers, Rollbackers 18,285 edits some hints on who uses which def ← Previous edit		Revision as of 16:35, 27 August 2009 edit undo Pcap (talk \| contribs) Pending changes reviewers, Rollbackers 18,285 edits clarify Next edit →
Line 5: * A language construct that facilitates the bundling of data with the methods operating on that data.<ref>Wm. Paul Rogers, [http://www.javaworld.com/javaworld/jw-05-2001/jw-0518-encapsulation.html?page=9 ''Encapsulation is not information hiding''], JavaWorld.com, 05/18/01</ref><ref>Thomas M. Connolly, Carolyn E. Begg, ''Database systems: a practical approach to design, implementation, and management'', Edition 4, Pearson Education, 2005, ISBN 0321210255, Chapter 25, "Introduction to Object DMBS", section "Object-oriented concepts", p. 814</ref> Programming language researchers and academics generally use the first meaning alone or in combination with the second in order to distinguish objects from mere [[Record (computer science)\|records]], which may contain function literal of function pointer in some languages. The second definition is motivated by the fact that in many OOP languages hiding of components is not automatic or can be overridden.<!-- this is based on all the refs given above, so no inline cite here--> == Information hiding mechanism ==

Encapsulation (computer programming): Difference between revisions