RE: [sv-ac] call to vote on 1900

Hi Shalom,

I agree with you that this is consistent with other constructs of the
language however checkers can be declared also outside of a module as in
the example on page 8 of the proposal:

	checker my_check (test_sig, clock);
		  default clocking @clock;
		  a1: assert property
(prop_declared_elsewhere(test_sig));
		  c1: cover property (!test_sig ##1 test_sig);
	endchecker : my_check
	module m(logic rst);
		wire clk;
		logic a, en;
		wire b = a && en;
		// Checker instantiation outside of procedural code
		check check_outside(b, clk);
        ...

Based on these examples I imagined other scoping rules (where
"prop_declared_elsewhere" appears somewhere inside the module) but if I
was wrong then simply those examples needs to be fixed - they can work
only if you define the checker inside another scope (module).

Yaniv
 


-----Original Message-----
From: Bresticker, Shalom [mailto:shalom.bresticker@intel.com] 
Sent: Tuesday, November 13, 2007 22:23
To: Fais Yaniv; sv-ac@eda.org
Subject: RE: [sv-ac] call to vote on 1900

Yaniv, 

> * page 8: it is mentioned:
> "Variables used in a checker that are neither formal arguments to the 
> checker nor internal variables of the checker are resolved according 
> to the scoping rules from the scope in which the checker is declared."
> Don't you mean where the checker is *instantiated* instead of declared

> ?

No. "declared" is correct. This is consistent with other constructs of
the language.
---------------------------------------------------------------------
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.