[John Havlicek] > I'm not sure that your diagram is faithful to the current > written descriptions of the behaviors of the assertion action > control tasks I was not involved in the discussions, so I don't doubt I have missed some of the subtleties. My intent was not to change what you have already decided, but only to clarify it. Changing the diagram to match your intent is fine by me. However, I suspect you should question the wisdom of introducing a state in which *only* vacuous successes trigger the pass action. I cannot imagine a scenario in which this is useful (except for certain kinds of debugging, which could be done other ways); and I can easily imagine it leading to user confusion. I agree that the lack of a single transition from "no reporting" to "report only nonvacuous" is perhaps unfortunate. Clearly one can live without it, and I felt that Doron's proposal was perhaps too disruptive at this late stage. Over to you experts; sorry to have interfered! -- Jonathan Bromley, Consultant DOULOS - Developing Design Know-how VHDL * Verilog * SystemC * e * Perl * Tcl/Tk * Project Services Doulos Ltd. Church Hatch, 22 Market Place, Ringwood, Hampshire, BH24 1AW, UK Tel: +44 (0)1425 471223 Email: jonathan.bromley@doulos.com Fax: +44 (0)1425 471573 Web: http://www.doulos.com The contents of this message may contain personal views which are not the views of Doulos Ltd., unless specifically stated. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Mar 29 05:09:58 2007
This archive was generated by hypermail 2.1.8 : Thu Mar 29 2007 - 05:10:19 PDT