[sv-cc] I updated errata 80

>X-Authentication-Warning: server.eda.org: majordom set sender to
>owner-sv-cc@eda.org using -f
>X-Sender: fm@gda.cadence.com
>X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
>Date: Mon, 16 Aug 2004 14:51:41 -0400
>To: sv-cc@eda.org
>From: Francoise Martinolle <fm>
>Subject: [sv-cc] Updated errata 80
>X-Received: By mailgate2.Cadence.COM as LAA05046 at Mon Aug 16 11:52:25 2004
>X-Virus-Scanned: clamd / ClamAV version 0.74, clamav-milter version 0.74a
> on server
>X-Virus-Scanned: clamd / ClamAV version 0.74, clamav-milter version 0.74a
> on server
>X-Virus-Status: Clean
>X-Virus-Status: Clean
>Sender: owner-sv-cc@eda.org
>X-pstn-levels: (S:99.90000/99.90000 R:95.9108 P:95.9108 M:98.6627
>C:79.5348 )
>
>I just updated errata 80 with the following:
>
>I thought about this property a little bit more. Its purpose in sv31a is
>not clear because we never had a description for this property as we only
>illustrate it with an example.
>If the purpose of this property is to indicate that a typespec has a
>typedef declaration, perhaps it is equivalent to say that a typespec has a
>name and query the vpiName property and checking for a non null string.
>
>If the purpose of this property is to indicate that it is a typedef of an
>alias, it is equivalent as querying the method vpiTypedefAlias and checking
>for a non null handle return.
>
>in either case, there is already a way to find this information, so I would
>suggest to remove this property from the standard.
>We can keep the iteration method vpiTypedef which would only return the
>typespecs which have an explicit typedef.
>
>If people agree to this analysis, I will make a formal proposal.
>
>Francoise
>'
Received on Tue Sep 21 13:03:31 2004