catch3/include/internal, branch v2.0.1 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Removed zombie files 2017-11-03T16:56:11+00:00 Phil Nash 2017-11-03T16:56:11+00:00 4acf112c19a554b35ee1fd77e7c122284e8dd8ec These files were removed from the Catch2 branch, and crept back in when Catch2 merged with master 
These files were removed from the Catch2 branch, and crept back in when Catch2 merged with master
Merge branch 'catch2' 2017-11-03T12:05:38+00:00 Phil Nash 2017-11-03T12:05:38+00:00 46c7c9d3a0cb975dabf5970cc65fd8fc72d4c5b5 






v2.0.1 release
2017-11-03T12:01:52+00:00

Phil Nash

2017-11-03T12:01:52+00:00

b119ebdde15ae4b092f22766fcd652307b42cdf2












Print any start-up exceptions in Session's constructor, so custom main's don't need to worry about them
2017-11-02T17:58:07+00:00

Phil Nash

2017-11-02T17:57:52+00:00

fe05062f9e3b00251b86fb76b3dab9732e1e7787












Approx cleanup: More tests, INFINITY handling, etc
2017-11-01T06:30:11+00:00

Martin Hořeňovský

2017-11-01T06:30:11+00:00

22ac9d2184b3868cccfd635eb631d0eee1529121












Approx rework: default scale == 0, epsilon applies to Approx::value
2017-10-31T14:43:42+00:00

Pfiffikus

2017-10-26T07:19:57+00:00

00af677577973758b3b35e1c94ab4142c45c3f67

Also adds check to Approx::epsilon that the new epsilon has a valid
(ie one between 0 and 1)

Based on
http://realtimecollisiondetection.net/blog/?p=89
https://randomascii.wordpress.com/2012/02/25/comparing-floating-point-numbers-2012-edition/
https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html
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)
is true.
The default scale should be invisible, thus,
e.g. 101.01 == Approx(100).epsilon(0.01) gets false.
Finally even 101.000001 == Approx(100).epsilon(0.01) is false





Also adds check to Approx::epsilon that the new epsilon has a valid
(ie one between 0 and 1)

Based on
http://realtimecollisiondetection.net/blog/?p=89
https://randomascii.wordpress.com/2012/02/25/comparing-floating-point-numbers-2012-edition/
https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html
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)
is true.
The default scale should be invisible, thus,
e.g. 101.01 == Approx(100).epsilon(0.01) gets false.
Finally even 101.000001 == Approx(100).epsilon(0.01) is false







dev build 6
2017-10-31T14:17:21+00:00

Martin Hořeňovský

2017-10-31T14:17:21+00:00

ae21020640e6137acac027177d86c08083225dc1












Make Approx::margin inclusive
2017-10-31T13:49:00+00:00

Martin Hořeňovský

2017-10-30T14:25:48+00:00

11f716f28d6621d1e54cf13374f8b5dd1a7489f5

Fixes #952, related to #980





Fixes #952, related to #980







`RandomNumberGenerator::result_type` should be unsigned (#1050)
2017-10-31T13:26:36+00:00

Sebastian Grottel

2017-10-15T16:30:40+00:00

96c5de678d538e4e9b95c7f06afa03e3d0a0b15e

`result_type` must be unsigned:
http://en.cppreference.com/w/cpp/concept/UniformRandomBitGenerator

Using a signed type causes an infinite loop working with MS Visual Studio 2017, targetting: v140, WindowsTargetPlatformVersion 10.0.15063.0, Debug, x64





`result_type` must be unsigned:
http://en.cppreference.com/w/cpp/concept/UniformRandomBitGenerator

Using a signed type causes an infinite loop working with MS Visual Studio 2017, targetting: v140, WindowsTargetPlatformVersion 10.0.15063.0, Debug, x64







Update handling of __JETBRAINS_IDE__ macro
2017-10-31T13:15:54+00:00

Dmitry Kozhevnikov

2017-09-04T16:43:32+00:00

44244713f10e772e9d8fcf011941f326099c1c9a

1. Use it to conditionally define CATCH_INTERNAL_CONFIG_COUNTER, not
   CATCH_CONFIG_COUNTER, as __JETBRAINS_IDE__ is similar to
   compiler-provided macros, not to user-provided ones.

2. Since __COUNTER__ will work starting with CLion 2017.3, use it
   when possible (and hopefully remove this check altogether
   at some point).





1. Use it to conditionally define CATCH_INTERNAL_CONFIG_COUNTER, not
   CATCH_CONFIG_COUNTER, as __JETBRAINS_IDE__ is similar to
   compiler-provided macros, not to user-provided ones.

2. Since __COUNTER__ will work starting with CLion 2017.3, use it
   when possible (and hopefully remove this check altogether
   at some point).