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

From: Daniel Mlynek <daniel.mlynek_at_.....>
Date: Tue Oct 27 2009 - 05:10:04 PDT
Adding this  reference (11.4.13 Set membership operator) in  coverage
description will clear the LRM ambiguity. Now this is nothing said what
should happend if order of numbers in range is descending - ie:
        bins ok = {4:2};
LRM doesnt say if that bin should be emtpy ir it should be 2,3,4?
Chapter 11.4.13 in open range definition explicitly says that above range is
empty - is this inside operator description also valid for coverage bin
definition?
 
 
 
DANiel

  _____  

From: owner-sv-ec@server.eda.org [mailto:owner-sv-ec@server.eda.org] On
Behalf Of Daniel Mlynek
Sent: 26 października 2009 15:33
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 (11.4.13 Set membership operator)   should be added
here:

"The open_range_list (see 11.4.13 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. 

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Tue Oct 27 05:10:59 2009

This archive was generated by hypermail 2.1.8 : Tue Oct 27 2009 - 05:11:53 PDT