This is probably too late, but I only just caught up with my email backlog after being away... I think there is an ambiguity, or at least a lack of clarity, in the proposed new clause "22.9 Assertion action control system tasks". Do the $assertpasson/$assertpassoff tasks enable/disable the action on nonvacuous pass, or both vacuous and nonvacuous passes? If they control all forms of pass action, how do they interact with $assertvacuouson/off? For example, if I do initial begin $assertpassoff; $assertvacuousoff; $assertpasson; end what will happen - is the $assertvacuousoff sticky, so that the later $assertpasson enables only non-vacuous successes? It might be preferable to express the effect in terms of three flags for each assertion, one flag to enable each action - fail, non-vacuous success, vacuous succes - and then describe the effect of the $assert... tasks on those flags. -- 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 This e-mail and any attachments are confidential and Doulos Ltd. reserves all rights of privilege in respect thereof. It is intended for the use of the addressee only. If you are not the intended recipient please delete it from your system, any use, disclosure, or copying of this document is unauthorised. 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 Wed Mar 28 03:20:33 2007
This archive was generated by hypermail 2.1.8 : Wed Mar 28 2007 - 03:21:00 PDT