RE: [sv-bc] question about specify blocks

Known specification hole - that's kind of an oxymoron, isn't it. :-) 

 

We have the same issue with clocking blocks, file I/O. They all need to
be updated to deal with new data types, including data types on wires.

 

I would expect that we would have to restrict selects in a similar
fashion as LHS targets of continuous assignments are restricted.

 

Dave

 

 

________________________________

From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of
Francoise Martinolle
Sent: Wednesday, August 10, 2005 10:07 AM
To: sv-bc@eda.org
Subject: [sv-bc] question about specify blocks

 

The specify blocks have not been enhanced to take advantage of the new
datatypes. For example the

syntax only allows scalar, vector or bit select, part select range
expression in the path specifications.

Is this a known specification hole? Are we expecting to fix this in the
future and specify timing on various 

packed struct members and perhaps even unpacked datatypes?

 

I realize that we could specify timing on packed structs and packed
arrays by determining the part select

corresponding to the member of the struct or sub-element of the packed
arrays, but it would be a lot more

readable to be able to use member selects and multiple indices.

 

Francoise

       '