Martin Hořeňovský 849f2848bd Rework how warning suppression in macros is done ... 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`.		2019-10-27 21:07:21 +01:00
..
external	Fix vendored dep because upstream is non-responsive	2019-04-10 20:17:25 +02:00
internal	Rework how warning suppression in macros is done	2019-10-27 21:07:21 +01:00
reporters	Improve JUnit failure report	2019-10-27 18:02:14 +01: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	v2.10.2	2019-10-24 18:41:25 +02:00