RE: [sv-cc] cbValueChange on SV String

I will fix this spelling error for the final LRM that will go to the IEEE.

 

Stu

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Stuart Sutherland                      

Sutherland HDL, Inc.

22805 SW 92nd Place

Tualatin, OR 97062

stuart@sutherland-hdl.com              

+1-503-692-0898

 

Training engineers to be Verilog, SystemVerilog and UVM wizards!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

From: Bresticker, Shalom [mailto:shalom.bresticker@intel.com] 
Sent: Monday, October 15, 2012 5:39 AM
To: stuart@sutherland-hdl.com
Cc: sv-cc@eda.org; Karen Pieper
Subject: FW: [sv-cc] cbValueChange on SV String

 

Stu,

 

Please fix the typo on the top line of page 1064 of Draft 6 of P1800-2012.

 

"Menber" should be "Member".

 

Thanks, Radek.

 

Regards,

Shalom

 

From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf Of Radoslaw
Nawrot
Sent: Monday, October 15, 2012 14:32
To: sv-cc@eda.org
Subject: [sv-cc] cbValueChange on SV String

 

Hi 

I'd like to ask about callback's on SystemVerilog string.

 

LRM says:

 

"cbValueChange After value change on some variables, any expression, or
terminal or after

execution of an event statement. Specifically excluded are class objects,
dynamic

arrays, strings, queues, and associative arrays."

 

Is there as reason why callback cbValueChange cannot be set on string?

 

example:

string s="a";

if I set cb on value change I can detect :

 

s="b"

 

were size is still the same 

 

BTW: LRM 1800-2009 on page 1022 have bug:

"For a cbValueChange callback, if the obj has the vpiArrayMenber property
set to TRUE" 

 

 

Regards,

Radek

 


-- 
This message has been scanned for viruses and 
dangerous content by  <http://www.mailscanner.info/> MailScanner, and is 
believed to be clean. 

---------------------------------------------------------------------
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, and is
believed to be clean.