Speri at 23:52, 22 September 2011

2011-09-22T23:52:55Z

← Older revision		Revision as of 23:52, 22 September 2011
Line 241:		Line 241:
	# http://download.oracle.com/javase/tutorial/java/javaOO/accesscontrol.html		# http://download.oracle.com/javase/tutorial/java/javaOO/accesscontrol.html
	# http://msdn.microsoft.com/en-us/library/wxh6fsc7.aspx		# http://msdn.microsoft.com/en-us/library/wxh6fsc7.aspx
			# http://stackoverflow.com/questions/2084801/c-using-declaration-scope-and-access-control

Speri at 22:10, 22 September 2011

2011-09-22T22:10:17Z

← Older revision		Revision as of 22:10, 22 September 2011
Line 1:		Line 1:
	'''Access Control in Object Oriented Languages'''		'''Access Control in Object Oriented Languages'''
	Each Object Oriented Language has its own way of implementing Access Control .This page discusses the various ways in which Access control is implemented in some of the Object Oriented Languages.		:Each Object Oriented Language has its own way of implementing Access Control .This page discusses the various ways in which Access control is implemented in some of the Object Oriented Languages.
	=='''Access Control'''==		=='''Access Control'''==
	Access control in programming languages provides the programmer the ability to define standards that are needed to hide the implementation of the modules from the public interface.Access control provides the programmer ,the ability to prevent under privileged users from access to internal components of a program and restricts them from changing the data within the component to an inconsistent state(i.e elements(members functions and variables) within a program(class)) there by protecting the integrity of the components .This concept of hiding the information in object oriented languages is called [http://en.wikipedia.org/wiki/Encapsulation Encapsulation].		Access control in programming languages provides the programmer the ability to define standards that are needed to hide the implementation of the modules from the public interface.Access control provides the programmer ,the ability to prevent under privileged users from access to internal components of a program and restricts them from changing the data within the component to an inconsistent state(i.e elements(members functions and variables) within a program(class)) there by protecting the integrity of the components .This concept of hiding the information in object oriented languages is called [http://en.wikipedia.org/wiki/Encapsulation Encapsulation].
Line 208:		Line 208:
	====Example====		====Example====
	To understand it in more detail consider the following the example.		To understand it in more detail consider the following the example.
	~~[[File:Access1.png\|400px\|center]]~~
	In the example each package contains two classes. Class C is a sub class of class A. Assuming class A as public then its members can be accessed like –		In the example each package contains two classes. Class C is a sub class of class A. Assuming class A as public then its members can be accessed like –
	Class A – It can access all its members independent of their access modifier.		Class A – It can access all its members independent of their access modifier.
Line 227:		Line 226:
	*"Internal": It can be used both for the types and type members. Internal types and members are accessible only by the code in the same assembly.		*"Internal": It can be used both for the types and type members. Internal types and members are accessible only by the code in the same assembly.
	*"Protected Internal": It’s a combination of protected and internal modifier. It allows the types and the members to be used by any code in the same assembly or by any derived class in another assembly. A protected internal element can be accessed in a derived class in another assembly by using an instance of the derived class.		*"Protected Internal": It’s a combination of protected and internal modifier. It allows the types and the members to be used by any code in the same assembly or by any derived class in another assembly. A protected internal element can be accessed in a derived class in another assembly by using an instance of the derived class.
			[[File:Access2.png\|400px\|center\|upright=0.56]]

	Usage of these access modifiers for all types or members is dependent on the conditions like the accessibility of the container restricts the accessibility of a type member.		Usage of these access modifiers for all types or members is dependent on the conditions like the accessibility of the container restricts the accessibility of a type member.
	*- Assembly is a physical unit that can be executed, deployed, versioned and secured.		*- Assembly is a physical unit that can be executed, deployed, versioned and secured.


	==References==		==References==
Line 237:		Line 238:
	# http://msdn.microsoft.com/en-us/library/kktasw36(v=VS.80).aspx		# http://msdn.microsoft.com/en-us/library/kktasw36(v=VS.80).aspx
	# http://www.kuzbass.ru:8086/docs/isocpp/access.html		# http://www.kuzbass.ru:8086/docs/isocpp/access.html
			# http://publib.boulder.ibm.com/infocenter/comphelp/v8v101/index.jsp?topic=%2Fcom.ibm.xlcpp8a.doc%2Flanguage%2Fref%2Fcplr130.htm
	# http://download.oracle.com/javase/tutorial/java/javaOO/accesscontrol.html		# http://download.oracle.com/javase/tutorial/java/javaOO/accesscontrol.html
	# http://msdn.microsoft.com/en-us/library/wxh6fsc7.aspx		# http://msdn.microsoft.com/en-us/library/wxh6fsc7.aspx

Speri at 01:03, 21 September 2011

2011-09-21T01:03:51Z

Show changes

Speri: Created page with "Riverside]"

2011-09-11T16:45:47Z

Created page with "[Riverside]"

New page

[[[Riverside, California|Riverside]]]

User:Speri - Revision history

Speri at 23:52, 22 September 2011

Speri at 22:10, 22 September 2011

Speri at 01:03, 21 September 2011

Speri: Created page with "Riverside]"