Functions with a long parameter list are difficult to use because maintainers must figure out the role of each parameter and keep track of their
position.
void setCoordinates(int x1, int y1, int z1, int x2, int y2, int z2) { // Noncompliant
// ...
}
The solution can be to:
- Split the function into smaller ones
// Each function does a part of what the original setCoordinates function was doing, so confusion risks are lower
void setOrigin(int x, int y, int z) {
// ...
}
void setSize(int width, int height, int depth) {
// ...
}
- Find a better data structure for the parameters that group data in a way that makes sense for the specific application domain
class Point { // In geometry, Point is a logical structure to group data
int x;
int y;
Point(this.x, this.y);
}
void setCoordinates(Point p1, Point p2) {
// ...
}
This rule raises an issue when a function has more parameters than the provided threshold.
