Shawndouglas: /* References */ Cat

2022-09-19T23:07:50Z

References: Cat

← Older revision		Revision as of 23:07, 19 September 2022
Line 125:		Line 125:

	<!---Place all category tags here-->		<!---Place all category tags here-->
	[[Category:Software ~~and hardware terms~~]]		[[Category:Software development]]

Shawndouglas: /* Notes */ Corrected link

2014-08-29T16:59:02Z

Notes: Corrected link

← Older revision		Revision as of 16:59, 29 August 2014
Line 119:		Line 119:

	==Notes==		==Notes==
	This article reuses numerous content elements from [http://en.wikipedia.org/wiki/~~ebXML~~ the Wikipedia article].		This article reuses numerous content elements from [http://en.wikipedia.org/wiki/Encapsulation_%28object-oriented_programming%29 the Wikipedia article].

	==References==		==References==

Shawndouglas: Created as needed.

2014-08-29T16:58:03Z

Created as needed.

New page

'''Encapsulation''' is one of the four fundamentals of object-oriented programming (OOP), involving the concept of "bundling data with the methods that operate on that data."<ref name="RogersEnc">{{cite web |url=http://www.javaworld.com/article/2075271/core-java/encapsulation-is-not-information-hiding.html |title=Encapsulation is not information hiding |author=Rogers, William Paul |work=JavaWorld |date=18 May 2001 |accessdate=28 August 2014}}</ref> Encapsulation places the values or state of a structured data object within a class, preventing unauthorized access to them. Publicly accessible methods are generally provided in the class (so-called "getters" and "setters") to access the values or state, and other client classes call these methods to retrieve and modify the values within the object. In some programming languages, this concept should not be interpreted as hiding; for example, in Java data can be encapsulated but also remain unhidden.<ref name="RogersEnc" /> Additionally, encapsulation is not unique to object-oriented programming. Implementations of abstract data types like modules offers a similar form of encapsulation.

==Definition==
In programming languages, "encapsulation" is used to refer to one of two related but distinct notions (and sometimes to both)<ref name="ScottPrag">{{cite book |url=http://books.google.com/books?id=GBISkhhrHh8C&pg=PA449 |chapter=Chapter 9: Data Abstraction and Object Orientation |title=Programming Language Pragmatics |author=Scott, Michael Lee |publisher=Morgan Kaufmann |edition=3rd |pages=449–500 |isbn=9780080922997 |year=2009 |accessdate=29 August 2014}}</ref><ref name="DaleJava">{{cite book |url=http://books.google.com/books?id=qBKO1b8CsNUC |chapter=Chapter 8: Object-Oriented Software Engineering |title=Programming and Problem Solving with Java |author=Dale, Nell B.; Weems, Chip |publisher=Jones & Bartlett Publishers |edition=2nd |pages=394–451 |year=2008 |isbn=9780763734022 |accessdate=29 August 2014}}</ref><ref name="PierceTypes">{{cite book |url=http://books.google.com/books?id=ti6zoAC9Ph8C |chapter=Chapter 20: Recursive Types |title=Types and Programming Languages |author=Pierce, Benjamin C. |publisher=MIT Press |year=2002 |pages=265–280 |isbn=9780262162098 |accessdate=29 August 2014}}</ref><ref name="RogersEnc" />:

* a language mechanism for restricting access to some of the object's components

* a language construct that facilitates the hiding of data with the functions operating on that data

Some programming language researchers and academics use the first meaning alone or in combination with the second as a distinguishing feature of OOP, while other programming languages which provide lexical closures view encapsulation as a feature of the language orthogonal to object orientation. The second definition is motivated by the fact that in many OOP languages the placement of components is not automatic or can be overridden; thus, information hiding is defined as a separate notion by those who prefer the second definition.

==As an information hiding mechanism==

Under the second definition of "hiding," the internal representation of an object is generally hidden from view outside of the object's definition. Typically, only the object's own methods can directly inspect or manipulate its fields. Some languages like Smalltalk and Ruby only allow access via object methods, but most others (e.g. C++, C#, or Java) offer the programmer a degree of control over what is hidden, typically via keywords like <code>public</code> and <code>private</code>.<ref name="PierceTypes" /> Note that the ISO C++ standard refers to <code>protected</code>, <code>private</code>, and <code>public</code> as "access specifiers" and that they do not strictly hide information.<ref name="ISO3690">{{cite web |url=https://isocpp.org/files/papers/N3690.pdf |format=PDF |title=ISO/IEC JTC 1/SC22 N3690 |publisher=ISO |pages=238–239 |date=15 May 2013 |accessdate=29 august 2014}}</ref> Information hiding is accomplished by furnishing a compiled version of the source code that is interfaced via a header file.

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 supposed benefit of encapsulation is that it can reduce system complexity, and thus increase robustness, by allowing the developer to limit the inter-dependencies between software components.<ref name="AdobeOOP">{{cite web |url=http://www.adobe.com/devnet/actionscript/learning/oop-concepts/encapsulation.html |title=Object-oriented programming concepts: Encapsulation |author=Yaiser, Michelle |publisher=Adobe Systems Incorporated |date=31 October 2011 |accessdate=29 August 2014}}</ref><ref name="PattersonDep">{{cite web |url=http://lostechies.com/chrispatterson/2014/01/03/separating-concerns-part-2-services/ |title=Separating Concerns – Part 2: Services |author=Patterson, Chris |work=Los Techies |date=03 January 2014 |accessdate=29 August 2014}}</ref>

Below is an example in C# that shows how access to a data field can be restricted through the use of a <code>private</code> keyword:
<source lang="csharp">
class Program {
public class Account {
private decimal accountBalance = 500.00m;

public decimal CheckBalance() {
return accountBalance;
}
}

static void Main() {
Account myAccount = new Account();
decimal myBalance = myAccount.CheckBalance();

/* This Main method can check the balance via the public
* "CheckBalance" method provided by the "Account" class
* but it cannot manipulate the value of "accountBalance" */
}
}
</source>

Below is an example in Java:
<source lang="java">

public class Employee {
private BigDecimal salary = new BigDecimal(50000.00);

public BigDecimal getSalary() {
return salary;
}

public static void main() {
Employee e = new Employee();
BigDecimal sal = e.getSalary();
}
}
</source>
PHP offers a more simplistic approach<ref name="PHPVis">{{cite web |url=http://php.net/manual/en/language.oop5.visibility.php |title=PHP: Visibility |work=PHP Manual |author=Achour, Mehdi; Betz, Friedhelm; Dovgal, Antony; Lopes, Nuno; Magnusson, Hannes; Richter, Georg; Seguy, Damien; Vrana, Jakub |publisher=The PHP Group |date=29 August 2014 |accessdate=29 August 2014}}</ref>:
* <code>public</code> - The method is publicly available and can be accessed by all subclasses.
* <code>protected</code> - The method/function/property is available to the parent class and all inheriting classes.
* <code>private</code> - The method is private and only available to the parent or base class.

Below is an example in PHP:

<source lang="php">
class person {
var $name;
public $height;
protected $social_insurance;
private $pinn_number;

function __construct($persons_name) {
$this->name = $persons_name;
}

function set_name($new_name) {
$this->name = $new_name;
}

function get_name() {
return $this->name;
}

}
</source>

Encapsulation is also possible in older, non-object-oriented languages. In C, for example, a structure can be declared in the public API (i.e., the header file) for a set of functions that operate on an item of data containing data members that are not accessible to clients of the API:
<source lang="csharp">
// Header file "api.h"

struct Entity; // Opaque structure with hidden members

// API functions that operate on 'Entity' objects
extern struct Entity * open_entity(int id);
extern int process_entity(struct Entity *info);
extern void close_entity(struct Entity *info);
</source>
Clients call the API functions to allocate, operate on, and deallocate objects of an opaque type. The contents of this type are known and accessible only to the implementation of the API functions; clients cannot directly access its contents. The source code for these functions defines the actual contents of the structure:
<source lang="csharp">
// Implementation file "api.c"

#include "api.h"

// Complete definition of the 'Entity' object
struct Entity {
int ent_id; // ID number
char ent_name[20]; // Name
... and other members ...
};

// API function implementations
struct Entity * open_entity(int id)
{ ... }

int process_entity(struct Entity *info)
{ ... }

void close_entity(struct Entity *info)
{ ... }
</source>

==Notes==
This article reuses numerous content elements from [http://en.wikipedia.org/wiki/ebXML the Wikipedia article].

==References==
<references />


[[Category:Software and hardware terms]]

Encapsulation (object-oriented programming) - Revision history

Shawndouglas: /* References */ Cat

Shawndouglas: /* Notes */ Corrected link

Shawndouglas: Created as needed.