I'll propose that we add a keyword "useas" useas ''discipline_name'' hier.net.reference.to.net; with the "useas" declaration, the net would not Actually be coerced to this discipline, we'd get an interface element instead.. One idea from tonights meeting. Jonathan David j.david@ieee.org jb_david@yahoo.com http://ieee-jbdavid.blogspot.com Mobile 408 390 2425 Work: jbdavid@scintera.com http://www.scintera.com 408 200-7024 ----- Original Message ---- From: Graham Helwig <graham.helwig@astc-design.com> To: Verilog-AMS Reflector <verilog-ams@eda.org> Sent: Wednesday, December 6, 2006 11:46:38 PM Subject: Hierarchical reference questions Hello, When simulating large mixed-signal design (containing transistors and gates) I have had the need to hierarchically reference an implicit net with the design. Also the resolved domain of the net is not known and even if it is known it may change from one simulation to the next. I may of missed in the LRM, but is hierarchical referencing of an implicit nets allowed in the language? If it is, then does the net need to be coerced to the same domain as the probe or does discipline resolution and ACMI resolves handle the resolution of the implicit net including any hierarchical references to that net? For example: myDesign system(.....); electrical system.inst.inst.net; // is this required? logic system.inst.net; // is this required? analog $display("Value is %g.", V(system.inst.inst.net)); initial $display("Value is %b.", system.inst.net); Regards Graham -- ========================================================== Graham Helwig AMS Verification Australian Semiconductor Technology Company (ASTC) Pty Ltd Location: 76 Waymouth St, Adelaide, SA, 5000, Australia Phone +61-8-82312782 Moblie: +61-4-03395909 Email: graham.helwig@astc-design.com Web: www.astc-design.com ==========================================================Received on Thu Dec 7 21:55:05 2006
This archive was generated by hypermail 2.1.8 : Thu Dec 07 2006 - 21:55:13 PST