Re: [Boost-users] [Boost.Test] improving BOOST_CHECK_CLOSE forarguments == 0

From: Pierre-Jules Tremblay (iamtrep_at_[hidden])
Date: 2007-03-14 08:34:04

I understand.

So I'm not sure I can build the tool I need with the existing tools.
What I need to do is essentially compare two vector<float> objects of
same size, element-by-element.  I would be ok with using an absolute
difference test in all cases (so that zero and non-zero comparison
tests remain valid), however if I'm not mistaken my only choice is
BOOST_CHECK_SMALL(a-b,tol) where a and b are corresponding elements of
the two vectors.  The downside of this approach is that if the test
fails, only one value gets printed out, i.e. the result of the
subtraction.

Can you suggest a way to combine existing tools to get what I'm looking for?

Cheers,

pj

On 3/13/07, Gennadiy Rozental <gennadiy.rozental_at_[hidden]> wrote:
> > I wonder: did I miss something, is there a better way?  If not,
> > perhaps this logic could be integrated in the _CLOSE tools.
>
> BOOST_CHECK_CLOSE and BOOST_CHECK_SMALL are two very different tools. Former
> is based on comparisons of relative values using percentage tolerance. Later
> is based on comparison of absolute value against the actual tolerance.
> Combining them into one is simply wrong. You couldn't use the same tolerance
> value for both of them. Also there is a reason why BOOST_CHECK_CLOSE behaves
> the way it behaves with zero value: in general no value is close to zero.
>   Now if you need to follow above logic for your purposes you are free to do
> this. But this could not be a part of Boost.Test.
>
> Gennadiy
>
>
>
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>