If this used the assertion mechanism, then the performance impact would no longer be small. That starts costing a lot. If you wanted to be able to control the warnings on a per-instance basis and turn them on and off during runtime, the costs would start to approach that of assertions. My comment that the performance impact would be relatively small only applies if the warnings are permanently on or off for the simulation, and this is decided at compile time. And of course, if the warnings are not actually happening. Steven Sharp sharp@cadence.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu May 7 12:06:08 2009
This archive was generated by hypermail 2.1.8 : Thu May 07 2009 - 12:06:46 PDT