Hi Yaniv: > 3. in 16.15.1 - if this definition correlates to the abstract grammar > then I think definition for the weak and strong operators is missing > (whereas always , eventually and reject_on operators are redundant since > those are derived but that is OK) Clock flow depends on the syntax that the user writes. E.g., a clock does not flow out of enclosing parentheses. Whenever the concept depends on syntax, it may not be the case that the semantic definition of the derived form can be used to get the desired definition of the concept. We have a similar situation with the non-vacuity relation. It would be good to make the clock flow definition complete, but that is not going to happen for 2008. I would like to resolve 1296 first and rewrite Annex F with clocks in a way that aligns with clock flow and then revise Clause 16. We decided a while back that we would not try to resolve 1296 for 2008. J.H. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Jan 24 09:58:27 2008
This archive was generated by hypermail 2.1.8 : Thu Jan 24 2008 - 09:58:59 PST