Pfiffikus 957b98a32a well-defined newEpsilon, target-epsilon, invisible default scale ...

What about to check for a well-defined newEpsilon (cf. http://realtimecollisiondetection.net/blog/?p=89)?
Apart from computational sciences view (cf. https://randomascii.wordpress.com/2012/02/25/comparing-floating-point-numbers-2012-edition/ or https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html) I would prefer two slight modifications referring to https://en.wikipedia.org/wiki/Approximation_error#Formal_Definition:
The given epsilon should refer to the target value, otherwise the result would be unexpected, e.g. 101.02 == Approx(100).epsilon(0.01) gets true. The default scale should be invisible, thus, e.g. 101.01 == Approx(100).epsilon(0.01) gets false. Finally (both modifications accepted) even 101.000001 == Approx(100).epsilon(0.01) should get false, e.g.

To prevent a misuse of epsilon its setting should be checked.

2017-10-26 09:19:57 +02:00

..

external

Addressed some static analysis warnings

2017-07-19 09:50:08 +02:00

internal

well-defined newEpsilon, target-epsilon, invisible default scale

2017-10-26 09:19:57 +02:00

reporters

adds flushes to the output stream of teamcity reporter, making the test output more responsive.

2017-10-17 16:42:05 +02:00

catch_session.hpp

Explicitly ignore return value of getchar

2017-08-22 22:06:37 +02:00

catch_with_main.hpp

Fixed catch_with_main.hpp (no longer references deleted catch_runner.hpp)

2015-12-28 15:06:04 +00:00

catch.hpp

Cosmetic fixes (whitespace and spelling)

2017-05-27 14:42:54 +02:00