RE: [sv-bc] time unit specification

I thought the reasoning behind this wording was a committee compromise,
or a lack of decisiveness, depending on your point of view. 

The default timeunit could be "no timeunit specified".

This provides an excuse for some implementations producing an error and
some not, and still be conforming to the LRM when there is a mix of
design units with specified and unspecified timeunits.

Dave


> -----Original Message-----
> From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org]
On
> Behalf Of Steven Sharp
> Sent: Wednesday, November 19, 2008 12:23 PM
> To: sv-bc@server.eda.org; Mark.Hartoog@synopsys.com
> Subject: Re: [sv-bc] time unit specification
> 
> 
> >From: "Mark Hartoog" <Mark.Hartoog@synopsys.com>
> 
> >If all design elements with no other time unit/precision
specification
> >use the default time unit, how can you have a design element with no
> >time unit/precision specified?
> 
> A design element using the default does not have one specified.
> 
> 
> >Does this mean that it is an error for some design elements to use
the
> >default and other design elements to have different time
unit/precision
> >specified?
> 
> Yes (or actually, for other design elements to have a time
unit/precision
> specified, whether it is different from the default or not).
> 
> I assume that the intent was to avoid problems caused by forgetting to
> specify a time unit/precision on a subset of the design.
> 
> There appears to be a hole in this, since I don't think the
compilation
> unit is considered a design element, but it can contain tasks that
> specify delays or otherwise use time scaling.
> 
> 
> Steven Sharp
> sharp@cadence.com
> 
> 
> --
> 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.