Uniform access principle

The uniform access principle of <a href="/facts/Computer_programming/QmSsFnu0">computer programming</a> was put forth by <a href="/facts/Bertrand_Meyer/fHywGneP">Bertrand Meyer</a> (originally in his book <a href="/facts/Object-Oriented_Software_Construction/u0uN1QpV">Object-Oriented Software Construction</a>). It states "All services offered by a <a href="/facts/Modular_programming/sNoqKvRD">module</a> should be available through a uniform notation, which does not betray whether they are implemented through storage or through computation." This principle applies generally to the <a href="/facts/Syntax_(programming_languages)/zM5oInza">syntax</a> of <a href="/facts/Object-oriented/TxNMEcao">object-oriented</a> <a href="/facts/Programming_languages/cWTYbgWa">programming languages</a>. In simpler form, it states that there should be no syntactical difference between working with an <a href="/facts/Attribute_(computing)/EpQSmn02">attribute</a>, pre-computed <a href="/facts/Property_(programming)/MRIIAw5g">property</a>, or <a href="/facts/Method_(computer_science)/8kAXxVYs">method</a>/<a href="/facts/Information_retrieval/MFSmpeNw">query</a> of an object.
While most examples focus on the "read" aspect of the principle (i.e., retrieving a value), Meyer shows that the "write" implications (i.e., modifying a value) of the principle are harder to deal with in his monthly column on the <a href="/facts/Eiffel_(programming_language)/gEzPjzmn">Eiffel programming language</a> official website.

Uniform access principle open-in-new

Uniform access principle