RE: [sv-bc] default initial values

Implementers and users should be aware that this is a subtle change of
behavior from SV3.1a.

And there's no rule that says the default initial value must be a valid
value

> -----Original Message-----
> From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of
Steven
> Sharp
> Sent: Monday, August 22, 2005 2:31 PM
> To: sv-bc@eda.org; pgraham@cadence.com
> Subject: Re: [sv-bc] default initial values
> 
> 
> >From: Paul Graham <pgraham@cadence.com>
> 
> >Several places in p1800 refer to the "default initial value"
> >of an enum type.  I don't see where this default initial
> >value is defined.
> 
> This is defined in Table 6-1 "Default values" in section 6.4
"Variables",
> along with the default values for other types.  These section numbers
> are for the latest draft standard.
> 
> >Also, while we're at it, do the next() and prev() methods
> >have a defined value when N == 0?  I would guess that
> >X.next(0) == X.
> 
> That would presumably be the correct value, at least if X has a value
> that is a valid member of the enumeration.  If X has been given a
value
> that is not a valid member (e.g. by a cast), then I would expect that
> the rule for that would apply, and the result would be the default
> initial value for the enumeration.  So it is not guaranteed that
> X.next(0) == X unless X has a valid value for the enumeration.
> 
> Steven Sharp
> sharp@cadence.com