Hi Charlie, I had an AI to list the Read API item / suggested resolution 593 -- Proposal Ready 587 -- dup of 572 588 -- dup of 572 583 -- Proposal Ready 567 -- close item, clarification added as NOTE 579 -- close item, clarification added as NOTE 573 -- No proposal, assign back to filer to list the issue and suggest resolution 570 -- Proposal Ready 571 -- Proposal Ready 561 -- Proposal Ready 572 -- Proposal Ready 560 -- Proposal Ready 559 -- close item, clarification added as NOTE 592 -- close item, clarification added as NOTE 590 -- *postpone* 584 -- Proposal Ready 581 -- close item, clarification added as NOTE 580 -- Proposal Ready 568 -- close item, clarification added as NOTE 565 -- Proposal Ready 563 -- Proposal Ready 562 -- Proposal Ready 558 -- Proposal Ready 557 -- Proposal Ready 556 -- Proposal Ready 555 -- Proposal Ready 589 -- dup of 572 2144 -- close item, clarification added as NOTE 2146 -- Proposal Ready 2147 -- close item, clarification added as NOTE -- suggest creating enhancement to elaborate in Read API on this in future 2148 -- Proposal Ready Thx. -Bassam. -----Original Message----- From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf Of Charlie Dawson Sent: Tuesday, January 29, 2008 3:11 PM To: sv-cc@eda.org Subject: [sv-cc] SV-CC agenda for 01/23/2008 Our next SV-CC meeting is on 01/23/2008. 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 EST (4: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 (01/16/2008) 3. Liaisons - Francoise to report on Champion issues - Anyone care to make a report? 4. New business - Update status of our remaining items. Here was what we had as of the last P1800 meeting: Project Owner Mantis Items Proposal available ------------------------------------------ ------------- ------------ ------------------ Class specialization JimV 2094 Now Packed arrays Chuck 1230 Now Handle lifetime Abi 2193 Now (sort of) Typed parameters Francoise 2191 Before Jan 15th Callbacks on dynamic objects JimV, Bassam, 2015 12/19/2007 Michael Values with delays on dynamic objects Chas 2190 12/19/2007 Expressions with side effects JimV 2143 Now Data Read API Bassam, Many 12/19/2007 Ghassan Better access to arrays Chuck 1688 12/19/2007 Naming issues for struct and array members Chuck 1593 12/19/2007 VPI causing new objs to exist Abi, Chuck 2192 12/19/2007 JEITA: Give a overarching name for APIs ???? 1835 TBD - Update on the Read API items - Item 1837 - sent back to us from the Champions - Items 1648, 1682, 2037, 1702 - Champions want SV-CC to review - Item 1668 - John thinks no change needed. JimV is not sure - Item 1667 - SV-AC still working on this - Item 1503 - more discussion needed? - Others? 5. Review SV-CC items with proposals: - Item 1230 How to represent packed arrays of complex types in VPI - Item 2218 Clarify meaning of vpi_compare_objects() - Item 2216 Details missing from VPI Generates object diagram - Item 2143 How should VPI handle index expressions with side effects? - Item 2054 Draft 3A, Section 40 - Deprecate Data Read API - Item 2094 Need to extend VPI to handle class specializations - Item 1599 The assertion API and VPI sections need changes as per mantis #805 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 and Bassam to figure out what should happen when you get the size of a string constant. - Chas to update Item 1570. - Chas to ask the editor about Item 0417. - Steve to write a proposal for dealing with the inconsistencies with the protection properties. - Chas to talk with editor on re-arranging the VPI that is outside of the VPI sections. - Bassam, JimV, and Lisa Piper to work on issues found in Item 1503. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Jan 29 22:20:39 2008
This archive was generated by hypermail 2.1.8 : Tue Jan 29 2008 - 22:21:00 PST