Yup, that reflects the semantics and should be alright grammatically (although being German, I'm not the expert here...) From: Andrew Piziali [mailto:andy@piziali.dv.org] Sent: 21 July 2014 19:09 To: Hannes Froehlich Cc: ieee1647@eda.org Subject: Re: IEEE - Latest Constraints revisions Hannes, you wrote: 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. Aha. Then, perhaps the following rendering would be both grammatically and functionally correct: A path that is generatable but is not intended to be generated may be modified by defining it as an input to a constraint using the read_only() syntax, as in keep x < read_only(y). In this case, the set of values that y can assume is unaffected by the constraints on x. The parameter y is treated as an input. How about that Hannes? -- Andy@Piziali.dv.org<mailto:andy@piziali.dv.org> [cid:image001.png@01CFA533.94F2D0D0] PGP Key ID: 6F66CA9F<http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6F66CA9F> "To believe in your own thought, to believe that what is true for you in your private heart is true for all men--that is genius." -- Ralph Waldo Emerson -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
This archive was generated by hypermail 2.1.8 : Mon Jul 21 2014 - 14:32:47 PDT