Thinking a little outside the box... Gord suggested thinking about the delayed reporting as a delayed child subprocess, and the discarding of pending violations as disabling those subprocesses, much like "disable fork". There has been disagreement about when to implicitly execute that disabling operation. What if it were made an explicit operation, like "disable fork" is? You could stick a "disable assert" into the code where you wanted to discard any pending unreported violations. This seems like overkill for the typical usage of unique/priority, but perhaps it is warranted for more general usage of assertions. 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 Wed Oct 17 00:41:36 2007
This archive was generated by hypermail 2.1.8 : Wed Oct 17 2007 - 00:42:17 PDT