Changes between Version 32 and Version 33 of NameSpaces


Ignore:
Timestamp:
2017-09-12 11:33:46 (8 years ago)
Author:
archibald
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NameSpaces

    v32 v33  
    44== Namespaces : Context == 
    55We need to create name spaces.[[BR]][[BR]] Namespaces are 
    6  
    7  * commonly structured as hierarchies to allow reuse of names in different contexts. 
     6 * a labeled/named subset of identified/labeled content, 
     7  * content can then be precisely identified with a compound identfier - the conjuction of the subset name and the content name. 
     8 * commonly structured as nested hierarchies to allow reuse of names in different contexts. 
    89 * typically employed for the purpose of grouping symbols and identifiers around a particular functionality and to avoid name collisions between multiple identifiers that share the same name. 
    910 * hierarchical, ie sets of namespaces can be nested within another namespace 
     
    1112== Namespaces : Examples == 
    1213=== In TDX === 
    13 {{{ NAMESPACE $project }}} 
     14'''{{{ NAMESPACE $project }}}''' 
    1415 
    1516Puts anything following in the current project context 
    1617 
    17 || {{{ NAMESPACE $project:subComponent }}} || {{{ NAMESPACE subComponent }}} || 
     18'''{{{ NAMESPACE $project:subComponent }}}''' 
     19OR 
     20'''{{{ NAMESPACE subComponent }}}''' 
    1821 
    19 Puts everyting that follows 
     22Puts everyting that follows into the project's subComponent namespace 
    2023 
    2124=== In VDX ===