Hi All,
I've been looking at some of the SV-CC Immediate items that do not have
proposals yet, and here are my observations and opinions:
005 joao        Compatibility of Section E.6.7 of SV3.1A with IEEE PLI aval and bval
   I've added a proposal for this one, which is straight forward.
053 fm          VPI access to instances and packages is incorrect
   This is a very important diagram, and I agree with Francoise that this should be
   corrected.  The way it is now will be confusing for application developers.  I
   also think that this could be done relatively quickly, but not in our meeting today.
054 chas        What is the vpiFullName of a package?
055 chas        fullnames of declarations in the global scope of a compilation unit
056 chas        vpi_handle_by_name on imported items?
   I think these three need to be addressed.  They all boil down to the same question,
   "Can an object be refered to in an un-ambiguous way?".  Unfortunately, I am not
   well versed enough in all the intricate details of packages, compilation units, ...etc.
   to write these proposals without some review by others and we have run out of time.
057 fm          VPI cannot access the dependent packages for a given instance
   I think this one can be postponed until the next version of the specification.
-- Charles Dawson Senior Engineering Manager NC-Verilog Team Cadence Design Systems, Inc. 270 Billerica Road Chelmsford, MA 01824 (978) 262 - 6273 chas@cadence.comReceived on Wed Dec 1 08:08:24 2004
This archive was generated by hypermail 2.1.8 : Wed Dec 01 2004 - 08:08:29 PST