feedc0de/boost_functional
1
0 Fork 0
forked from boostorg/functional
Code Pull Requests Activity

Update paths for headers moved to different modules

Browse Source 
Makes it easier to see dependencies.
This commit is contained in:
Daniel James committed 2017-12-19 17:48:18 +00:00
1 parent 3697941e27
commit 5f9b5bcfad
51 files changed
+111 -111
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

overloaded_function/doc/overloaded_function.qbk
+2 -2
View File
@@ -42,9 +42,9 @@ Consider the following functions which have distinct signatures:
Instead of calling them using their separate names (here `BOOST_TEST` is equivalent to `assert`):
[footnote
In most of the examples presented in this documentation, the Boost.Detail/LightweightTest (=boost/detail/lightweight_test.hpp=) macro `BOOST_TEST` is used to check correctness conditions (conceptually similar to `assert`).
In most of the examples presented in this documentation, the Boost.Core/LightweightTest (=boost/core/lightweight_test.hpp=) macro `BOOST_TEST` is used to check correctness conditions (conceptually similar to `assert`).
A failure of the checked condition does not abort the execution of the program, it will instead make `boost::report_errors` return a non-zero program exit code.
Using Boost.Detail/LightweightTest allows to add the examples to the library regression tests so to make sure that they always compile and run correctly.
Using Boost.Core/LightweightTest allows to add the examples to the library regression tests so to make sure that they always compile and run correctly.
]
[identity_calls]