RE: [sv-ac] 1900 Checkers

Yes, defining checkers within other entities is like having nested
modules or nested interfaces. I assume that normally checkers will be
declared in the compilation unit scope.

 

Thanks,

Dmitry

 

________________________________

From: Bresticker, Shalom 
Sent: Sunday, September 23, 2007 8:29 AM
To: Seligman, Erik; Lisa Piper; Korchemny, Dmitry;
Thomas.Thatcher@sun.com
Cc: sv-ac@server.eda-stds.org
Subject: RE: [sv-ac] 1900 Checkers

 

So it would be like a nested module or a nested interface?

 

Shalom

	 

	
________________________________


	From: owner-sv-ac@server.eda.org
[mailto:owner-sv-ac@server.eda.org] On Behalf Of Seligman, Erik
	Sent: Sunday, September 23, 2007 4:39 AM
	To: Lisa Piper; Korchemny, Dmitry; Thomas.Thatcher@sun.com
	Cc: sv-ac@server.eda-stds.org
	Subject: RE: [sv-ac] 1900 Checkers

	 

	Lisa-the intention was not that checkers have to be defined in a
module.  They may be declared within a module, or outside a module.   In
an OVL-like library, the checkers would be defined as standalone
objects.  

	 

	Dmitry-maybe we should state this more explicitly?

	 

	
________________________________


	 

	I could use some more up front information on the use model. I
thought this was to be similar to OVL but get around the issues that
result from having it conform to a module definition.  But if it has to
be defined in a module, then how is it used as a general library
element?  If I define the checker in module a, then how do I reference
it from module b?  I feel like I'm missing something important.

	 

	lisa

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