catch3/include/internal/catch_compiler_capabilities.h, branch v2.11.1 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Avoid detecting Clang as having MSVC's traditional preprocessor 2019-12-28T17:57:24+00:00 Martin Hořeňovský 2019-12-28T17:57:24+00:00 55794e9b27740a51f1698f482d79ead4e0a38ffe Fixes #1806 
Fixes #1806
Rework how warning suppression in macros is done 2019-10-27T20:07:21+00:00 Martin Hořeňovský 2019-10-27T20:07:21+00:00 849f2848bdf625a7b6248e4e62ba0e39ee609634 Previously, each warning suppression was self-contained, with its own pair of `SUPPRESS_X_WARNING` and `UNSUPPRESS_X_WARNING` macros. This had the obvious advantage of being self-containing, but it also meant that if we needed to suppress more than one warning in a single place, then we would manipulate the compiler's warning state multiple times, even though logically we would only need one layer. The new way of suppressing warnings in macros is to push compiler's warning state with `CATCH_INTERNAL_START_WARNINGS_SUPPRESSION` macro, then disable whatever macros we need with the `CATCH_INTERNAL_SUPPRESS_X_WARNINGS` macro, and then return to the previous state using `CATCH_INTERNAL_STOP_WARNINGS_SUPPRESSION`. 
Previously, each warning suppression was self-contained, with its
own pair of `SUPPRESS_X_WARNING` and `UNSUPPRESS_X_WARNING` macros.
This had the obvious advantage of being self-containing, but it
also meant that if we needed to suppress more than one warning
in a single place, then we would manipulate the compiler's warning
state multiple times, even though logically we would only need one
layer.

The new way of suppressing warnings in macros is to push compiler's
warning state with `CATCH_INTERNAL_START_WARNINGS_SUPPRESSION` macro,
then disable whatever macros we need with the
`CATCH_INTERNAL_SUPPRESS_X_WARNINGS` macro, and then return to the
previous state using `CATCH_INTERNAL_STOP_WARNINGS_SUPPRESSION`.
TemplateTests: suppress -Wunused-template warning in template test cases 2019-10-18T16:38:39+00:00 Jozef Grajciar 2019-10-18T10:30:17+00:00 ae14a47360028c941f37a0f656c4d8ee78ab4837 this warning was introduced by rework to support NTTPs since we have implementation macro for NTTPs and normal template test cases warning is going to be suppressed Fixes #1762 
this warning was introduced by rework to support NTTPs
since we have implementation macro for NTTPs and normal template test cases
warning is going to be suppressed

Fixes #1762
Unify handling of __has_include checks 2019-09-06T11:38:58+00:00 Martin Hořeňovský 2019-09-06T11:38:58+00:00 6e8d769775c6840156355a663b9073be78ac4bcb 






Workaround missing std::nextafter in uClibc
2019-09-06T11:08:44+00:00

Martin Hořeňovský

2019-09-06T11:08:44+00:00

addf799040e8f0cefbe42ca1a22787802a969077

Luckily, the rest of C++11 features seem to be supported...

Closes #1739





Luckily, the rest of C++11 features seem to be supported...

Closes #1739







Add disabling the use of Android's logging at compile time
2019-09-06T10:44:06+00:00

Martin Hořeňovský

2019-09-06T10:41:42+00:00

155274f0dff32fd109a05a94cf1f002bf2dd97a0

This is done via the new compile time toggle,
`CATCH_CONFIG_ANDROID_LOGWRITE`.

Closes #1743





This is done via the new compile time toggle,
`CATCH_CONFIG_ANDROID_LOGWRITE`.

Closes #1743







Add autoconfiguration for RTX
2019-07-30T09:28:28+00:00

Martin Hořeňovský

2019-07-30T09:26:25+00:00

ba9193370b44dbf68632adaff7e33522f24279e6

Closes #1693





Closes #1693







Add `std::byte` stringification support (#1686)
2019-07-13T12:47:56+00:00

Stuart Dootson

2019-07-13T12:47:56+00:00

87739ad3feed09ba0284731cacaed14def894aff

* Add `std::byte` support

1. Add byte detection in Catch config
2. Add a `std::byte`specialisation for Catch2::Detail::StringMaker





* Add `std::byte` support

1. Add byte detection in Catch config
2. Add a `std::byte`specialisation for Catch2::Detail::StringMaker







Standardize and document the parallel processing toggle
2019-06-15T10:50:36+00:00

Martin Hořeňovský

2019-06-15T10:50:36+00:00

c365ac392b3b4edf1cb232407111902146249404












Integrate Nonius benchmark into Catch2
2019-06-06T17:33:37+00:00

Joachim Meyer

2019-04-23T21:41:13+00:00

ce2560ca956c1743f8bc871e0bf95f65a3db887c

Changes done to Nonius:
* Moved things into "Catch::Benchmark" namespace
* Benchmarks were integrated with `TEST_CASE`/`SECTION`/`GENERATE` macros
* Removed Nonius's parameters for benchmarks, Generators should be used instead
* Added relevant methods to the reporter interface (default-implemented, to avoid
breaking existing 3rd party reporters)
* Async processing is guarded with `_REENTRANT` macro for GCC/Clang, used by default
on MSVC
* Added a macro `CATCH_CONFIG_DISABLE_BENCHMARKING` that removes all traces of
benchmarking from Catch





Changes done to Nonius:
* Moved things into "Catch::Benchmark" namespace
* Benchmarks were integrated with `TEST_CASE`/`SECTION`/`GENERATE` macros
* Removed Nonius's parameters for benchmarks, Generators should be used instead
* Added relevant methods to the reporter interface (default-implemented, to avoid
breaking existing 3rd party reporters)
* Async processing is guarded with `_REENTRANT` macro for GCC/Clang, used by default
on MSVC
* Added a macro `CATCH_CONFIG_DISABLE_BENCHMARKING` that removes all traces of
benchmarking from Catch