Gennadiy Rozental skrev:
Thorsten Ottosen <thorsten.ottosen <at> dezide.com> writes:
I tend to get a compilation error the first time, because I wrote
BOOST_CHECK_CLOSE( a->conditionals().sum(), 2, 0.001f );
[snip]
The changes are small and the only downside it new dependency on numeric conversion headers. But I find it worth the price. One more thing we may do on top of this is to validate against both FTP1 and FTP2 type to be integral: we don't really want to check closeness of integer values.
What do you think?
I think it is very good. As for the check for integers, then I don't think it is worth doing. In particular, when I'm using Boost.Test with my students, compile-time errors are sort of bad in this case (even though they are good in general). -Thorsten