Difference between revisions of "Naming"
From Organic Design wiki
m (Caretaker: Format cat links) |
(see Wikipedia:Name binding) |
||
| Line 1: | Line 1: | ||
[[Category:Nodal Concepts]][[Category:Philosophy]] | [[Category:Nodal Concepts]][[Category:Philosophy]] | ||
{{stub}} | {{stub}} | ||
| + | = General = | ||
*Naming is often talked about in spiritual texts as a problem which is difficult to overcome | *Naming is often talked about in spiritual texts as a problem which is difficult to overcome | ||
*One of the main problems is that names are easily confused with what they refer to | *One of the main problems is that names are easily confused with what they refer to | ||
| + | |||
| + | = Computer programming = | ||
| + | In programming languages, ''name binding'' refers to the association of [[w:Value (computer science)|value]]s with [[w:identifier|identifier]]s. An identifier bound to a value is said to ''[[w:Reference (computer science)|reference]]'' that value. Since computers themselves have no notion of identifiers, there is no binding at the [[w:machine language|machine language]] level — name binding is an [[w:abstraction|abstraction]] provided by programming languages. Binding is intimately connected with [[w:scope (programming)|scoping]], as scope determines when binding occurs. | ||
| + | |||
| + | Use of an identifier Id in a context that establishes a binding for Id is called a binding (or defining) occurrence. Other occurrences in expressions, assignments and subprogram calls an identifier stands for what it is bound to; such occurrences are called applied occurrences. | ||
*In IT naming becomes a problem when names from different interacting technologies conflict | *In IT naming becomes a problem when names from different interacting technologies conflict | ||
*Changes in names can cause problems if the information of the change is not universal | *Changes in names can cause problems if the information of the change is not universal | ||
| + | *see [[Wikipedia:Name binding]] | ||
| − | + | = The nodal take on naming = | |
| − | |||
| − | |||
*names and GUID's - guids are meaningless and unseen, there is no attachment to any one more than another | *names and GUID's - guids are meaningless and unseen, there is no attachment to any one more than another | ||
*the [[Identity]] organisation | *the [[Identity]] organisation | ||
| Line 14: | Line 19: | ||
*See [[key-as-reference]] for details of non-name-based data structure | *See [[key-as-reference]] for details of non-name-based data structure | ||
| − | + | = See also = | |
| − | |||
*[[Spiritual Truth and its many Names]] | *[[Spiritual Truth and its many Names]] | ||
Revision as of 00:50, 16 December 2006
|
General
- Naming is often talked about in spiritual texts as a problem which is difficult to overcome
- One of the main problems is that names are easily confused with what they refer to
Computer programming
In programming languages, name binding refers to the association of values with identifiers. An identifier bound to a value is said to reference that value. Since computers themselves have no notion of identifiers, there is no binding at the machine language level — name binding is an abstraction provided by programming languages. Binding is intimately connected with scoping, as scope determines when binding occurs.
Use of an identifier Id in a context that establishes a binding for Id is called a binding (or defining) occurrence. Other occurrences in expressions, assignments and subprogram calls an identifier stands for what it is bound to; such occurrences are called applied occurrences.
- In IT naming becomes a problem when names from different interacting technologies conflict
- Changes in names can cause problems if the information of the change is not universal
- see Wikipedia:Name binding
The nodal take on naming
- names and GUID's - guids are meaningless and unseen, there is no attachment to any one more than another
- the Identity organisation
- All aspects changeable means that any concepts can have any number of names (only GUID's are fixed)
- See key-as-reference for details of non-name-based data structure
