I have no opinion on the issue, but as to why someone might want assertion constructs in a clocking block, Ed previously wrote: "I could see a case where the user has a clocking block for specifying sampling and driving and wants to put assertions on the signals that are marked as input, output, ... BUT, I hope that it will not confuse the user that the assertions sample at 1step while the clocking block specifies some other sampling and driving offset." Shalom > I think we need to review the way assertion constructs > can or cannot be put into clocking blocks, interfaces, and > modports. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Feb 22 02:33:09 2007
This archive was generated by hypermail 2.1.8 : Thu Feb 22 2007 - 02:33:23 PST