> I like 1715. It is good for consistency Yeah, me too, but when everyone agreed it was a bad idea to allow (cb) to be assigned to an event handle, I thought it wasn't worth the bother of fighting for it. I can easily clocking cb @(...); endclocking event cb_e; always @(cb) -> cb_e; And now I can pass references to cb_e around the place, wait on cb_e.triggered, and so on. I'm happy (ish). I have lost nothing - my input clockvars are already updated when @cb_e fires, and I still have plenty of time left in the timeslot to drive my output clockvars. And I can remotely mimic ##0 using wait(cb_e.triggered). -- 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 Mon Apr 30 11:05:00 2007
This archive was generated by hypermail 2.1.8 : Mon Apr 30 2007 - 11:05:10 PDT