* topic/11756-non-standards-fpexception-intel:
Changelog
FPE: disabling support of the glibC extensions for uLibC std library
Preventing the compilation of floating points with GCC when glibc is not in use
- Gathering the support of FPE in one place/several macros and using those in both
execution_monitor.hpp and execution_monitor.ipp in a more coherent way
- Updating the support of the floating point exceptions: fenableexcept/fdisableexcept are
GLIBC extensions and the definition of FENV does not imply the existance of those functions
* topic/12540-printing-types-customisation-point:
Change log update
Documenting the customization point
Fixing the tests and checking everything works ok
Test for customization points
Customization points for printing user defined types through `boost_test_print_type`
* topic/junit-more-efficient:
Change log update
JUnit: updating documentation
JUnit: changing the default to log-messages
JUnit: refactoring for handling the different phases in an easier way
JUnit: being able to indicate the log level for speeding up
Using lists for the output streams
Lowering JUnit output memory footprint
- junit internal log level to be able to intercept all the intermediate messages (tu enter/exit)
- skipping events that do not match the desired log level
- some refactoring (root of the subtree, getter of the current log)
- logs that do not belong to any TU go to a global log
TODO: global log should be outputted to the stream as well
* develop:
Change log update
Fix typo
Change log update
nullptr support in the test tools + test
Fix tests issues
Change log update
Change some capital variable names to lowercase
Change log
Fix using __COUNTER__ when available
Test case firing issue 12712
Correction of the previous syntax fix
Fix Markdown link format
Preparing changelog for 1.64
Fix documentation header
Fixing the compilation issues in mingw
* topic/12712-several-test-suite-decl-in-same-comp-unit:
Change log
Fix using __COUNTER__ when available
Test case firing issue 12712
Correction of the previous syntax fix
Fix Markdown link format
Preparing changelog for 1.64
The scenario is that we have two identical files defining test cases and suites. The suites are the same in both files, tests are not. The line numbers are the same as well.
Finally those files are #include'd in a unique .cpp file. The registrar for the test suites are having the same name and raising a compilation error
I messed up the order of the different brackets and did not preview the
markdown before pushing. I'm very sorry.
This fix is tested in Atom's Markdown preview now and really fixes the
issue.
* develop:
Bugfix token iterator ctor
Merging tokens that start with \ or / with previous tokens
BOOST_TEST string tests: protecting tests with API defines
Change log
Boost.Test learned the '--version' command line argument
Minor documentation changes
Change log and breaking change annoucement
Apparently the name appears as "test<struct_ns__X>" in Visual (instead of "test<ns__X>" on gcc like)
Cleaning names with colons and fixing the proper demangling on all platforms
Change log and doc update
String comparison can now be used with BOOST_TEST additional compare options
Making std::string compatible with string comparison backend
Change log
Now underlining the fatal errors instead of blinking
