Re: static or not?
On Jan 28, 2:12 pm, "Alf P. Steinbach" <al...@start.no> wrote:
Whether to use the names "min" and "max" is another matter, which I
think can only be resolved by thinking about what makes sense (or not)
in your problem domain, and whether you plan on using or suspect you
might in future be using std::max or std::min for Point3D.
FWIW I don't see min and max being useful for points and vectors.
The only possible use is if you treat a vector as a sequence and then
do min or max on each element:
#include <vector>
#include <algorithm>
#include <iostream>
int main()
{
typedef std::vector<double> vect;
vect v1, v2, r_min(3), r_max(3);
v1.push_back(1);
v1.push_back(2);
v1.push_back(3);
v2.push_back(0.5);
v2.push_back(3);
v2.push_back(-1);
typedef double const &(*pf)(double const &, double const &);
std::transform(v1.begin(), v1.end(),
v2.begin(),r_min.begin(),pf(std::min));
for ( std::size_t i = 0; i < r_min.size(); ++i){
std::cout << r_min[i] <<'\n';
}
std::cout << "......\n";
std::transform(v1.begin(), v1.end(),
v2.begin(),r_max.begin(),pf(std::max));
for ( std::size_t i = 0; i < r_max.size(); ++i){
std::cout << r_max[i] <<'\n';
}
}
You can of course also write a version that acts on a tuple.
Alternatively xmin(Pt,Pt), ymin(Pt,Pt),zmin(Pt,Pt) are useful
returning the minimum x and y of the 2 points. In this case its
similar to writing out each iteration of the sequence.
OTOH funnily enough min and max could make sense for a bounding
box :-)
regards
Andy Little