Re: paramsets and module terminals

Marq Kole wrote:
> 
> All,
> 
> With respect to the very open relation between a paramset and the
> module it is associated with: can I use parameter overloading for
> different modules that also have different numbers of terminals:

Marq -
This seems a rather roundabout way of doing it.  When we created
the $port_connected function, the idea was that one could test
this to conditionally leave out a section of code, eg:
  if ($port_connected(bulk)) begin
    Vbs = 0;
    Vth_pre_dibl = ...
  end else begin
    ...
  end

I guess in your case, if there is no bulk node, you also want to
change the topology (eg, no internal bulk node / bulk resistance).

Would we consider additional paramset selection rules such as:
a) the underlying module shall have a port declared for each
  port connected in the instance line
b) the underlying module with the fewest ports not connected
  in the instance line shall be preferred

-Geoffrey