RE: [sv-cc] Concatenation on vpiIODecl - vpiExpr relation

For the following test case:

module test (.foo({r, j}));
  output r;
  int r;
  output j;
  bit j;
endmodule

a simple test case here returns

Processing a vpiModule named test.
  Found a vpiIODecl named r.
    vpiExpr: a vpiIntVar named test.r.
  Found a vpiIODecl named j.
    vpiExpr: a vpiBitVar named test.j.

So my guess is that a vpiIODecl is not the same thing as a port, and its vpiExpr is not the same as the vpiLowConn of the port.  Rather the vpiIODecl is supposed to be accessing things declared as input, output, inout, and so on.  To put it another way, an io decl is something that is declared as an I/O (input, output, etc.).

Regards,
Jim Vellenga

From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf Of Radoslaw Nawrot
Sent: Tuesday, August 27, 2013 7:51 AM
To: sv-cc@eda.org
Subject: [sv-cc] Concatenation on vpiIODecl - vpiExpr relation

Hello,
I have simple question:
If I have concatenation on port and I get vpiExpr from io decl  should I receive vpiOperation?
According to 1800-2012 37.13 I can get only one of four objects/object's classes :
ref obj
interface tf decl
nets
variables

Is it bug in LRM, or it must be get different way ?


Thanks in advance,
Radek


--
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.