[sv-bc] RE: [sv-cc] SV-CC Meeting Minutes for 08/29/2007

hi all
My reasons for floating the idea of deprecating the Read API are
pragmatic:
- no one has implemented it as far as we know
- no one is championing it, i.e., actually doing the required work to
fix the LRM problems with it
- the Read API is not just a NO-OP, but actively a drain on the SV-CC,
because of outstanding Mantis items
- it's relevance slips out of date while the above are true and time
passes, so if a champion were to step up, they would probably rather
start from scratch anyway, building on the experience that has been
gained with SV

It's a big enough project that it really needs an active champion to
keep it alive; proposing deprecation might bring someone forward, if
not, then maybe it deserves to be deprecated.

Abi

-----Original Message-----
From: owner-sv-cc@server.eda.org [mailto:owner-sv-cc@server.eda.org] On
Behalf Of Jim Vellenga
Sent: Tuesday, September 04, 2007 5:24 AM
To: Bresticker, Shalom; Charlie Dawson; sv-cc@server.eda.org
Cc: sv-bc
Subject: RE: [sv-cc] SV-CC Meeting Minutes for 08/29/2007

That's a nice intention, of course, and one of which I personally was
unaware.  But do you know of anyone who is actually using the read API
as of yet?  The vendor representatives who were at the SV-CC meeting
were not
-- although that doesn't ensure that no vendor is supporting it yet.

In addition, I recall that someone, at least, was asking for extensions
to VCD to support SystemVerilog anyhow.
But I don't remember who that was.

Regards,
Jim Vellenga

--------------------------------------------------------- 
James H. Vellenga                            978-262-6381 
Software Architect                              (FAX) 978-262-6636 
Cadence Design Systems, Inc.         vellenga@cadence.com 
270 Billerica Rd
Chelmsford, MA 01824-4179
"We all work with partial information." 
----------------------------------------------------------  

]-----Original Message-----
]From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On ]Behalf Of
Bresticker, Shalom
]Sent: Saturday, September 01, 2007 3:10 PM
]To: Charlie Dawson; sv-cc@eda.org
]Cc: sv-bc
]Subject: RE: [sv-cc] SV-CC Meeting Minutes for 08/29/2007 ] ]But the
read API is a replacement for VCD, isn't it?
]
]VCD does not cover all SV constructs, and the read API was done instead
]of extending the VCD. That is what I understood. 
]
]>    - Chas noted that there were 21 new items related to the read API.
]>      Every time he tried to solve any of them, he ended up wanting to
]>      rewrite the entire section.  Abi would consider moving 
]> to deprecate
]>      the read API.  She will consider filing a Mantis item on it.
]
]Shalom
]
]--
]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.