We now have *two* existence proofs from Doron - one in his state transition diagram, one in an email - for how hard it is to spell "$assertnonvacuouson" correctly :-) I agree with Doron's position but I don't think there is any need to change the task names or intended behaviours at this stage. I merely expressed a concern about clarity. Users will not call these tasks a large number of times, in practical code; so I have absolutely no problem with the need to make two calls in succession to achieve the desired effect. But we *must* know what happens. A state diagram like Doron's is ideal. Attached is my attempt at the same diagram, for the tasks currently proposed by 1361. Just a thought: Since the behaviour of these tasks is stateful, has anyone considered the possibility of inquiry functions to find out what the current state is of any given assertion? You could easily do that by allowing $assertpasson and $assertvacuouson to be used either as tasks or as functions returning a bit; when used as functions they could indicate the current state. -- 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.
This archive was generated by hypermail 2.1.8 : Thu Mar 29 2007 - 01:53:38 PDT