All: We said in our last meeting that 1682 looks ready for vote, but this proposal depends critically on 1681. I think we need to pass 1681 first. I read over 1681 and noticed a couple of things that I think need to be addressed. Please see the notes below. J.H. 2007-06-26 ---------- p. 1. The reference to Annex E needs to be changed to Annex F. p. 4. The examples with the ## delays are not clear to me. I'm not sure they were entirely clear before with the "using default clocking" comment, but now that this explanation has been struck out I am sure that they are not clear. I think there needs to be some explanation, perhaps following the examples, that says how the clocking events are determined. Maybe a different scheme of examples is needed. p. 5. In the suggested replacement text, there is something missing. The new paragraph begins is controlled by $global_clock p. 5. The reference to Annex E needs to be changed to Annex F. p. 5. Are the phrases "primary system clock" and "primary phase" defined? p. 6. In the proposed addition to 16.13.2, is the scope of the requirement of alignment to the global clock limited to the clocking events appearing in property expressions? I suppose that it applies transitively into instances of named sequences and properties. Does it apply to clocking events in action blocks or in sequence match items? pp. 10-11. I'm sure you know that the rightarrows (long mapsto) are missing in the clock rewrite rules. It would be good to fix this to avoid confusion. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Jun 26 08:33:56 2007
This archive was generated by hypermail 2.1.8 : Tue Jun 26 2007 - 08:34:04 PDT