From: Steven Sharp (sharp@cadence.com)
Date: Fri Feb 25 2005 - 12:52:23 PST
>Actually combination of "defparam-generate-configuration-hierRef" may cause
>lots of such
>scenario for which LRM is totally silent.
I believe that all such ambiguities are prevented by the existing LRM text,
or by fixes in the current draft standard.
The existing LRM forbids hierarchical references in constant expressions,
so a constant expression outside a generated hierarchy cannot depend on
something inside that generated hierarchy. It also forbids defparams inside
a generated hierarchy from changing values outside that hierarchy. These
two restrictions ensure that parameter information can only pass from
outside the generate construct to inside it, never the other direction.
This prevents cyclical dependencies.
There is one known ambiguous scenario with the current LRM. It is a subtle
issue involving upward name resolution, pointed out by Gord Vreugdenhil.
It was filed as erratum 604 in the ETF database, and is fixed in the current
draft standard.
Steven Sharp
sharp@cadence.com
This archive was generated by hypermail 2.1.4
: Fri Feb 25 2005 - 12:32:58 PST
and
sponsored by Boyd Technology, Inc.