RE: IEEE - Latest Constraints revisions

Hi Andy,

You wrote
"
In section 10.2.10, "Generatable paths and the sampling of inputs," on PDF page 10 the paragraph:
An otherwise generatable path can be defined as input to a constraint using the read_only() syntax, e.g., keep x<read_only(y). In this case, the set of values y can take is unaffected by the constraints on x.  The parameter y is treated as an input.
would be grammatically correct if written as:
A non-generatable path can be transformed into a generatable path if it is defined as an input to a constraint using the read_only() syntax, e.g., keep x < read_only(y). In this case, the set of values y can take is unaffected by the constraints on x. The parameter y is treated as an input.
"

I'd like to point out that one cannot make a non-generatable path generatable. Impossible.

However, what one can do is to make a generatable path non-generatable, using read_only(<>).
This is what this paragraph tried to capture.

-hannes

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.