Re: [sv-ec] Ballot issue #106

From: David Scott <david_scott_at_.....>
Date: Fri Apr 24 2009 - 09:36:56 PDT

Sorry, I meant the bit about const ref.  It seems to me that was not raised as a ballot issue so it out of scope.

As for warning vs. error, I don't have a really strong opinion.  Is it an error to declare something as an output yet not actually assign it?  That's the analogue of the covergroup case.  Why is that necessarily an error?  True, in the covergroup case, it cannot be assigned, but it depends whether you consider that a serious mistake.  It is a benign mistake at worst.

Just occurred to me ... shouldn't a covergroup output argument be passable as an output argument to a function in a coverpoint expression?  That would argue that sometimes the output argument is OK, so neither a warning nor error is justified in all cases.

At any rate, sounds to me like this merits discussion Monday.

Dave


Rich, Dave wrote:

This is a ballot issue. We are not required to accept the proposed solution as stated, just make sure that the original issues is addressed.

 

---

From: Scott, David
Sent: Friday, April 24, 2009 9:17 AM
To: Rich, Dave
Cc: sv-ec@server.eda.org
Subject: Re: [sv-ec] Ballot issue #106

 

I believe we were told to work on ballot issues only.  I'd like clarification from Mehdi and Neil on that.

Dave


Rich, Dave wrote:

I would really like to make a covergroup output/inout arguments illegal. There is no reason to allow these other than sloppiness.

 

I would also like to address ballot #110 in the same proposal by mentioning that a ref argument is treated as const ref, and that const ref only requires type compatibility with wires and variables.

 

Dave

 

 

---

From: owner-sv-ec@server.eda.org [mailto:owner-sv-ec@server.eda.org] On Behalf Of Scott, David
Sent: Wednesday, April 22, 2009 3:26 PM
To: sv-ec@server.eda.org
Subject: [sv-ec] Ballot issue #106

 

This is the one about covergroup arguments using "output" ...

 

http://www.eda-stds.org/mantis/view.php?id=2710

 

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

 

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. Received on Fri Apr 24 09:52:54 2009