Access level

In computer science and computer programming, access level denotes the set of permissions or restrictions provided to a data type. Reducing access level is an effective method for limiting failure modes, debugging time and overall system complexity. It restricts variable modification to only the methods defined within the interface to the class. Thus, it is incorporated into many fundamental software design patterns. In general, a given object cannot be created, read, updated or deleted by any function without having a sufficient access level.

The two most common access levels are public and private, which denote, respectively; permission across the entire program scope, or permission only within the corresponding class. A third, protected, extends permissions to all subclasses of the corresponding class. Access levels modifiers are commonly used in Java [1] as well as C#, which further provides the internal level.[2] In C++, the only difference between a struct and a class is the default access level, which is private for classes and public for structs.[3]

To illustrate the benefit: consider a public variable which can be accessed from any part of a program. If an error occurs, the culprit could be within any portion of the program, including various sub-dependencies. In a large code base, this leads to thousands of potential sources. Alternatively, consider a private variable. Due to access restrictions, all modifications to its value must occur via functions defined within the class. Therefore, the error is structurally contained within the class. There is often only a single source file for each class, which means debugging only requires evaluation of a single file. With sufficient modularity and minimal access level, large code bases can avoid many challenges associated with complexity.[4]

Example: Bank Balance Class

Retrieved from Java Coffee Break Q&A [5]

public class bank_balance
{
	public String owner;
	private int balance; 

	public bank_balance( String name, int dollars )
	{
		owner = name;

		if (dollars >= 0)
			balance = dollars;
		else
			dollars =0;
	}

	public int getBalance()
	{
		return balance;
	}

	public void setBalance(int dollars)
	{
		if (dollars >= 0)
			balance = dollars;
		else
			dollars = 0;		
	}
}

Here, the imperative variable balance is defined as a private int. This ensures other classes, methods and functions cannot accidentally overwrite the variable balance. Instead, they must access the interface for the class bank_balance, whose methods ensure the balance cannot drop below 0.

gollark: Anyway, hopefully you won't end up horribly addicted to stimulants or something.
gollark: Specifically the "half" bit.
gollark: Do you know how "half life" works?
gollark: Why do you have ominous helicopters™?
gollark: Interestingly, solar panels are actually about ten times as efficient as photosynthesis in plants is.

References
  1. "Controlling Access to Members of a Class (The Java™ Tutorials > Learning the Java Language > Classes and Objects)". docs.oracle.com. Retrieved 2016-11-22.
  2. "Access Modifiers (C# Reference)". msdn.microsoft.com. Retrieved 2016-11-22.
  3. "Friendship and inheritance - C++ Tutorials". www.cplusplus.com. Retrieved 2016-11-23.
  4. "Why do we need private variables?". softwareengineering.stackexchange.com. Retrieved 2016-11-22.
  5. http://www.javacoffeebreak.com/faq/faq0002.html
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.