RE: [sv-ec] 19.5 lack of reference to open_range_list

True - sorry I copy&paste wrong reference.
I wanted 11.4.13
(11.4.13 Set membership operator)
 
 
DANiel

  _____  

From: Bresticker, Shalom [mailto:shalom.bresticker@intel.com] 
Sent: 26 października 2009 15:44
To: Daniel Mlynek; sv-ec@server.eda.org
Subject: RE: [sv-ec] 19.5 lack of reference to open_range_list


18.5.3 does not define open range list. Perhaps you want 11.4.13.
 
Shalom


  _____  

From: owner-sv-ec@server.eda.org [mailto:owner-sv-ec@server.eda.org] On
Behalf Of Daniel Mlynek
Sent: Monday, October 26, 2009 4:33 PM
To: sv-ec@server.eda.org
Subject: [sv-ec] 19.5 lack of reference to open_range_list



LRM "19.5 Defining coverage points" says

"The open_range_list used to specify the set of values associated with a bin
shall be constant expressions (see 11.2.1), instance constants (for classes
only), or non-ref arguments to the coverage group. It shall be legal to use
the $ primary in an open_value_range of the form [ expression : $ ] or [ $ :
expression ]."

There is lack of reference to open_range_list definittion. Maybe such
reference to chapter '18.5.3 Set membership'  should be added here:

"The open_range_list (see 18.5.3 for open range list definition) used to
specify the set of values associated with a bin shall be constant
expressions (see 11.2.1), instance constants (for classes only), or non-ref
arguments to the coverage group. It shall be legal to use the $ primary in
an open_value_range of the form [ expression : $ ] or [ $ : expression ]."

DANiel


-- 
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.