Subject: Re: VerilogAMS Committee Meeting Minutes - 15 December 2003
From: Geoffrey.Coram (Geoffrey.Coram@analog.com)
Date: Wed Jan 07 2004 - 07:59:45 PST
Martin O'Leary wrote:
[regarding "visible" variables/parameters]
> This definition seems very specific to device models and not applicable
> to Verilog(-AMS) modules in general - therefore I think hiding variables
> should be handled by putting an attribute on the parameter declaration.
> Understand that attributes were intended for application specific
> purposes such as this.
> Maybe this might be more typing for folks but if there are up to a
> 1000 parameters of bsim model, I expect cut-and-paste would be used by
> modelers anyway so this attribute mightn't be such a chore to deal with.
Parameters are (for Spice simulators) always visible, so I don't know
that we'd ever want to "hide" them. I suppose someone might want to,
so we could standardize an attribute to hide them, which wouldn't be
used much. The parameter declaration line is already getting quite
lengthy.
For output/operating point variables (let's not use the word parameter
here), the declaration line won't have much on it, so I'm somewhat
ambivalent about adding attributes. Also, there won't be so many
of these compared with parameters (gm, gds, gbms, plus a dozen or
so transcapacitances).
If we standardize an attribute to hide the parameters, then I would
say we should use that same attribute to hide op pt vars. So, for
variables declared at top level, a Spice simulator should either
(a) print them all for operating point info, or
(b) print only those that have a description
unless the hidden attribute is specified.
-Geoffrey
This archive was generated by hypermail 2b28 : Wed Jan 07 2004 - 08:00:25 PST