Unnecessary VTK API change

Development
18

I suppose there is another way to look at this.
If for example vtkThreshold contained a vtkRange object

class vtkRange
{
private:
  int lower;
  int upper;
}

then it would seem reasonable to have
vtkThreshold::SetRange(const vtkRange& value)
VtkThreshold::SetRange(int lower, int upper)