[sv-cc] SV-CC agenda for 08/15/2007

Our next SV-CC meeting is on 08/15/2007.

The call-in information for this meeting is as follows:

   U.S.               866-807-0627
   International      203-955-5179
   Passcode           399143

Meeting will start at 11:30am EDT (3:30pm GMT), and last for 1.5 hours.

AGENDA

1.  Review Patent information

   Go to:
     http://standards.ieee.org/board/pat/pat-slideset.ppt

2.  Review minutes from last meeting (07/18/2007 and 08/01/2007)

3.  Liaisons

   - Francoise to report on PASSED SV-BC items
   - Anyone care to make a report?

4.  New business

   - Item 1865 Definition of `s_vpi_vecval' in `svdpi.h' and `vpi_user.h'
   - Item 1946 Clarify vpiSize for string vars and other SystemVerilog variable types
   - Item 1947 vpiTask, vpiFunction for built-in method calls
   - Item 1599 The assertion API and VPI sections need changes as per mantis #805
   - Item 1361 need a way to control execution of action blocks
   - Item 1952 "Null argument" to mean "omitted argument" may be confusing
   - Item 1603 Unused vpiMultiArray declaration in vpi_user.h
   - Item 1942 Deprecated vpiArray property still appears in several places where vpiArrayMember should replace it.
   - Item 1970 What is vpiIndexTypespec for an array with a wildcard index type?
   - Item 1696 What is vpiRange for a dynamic array, assoc. array, queue?
   - Others?

5.  Review SV-CC items with proposals:

6.  Review SV-CC items with proposals (Straw poll only):

   - Others?

7.  Review old business:

    - Francoise and Bassam to continue work on assignment patterns.
    - Francoise to champion adding support for typed parameters to the
      typespec diagrams.
    - Abi to champion adding support for parameterized classes.
    - Abi/JimV to champion improving the ability to compare objects.
    - Steve to send out exact text on referring to a prior version.
    - Chas to take a look for questions from Editor in these sections
      and either answer them himself or parcel them out to other
      committee members as appropriate.



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