RE: [sv-bc] Glitches in unique/priority case/if violations

I think the following suggestion from Steve Sharp should be
considered as part of any comprehensive proposal to address
the usability problems with unique/priority case/if.
This is what I was alluding to when I mentioned some
kind of "pulse reject" mechanism in my earlier mail.

Regards,
Doug

-----Original Message-----
From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On
Behalf Of Steven Sharp
Sent: Monday, September 10, 2007 8:01 PM

I would think you could have the concept of a concurrent assertion
that is "clocked" by a change in any of its operands (like a
combinational block) and waits until an appropriate end-of-time
queue to evaluate in order to filter out glitches.  Is that what
you meant?


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.