S
Steve Chow
Originally I had a bunch of related functions that all took a vector
of Point2D as their argument.
Point2D findGreatestDistance(std::vector<Point2D>& points);
However, this didn't strike me as a very C++/OO way to do things, so I
found a solution I was happy with in:
class Path : public std::vector<Point2D>
{
public:
Path();
~Path();
Point2D findGreatestDistance();
/* related functions */
};
And it works, at least as far as I can tell. Yet it's been received by
people more knowledgeable than me as disgusting and wrong, without
explaining why. Is there a better way I should be doing this?
Someone suggested moving findGreatestDistance into Point2D (struct
with x,y and overload ==) but I don't see how that's possible because
it'd only be able to look at itself.
of Point2D as their argument.
Point2D findGreatestDistance(std::vector<Point2D>& points);
However, this didn't strike me as a very C++/OO way to do things, so I
found a solution I was happy with in:
class Path : public std::vector<Point2D>
{
public:
Path();
~Path();
Point2D findGreatestDistance();
/* related functions */
};
And it works, at least as far as I can tell. Yet it's been received by
people more knowledgeable than me as disgusting and wrong, without
explaining why. Is there a better way I should be doing this?
Someone suggested moving findGreatestDistance into Point2D (struct
with x,y and overload ==) but I don't see how that's possible because
it'd only be able to look at itself.