From: Steven Sharp (firstname.lastname@example.org)
Date: Mon Nov 03 2003 - 16:10:00 PST
The following reply was made to PR errata/211; it has been noted by GNATS.
From: Steven Sharp <email@example.com>
To: firstname.lastname@example.org, Shalom.Bresticker@motorola.com
Subject: Re: errata/211: Re: errata/211: PROPOSAL - 3.11.2: localparam behavior not clear
Date: Mon, 3 Nov 2003 19:12:32 -0500 (EST)
> "However, overriding a parameter, whether by a defparam statement or in a
> instantiation statement, effectively forces the parameter to a new value,
> regardless of any expression associated with the parameter declaration in the
> module definition."
Note that it is not just a new value. The new value could be an expression
containing other parameters. Not only is the overridden parameter no longer
dependent on any parameters in its old definition, but it is now dependent on
any parameters in its new definition, if they change values. The old
definition has been completely replaced with the new one.
I'm not sure that the word "force" is a good choice here either, given the
existence of force statements, which are unrelated to this.
This archive was generated by hypermail 2.1.4
: Mon Nov 03 2003 - 16:10:02 PST
sponsored by Boyd Technology, Inc.