[Switching back from selected to hierarchical naming through a virtual interface] > I think that what you hope to have (or expect to have) is > that given "obj.vintf.a.b.c" that "a.b.c" will be treated > as a hierarchical reference *relative to* the actual > interface instance referenced by obj.vintf. Precisely so. If you, Mark and the other experts are happy that this won't present a problem provided "a.b.c" is a downward path from whatever instance vintf points to, then I'm OK. > The only time in which you would care is if "a.b.c" ended > up resolving upwards with respect to the actual instance. Personally I would have no problem with prohibiting that. I can imagine situations where it would be nice to point a vintf at one of a set of sibling interfaces, and be able from any one of them to reach their common parent in the statically-instanced hierarchy; but I don't want to rock the boat, since plainly there are other ways to get the desired effect in practice. Thanks -- Jonathan Bromley, Consultant DOULOS - Developing Design Know-how VHDL * Verilog * SystemC * e * Perl * Tcl/Tk * Project Services Doulos Ltd. Church Hatch, 22 Market Place, Ringwood, Hampshire, BH24 1AW, UK Tel: +44 (0)1425 471223 Email: jonathan.bromley@doulos.com Fax: +44 (0)1425 471573 Web: http://www.doulos.com The contents of this message may contain personal views which are not the views of Doulos Ltd., unless specifically stated. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Sep 25 10:01:24 2007
This archive was generated by hypermail 2.1.8 : Tue Sep 25 2007 - 10:02:02 PDT