paramset error conditions

From: Geoffrey.Coram <Geoffrey.Coram@analog.com>
Date: Thu Jun 17 2004 - 10:41:45 PDT

I believe all of the following should generate errors:

1) a mismatch between the ports of the instance and
those of the module underlying the paramset that was
selected for that instance
  a) the instance connects to a port by name, but the
     module does not have a port by that name
  b) the instance connects ports by ordered list, but
     the list has more ports than the module has

(note that an instance need not connect to all the
ports of the module, whether by name or by order)

2) a paramset assigns a value to a module parameter
and this value is outside the range specified for
that module parameter

(One could simply say that that paramset is not a
match; however, I believe it is an error on the
part of the paramset writer, who should have put
the constraint in the paramset. If we say it is
not a match, and then no match is found, it could
be very hard to debug.)

3) a paramset assigns a value to a non-existant
module parameter (probably a typographical error,
but maybe the underlying module was updated and
a parameter was removed).

-Geoffrey
Received on Thu Jun 17 10:41:49 2004

This archive was generated by hypermail 2.1.8 : Thu Jun 17 2004 - 10:41:50 PDT