Re: [sv-cc] vpiObj, vpiObjectVal

From: Jim Vellenga <jvellenga_at_.....>
Date: Thu Jan 15 2009 - 04:58:54 PST
It certainly looks like it.  This looks like another case of the dangers
of having "two copies of the truth," in that all the information in
Table 38-5 is also in Table 38-3.  My guess is that someone updated
Table 38-3 without realizing that they needed to change 38-5 as well.

Although I no longer have access to the older versions of the standard,
I'm guessing that this problem has been there for a while, and hence
needs a new Mantis item.  Yes?

Regards,
Jim Vellenga

-----------------------------------------------------------------------
Jim Vellenga (jvellenga@alum.mit.edu)
Senior software engineer for team-based development; skilled at team-
building while retaining a detailed technical knowledge of the project 
itself.  Excellent at negotiating clear definitions (standards, 
interfaces, etc.) across functional and industry boundaries.
781-646-6778
-----------------------------------------------------------------------



Bresticker, Shalom wrote:
> Hi,
>  
> The following was provoked by a note in the Verilog-AMS committee.
>  
> Table 38-5 has vpiObjectVal as the last entry. Should it be vpiObjTypeVal?
>  
> Thanks,
> Shalom
>  
> Shalom Bresticker
> Intel Jerusalem LAD DA
> +972 2 589-6582
> +972 54 721-1033
>  
>  
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>   
>
> -- 
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
> ------------------------------------------------------------------------
>
> This email was Anti Virus checked by Astaro Security Gateway. http://www.astaro.com

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Thu Jan 15 05:02:02 2009

This archive was generated by hypermail 2.1.8 : Thu Jan 15 2009 - 05:02:21 PST