The problem described in IR2131 is: vhpiClassKindT enum type does not contain values for concrete classes: concProcCallStmt and seqProcCallStmt instead of abstract class procCallStmt. There does not appear to be any difference in the members of the two concrete classes, and the use of the abstract class members is adequate. Whether the call is concurrent or sequential can be determined from the parent object hierarchy. The solution described in IR2131 is: "vhpi_user.h" requires update and synchronization with VHPI information model. For the classes concProcCallStmt and seqProcCallStmt this would be adding vhpiConcProcCallStmtK and vhpiSeqProcCallStmtK to vhpiClassKindT enum type. This solution would require the enum value to be changed either for concurrent or sequential procedure calls, and hence VPI code which relied on this value would no longer work. This does not seem to be a good idea, particularly as no practical problem has been demonstrated. Therefore I am not in favour of this change. Regards, Peter Flake -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Oct 10 09:39:31 2013
This archive was generated by hypermail 2.1.8 : Thu Oct 10 2013 - 09:40:05 PDT