#4 Exclude-Options for "Number of parameters"

[dhiller]

Although the metric "Number of parameters" is very valuable, in some cases you can't do anything against it:

Case 1: Override inherited method/Implement interface method:

If you create MyTreeCellRenderer extending DefaultTreeCellRenderer and override method "getTreeCellRendererComponent" you can't do anything against the method "getTreeCellRendererComponent" violating the rule "Number of parameters" except including it into the exclude list. This prohibits all other metrics from measuring the class, which IMO is not desirable.

Same is true for implementing interfaces (TreeCellRenderer).

Therefore I suggest introducing the option "Exclude overwritten methods/methods implementing interface".

Case 2: "Introduce parameter object" creates constructor violating above rule:

To avoid the above problem for your own methods you can use "Introduce parameter object" to shorten the parameter list. But as constructors are measured also you don't get out here.

For public constructors this may be a reasonable measure but for private ones, which I prefer to use for parameter objects, IMHO this doesn't make sense.

Therefore I suggest introducing the option "Exclude (invisible) constructors"