[sv-cc] FW: Updated compatibility proposal

This was sent via the reflector over an hour ago, but it seems it
may not be working, as no one here at Cadence has received it.
So, I'm trying this again, but this time without the proposal attached
to see if that helps (cc'ed direct to all interested parties I could
think of- if you do not receive a reflector version also, please
forward to other SV-CC participants not included).

Please download the updated .pdf from Mantis directly assuming you did
not get the original posting.  I believe this is complete enough to vote
on, if we are in substantial agreement on this.

Abi, FYI- I opted for the new VPI property 'vpiCompatibilityMode' vs.
the
'vpi_get_compatibility' function you proposed, because it seemed easier
to add (and we would have needed the new mode values in the header
anyway).
Regards,
Chuck

-----Original Message-----
From: Chuck Berking 
Sent: Thursday, April 26, 2007 12:45 PM
To: sv-cc@eda-stds.org
Subject: Updated compatibility proposal

All-
I have uploaded the attached updated compatibility proposal
to Mantis item #1385 (for discussion in Tuesday's 5/1 agenda).

The following changes have been included:
1) I have amplified description text in response to feedback from Abi,
   emphasizing the intended use-model (design vs. VPI compatibility);
2) I have removed 'vpiMultiArray' from the incompatibility table
   (as per Michael's feedback); there are now 8 items.
3) I have added the 1800-2008 mode (per Michael & Abi's inputs);
4) Insert for header "vpi_user.h" is now complete (with 2008 mode).
5) I have added a new integer property 'vpiCompatibilityMode', with mode
   values (for "sv_vpi_user.h").

Pre-meeting feedback & comments welcomed.
Regards,
Chuck

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.