Hmm ... but then what is the role of the bind_target_scope ? It seems
it would be more useful for the hierarchical instance name to be
relative to the bind_target_scope.
J.H.
From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
Korchemny, Dmitry
Sent: Monday, September 13, 2010 8:51 AM
To: Daniel Mlynek
Cc: 'sv-ac@server.eda.org'
Subject: RE: [sv-ac] hier reference as bind target
Hi Daniel,
My understanding is that the in this case the hierarchical names are (as
elsewhere) specified relative to the scope to which the bind statement
belongs as specified in 23.6.
Regards,
Dmitry
From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
Daniel Mlynek
Sent: Wednesday, September 08, 2010 11:37 AM
To: 'sv-ac@server.eda.org'
Subject: [sv-ac] hier refernce as bind target
LRM says than as bind_target_instance_list may be a hierarchical
reference - but there is no such examples in LRM.
I'm not sure if this how hierarchical reference should work in this
context.
Those hierarchical identifiers should be relative to context where bind
is placed or relative to bind target?
I assume that global hier refs or hier refs starting with $root are also
allowed.
Snippet from LRM:
bind bind_target_scope [: bind_target_instance_list]
bind_instantiation ;
bind_target_instance ::=
hierarchical_identifier constant_bit_select
bind_target_instance_list ::=
bind_target_instance { , bind_target_instance }
bind bind_target_scope : hierarchical_identifier
constant_bit_select bind_instantiation ;
-- This message has been scanned for viruses and dangerous content by MailScanner <http://www.mailscanner.info/> , 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 <http://www.mailscanner.info/> , and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Mon Sep 13 11:11:16 2010
This archive was generated by hypermail 2.1.8 : Mon Sep 13 2010 - 11:11:21 PDT