===========================================================
IM12 Override Attributes
Bojsen, Per wrote:
> Hi,
>
> on p. 48 under the declarations of the OverrideAttributeIntegerValue()
> and OverrideAttributeStringValue() methods it is stated that it shall
> be an error to attempt to override any of the standard attributes
> as well as implementation defined attributes designated as read-only.
> However, it does not state what happens if an attribute that does not
> exist in the parameters database is attempted to be overridden.
>
> Should this be an error, should it be explicitly allowed, or should
> it be undefined, i.e., implementation defined? Given the use of
> `override' in the name of these methods it sounds like it should be
> an error to attempt to override a non-existent attribute. This would
> imply, though, that the user will not be able to add his own
> information in the form of new attributes to this database, but I
> don't think that is a big deal.
>
> What does the committee think?
>
> Thanks,
> Per
johnS:
Let's make this an error as you suggest.
===========================================================
IM13 Cyclestamp Zeroing
Bojsen, Per wrote:
> Hi John,
>
> > Right now we're starting it after ureset.
>
> I believe we are doing the same (have to check again
> though).
>
> > Is there a reason you can see to do otherwise ?
>
> No, not really, I just wanted to confirm my understanding.
> My understanding has been proven wrong before which is why
> I am extra cautious :-)
>
> > I do agree that we should be specific about this for
> > consistency among implementations.
>
> Agreed.
>
> So, as you understand the standard, the cycle stamp should
> be 0 while ureset is asserted and it should become 1 at the
> first 1/1 cclock rising edge after ureset is deasserted?
>
> Per
>
johnS:
Yes. This seems reasonsable.
-- johnS
______________________________/\/ \ \
John Stickley \ \ \
Principal Engineer \ \________________
Mentor Graphics - MED \_
17 E. Cedar Place \ john_stickley@mentor.com
Ramsey, NJ 07446 \ Phone: (201) 818-2585
________________________________________________________________
Received on Wed Mar 24 18:51:13 2004
This archive was generated by hypermail 2.1.8 : Wed Mar 24 2004 - 18:51:15 PST