IR2131 inconsistent class info in vhpi_user.h

From: Peter Ashenden <peter_at_.....>
Date: Wed Jun 18 2008 - 21:40:27 PDT
Folks,

IR2131 points out some inconsistencies between the VHPI information model
and the enum values provided for concrete classes in vhpi_user.h. If you
look at the HTML report for the information model, it includes a list of
classes, differentiating between abstract and concrete classes. I compared
this with the definition of vhpiClassKindT in vhpi_user.h and found the
following discrepancies.

1. The following concrete classes are not represented by enum values:

aliasedName
concAssertStmt
concProcCallStmt
expr
foreverLoop
name
seqAssertStmt
seqProcCallStmt
seqSigAssignStmt

2. The following enum values represent abstract classes and should be
deprecated:

vhpiAssertStmtK
vhpiLoopStmtK
vhpiProcCallStmtK

3. The enum value vhpiProtectedTypeK should be vhpiProtectedTypeInstK.
Probably this should be done by deprecating vhpiProtectedTypeK and adding
vhpiProtectedTypeInstK.

4. The enum value vhpiOperatorK does not correspond to any class and should
be deprecated.

Note that the vhpi_user.h file includes a number of other enum types for
associations between classes. We should probably check them for consistency
against the information model at some stage.

Cheers,

PA

--
Dr. Peter J. Ashenden         peter@ashenden.com.au
Ashenden Designs Pty. Ltd.    www.ashenden.com.au
PO Box 640                    VoIP: sip://0871270078@sip.internode.on.net
Stirling, SA 5152             Phone: +61 8 7127 0078
Australia                     Mobile: +61 414 70 9106 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Wed Jun 18 21:41:46 2008

This archive was generated by hypermail 2.1.8 : Wed Jun 18 2008 - 21:41:49 PDT