Hierarchical references

Hi all,

There was a discussion about what is allowed/disallowed using 
hierarchical naming convention. Finally we thought it was good to have a 
separate section in the original chapter 7 (now chapter 6 i guess) for 
including just the valid options and semantic restrictions on the 
hierarchical usage. I am sending a proposal for the same (6.6.1 or 6.7.1 
subsection). Its probably little bit restrictive at this point but the 
usage below doesn't impact the language in a big way and is probably 
consistent with the usage today, and we can look at removing some of the 
restrictions moving forward.

Section 6.6.1: Usage of hierarchical references

The following usage rules and semantic restrictions will be applied to 
identifiers referred hierarchically in a mixed signal module

* Potential & flow access for named branches can be done hierarchically
* Access of variable values can be done hierarchically
* It shall be an error to contribute to or access an unnamed 
hierarchical branch
* It shall be an error to have potential & flow contributions to named 
branches hierarchically
* It shall be an error to assign to a variable using hierarchical notation

When accessing variable values and probes on named branches the value as 
per the last iteration shall be returned (to avoid race conditions) and 
without affecting any partial dependencies. Hierarchical access or 
branches & variables are purely considered as value access without the 
derivative component.

Regards,
Sri
-- 
Srikanth Chandrasekaran
Design Technology (Tools Development)
Freescale Semiconductor Inc.
T:+91-120-439 5000 p:x3824 f: x5199

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.