* topic/12531-run-test-with-colons:
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
- replacing colons with underscores in the names cleaning
- names generated by template elements were not properly demangled in all platforms: using now the boost.core demangling functions (same as execution monitor)
- adding smoke tests and changing existing ones accordingly
* topic/11756-floatingpoint-exception-macros:
Some cleanup on the fpe symbols
Updated change log
trac 11756: fix usage of floating point exception macros
# Conflicts:
# doc/closing_chapters/change_log.qbk
* topic/12507-broken-report-sink:
Changelog update
More smoke tests
Bug fix default argument
Adding smoke tests for the loggers issue
Bugfix: cast to wrong type
A fully standards conforming fenv.h does not have to define any FE_* macros, and if it does define them,
then it defines macros only for the FP exceptions it actually supports.
Correct usage requires a triple check:
1) Check BOOST_NO_FENV_H to see if the header is supported.
2) Include the header and then check FE_ALL_EXCEPT to see
if any FP exceptions are supported.
3) Before using the individual FE_* macros, you need to
check for their existence too as not all may be
supported.
The reason is that some (notably FPU-less) architectures,
including mips*-nf, don't define/implement some of the
floating point constants, even though fenv.h is
available.
Other projects have similar issues, e.g. pixman, and apply similar work-arounds:
https://lists.freedesktop.org/archives/pixman/2014-February/003172.html
Architectures are notably also allowed to define FE_ALL_EXCEPT to 0!
Keeping this in mind, and knowing that the compiler will eliminate
code that can't be executed, we can change BOOST_FPE_ALL to be 0 for
the case of compiling using Clang and/or fenv.h being unavailable
as well, which allows simplification of the #ifdef's in
execution_monitor.ipp a bit.
* topic/loggers-additional-cleanups:
Loggers: now checking for --logger params correctness
Logger: cleaned up and improved the API
being able to add a custom formatter instead of having it in an 'invalid' state
Additional cleanups
Additional cleanup of unused fields
Moving the logger setup into a dedicated function
- now experiencing the same behaviour as pre 1.62
- set_stream and set_threshold_level for the loggers are now mutating all loggers, not only the active ones
- renamed function
- when adding a custom logger, it is added to the set of loggers with CUSTOM
- updated the documentation
* topic/12093-gcc-compilation-issues:
Change log update
gcc 4.6: fixing failing tests
gcc 4.6: fixing issues related to the new cla and C++11 not fully supported
gcc 4.6: fixing issues related to operator<< not properly seen by the compiler
- major reorganization of the output section
- making more clear what a log and what a report is
- checkpoints doc update
- links to API, improved doxygen documentation and reference
- renamed files and sections
- JUNIT additional doc
- removed useless parts
