* topic/GH-264-GCC-override-warnings-suggestions:
Change log
Use BOOST_OVERRIDE to fix GCC -Wsuggest-override and Clang-tidy modernize-use-override warnings. Also fix misspellings in comments.
* must become declarations and inline definitions outside the class for Embarcadero C++ clang-based compilers. This bug has been reported to Embarcadero.
* using definition from Boost.Config for the Embarcadero non-clang-based compilers.
* Embarcadero C++ clang-based compilers act like clang ( __GNUC__ ) in regard to SEH based signal handling.
* The __cdecl calling convention is valid for Embarcadero C++ clang-based compilers
__MACH__ matches any Mach-based OS, which means both macOS and GNU/Hurd;
since the API used is really specific to macOS, then also check for
__APPLE__.
- now report in more details the reasons of a mismatch for per element
- now report in more details the reasons of a stopping condition for per lexicographic
- punctuation
- now indicates better the operations names as well as their inverse
- tolerance manipulator commutes with stream message
This allows the inclusion of various translation units with mixed
header/non-header variant, without the need to specify any of the
auto-linking +/- disabling macros.
Updated unit tests to capture the issue.
Previously all loggers were looped in the context helper, which causes
duplicate context messages and discards the log level of each of the
loggers.
Associated unit tests: they have to save their save_pattern state into
another global mechanism as the junit tests are changing the runtime configuration.
Those new tests asserts inside JUnit before the fix.
- "configure" the logger singleton when setup changes
- returning previous log levels
- reducing the number of loggers on startup: now only the active loggers (that are logging something) are used during the test execution. This reduces the
loops and the number of tests
- Used only during the initialization/deinit of the framework to catch any issues in the global fixtures
or other observers initialization.
- Removed during tests execution to reduce overhead
- Not a singleton anymore
This fixes numerous compilation warnings:
note: #pragma message:
The practice of declaring the Bind placeholders (_1, _2, ...)
in the global namespace is deprecated.
Please use <boost/bind/bind.hpp> + using namespace boost::placeholders,
or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.
BOOST_UNREACHABLE_RETURN creates several issues on
various MSVC compilers (manifest issue), curiously only
for the program monitor type of binaries. Making
a workaround for the time being.
- framework now does not shortcut the message when a skipped
tests is encountered
- framework messages are now at line "0" to avoid any further noise
in the messages when files in the framework are changed
- counting tests in case of disabled tests goes in the hierarchy
- counter class now has the ability to discard the enabled status
to count properly the children tests
- adding tests
- ensuring C++03 compatibility
