Index: trunk/doc/user/06_features/hierarchic/index.html
===================================================================
--- trunk/doc/user/06_features/hierarchic/index.html (revision 10194)
+++ trunk/doc/user/06_features/hierarchic/index.html (revision 10195)
@@ -33,7 +33,7 @@
design.
In a non-hierarchic case every component and network are in a single
-global namespace. In practice this means:
+project global namespace. In practice this means:
- if two or more concrete symbols have the same name, they are merged into a single abstract component
- if two or more concrete nets have the same name, they are merged into a single abstract net
@@ -62,12 +62,12 @@
Scopes, addressing
- Basic: using only the global scope
+ Basic: using only the project global scope
In the simplest setup each child sheet is used only once. There are two
ways to make connections across sheets:
- - by naming nets and components in any sheet; they all end up in the global namespace
+
- by naming nets and components in any sheet; they all end up in the project global namespace (also called global namespace)
- by connecting the sheet ref sym's terminal on the parent sheet
@@ -268,6 +268,35 @@
safer choice.
+
Expert: scope summary and explicit global scoping
+
+A full list of hierarchic name prefixes (and their scopes) can be
+found in the design document.
+
+The system is designed so that:
+
+ the auto scope, when no prefix is prepended to the net name,
+ usually does what's expected, searching from local to global, then if
+ no existing net of the same name is found, creating a new globla net.
+ This is the only addressing used in the flat (non-hierarchic) case and
+ the most commonly used addressing for non-local objects in the
+ hierarchic case
+ it offers an easy to use ./ prefix, which is the most commonly used
+ local scope prefix in the hierarchic case, locking the given object
+ into the current sheet
+ offers a less often used subtree local mechanism for real complicatedcase,
+ prefixed with v/ for "search downward" or ^/ for "search upward"
+ offers the exotic / prefix for explicitly addressing the global scope.
+
+The explicit global scope prefix can be used in the real exotic case when
+a (near) bottom child sheet needs to address a project global net not being sure
+there was no same named sheet local or subtree local net in the hierarchy.
+The auto scope (no prefix) or the ./ or ^/ prefixes would pick up those
+intermediate nets, may they exist, not reaching the global scope. The / prefix
+turns off the search mechanism and searches right in the project global namespace;
+if the object is not found, it is created in the project global namespace.
+
+
Expert: component addressing