RE: [sv-ec] Re: [sv-bc] Re: Feedback from Freescale on name resolution issues

On a related subject, generates have the following rule:

"If the generate block selected for instantiation is not named, it still
creates a scope; but the declarations within it cannot be reference
using hierarchical names other than from within the hierarchy
instantiated by the generate block itself." 

Would it make sense to apply this rule in general to unnamed procedural
blocks and to automatic scopes?

Shalom

> -----Original Message-----
> From: owner-sv-bc@server.eda.org 
> [mailto:owner-sv-bc@server.eda.org] On Behalf Of Steven Sharp
> Sent: Friday, October 19, 2007 1:47 AM
> To: Ray_Ryan@mentor.com; michael.burns@freescale.com
> Cc: gordon_vreugdenhil@mentor.com; sv-ec@server.eda.org; 
> sv-bc@server.eda.org
> Subject: Re: [sv-ec] Re: [sv-bc] Re: Feedback from Freescale 
> on name resolution issues
> 
> Mike has mentioned that there is no way to disambiguate a 
> reference in favor of a local variable if that variable is automatic.
> 
> The rule disallowing hierarchical references to automatic 
> variables was intended to prevent references from outside the 
> scope, where the variable might not exist, or where there 
> might be multiple instances of the variable in existence 
> simultaneously.
> 
> I don't see a problem with allowing a hierarchical reference 
> to an automatic variable from inside its scope, where the 
> hierarchy is just intended for name disambiguation.  Would 
> this help?  Does anyone else see a problem with this?
> 
> Steven Sharp
> sharp@cadence.com
> 
> 
> --
> This message has been scanned for viruses and dangerous 
> content by MailScanner, and is believed to be clean.
> 
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

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