This proposal seems extreme -- http://www.eda-stds.org/svdb/view.php?id=2054 "The Data Read API has many serious problems which will prevent vendors from implementing it. Unless someone wants to step up and work on fixing them, I think the entire section should be eliminated." To help us understand the context of this proposal, could someone please send a prioritized list of these "many serious problems"? -- Brad -----Original Message----- From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of Neil Korpusik Sent: Thursday, September 20, 2007 2:27 PM To: sv-ac@eda.org; sv-bc@eda.org; sv-ec@eda.org Subject: [sv-bc] [Fwd: [sv-cc] Added Mantis item 2054 - deprecate Data Read API] Forwarding to a wider audience. Neil -------- Original Message -------- Subject: [sv-cc] Added Mantis item 2054 - deprecate Data Read API Date: Thu, 20 Sep 2007 16:09:46 -0400 From: Charlie Dawson <chas@cadence.com> To: SV-CC <sv-cc@eda-stds.org> Hi All, I've added a mantis item to deprecate the Data Read API and a proposal. We can further debate the merits of this at our next meeting. -Chas -- Charles Dawson Senior Engineering Manager NC-Verilog Team Cadence Design Systems, Inc. 270 Billerica Road Chelmsford, MA 01824 (978) 262 - 6273 chas@cadence.com -- 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. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Sep 20 14:48:27 2007
This archive was generated by hypermail 2.1.8 : Thu Sep 20 2007 - 14:49:36 PDT