feedc0de/boost_type_traits
1
0
Fork 0
forked from boostorg/type_traits
Code Pull Requests Activity

Update type traits links for new location.

Browse Source 
[SVN r43621]
This commit is contained in:
Daniel James
2008-03-15 12:59:21 +00:00
parent 1f23f44e86
commit 78eba00f6b
4 changed files with 13 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/credits.qbk
View File

@ -8,8 +8,8 @@
[section:credits Credits]
This documentation was pulled together by John Maddock, using
[@../../tools/quickbook/doc/html/index.html Boost.Quickbook]
and [@boostbook.html Boost.DocBook].
[@../../../../tools/quickbook/doc/html/index.html Boost.Quickbook]
and [@../../../../doc/html/boostbook.html Boost.DocBook].
The original version of this library was created by Steve Cleary,
Beman Dawes, Howard Hinnant, and John Maddock. John Maddock is the

11
doc/examples.qbk
View File

@ -11,7 +11,7 @@
Demonstrates a version of `std::copy` that uses `__has_trivial_assign` to
determine whether to use `memcpy` to optimise the copy operation
(see [@../../libs/type_traits/examples/copy_example.cpp copy_example.cpp]):
(see [@../../examples/copy_example.cpp copy_example.cpp]):
//
// opt::copy
@ -62,7 +62,7 @@ determine whether to use `memcpy` to optimise the copy operation
Demonstrates a version of `std::fill` that uses `__has_trivial_assign` to
determine whether to use `memset` to optimise the fill operation
(see [@../../libs/type_traits/examples/fill_example.cpp fill_example.cpp]):
(see [@../../examples/fill_example.cpp fill_example.cpp]):
//
// fill
@ -107,7 +107,7 @@ determine whether to use `memset` to optimise the fill operation
Demonstrates a simple algorithm that uses `__has_trivial_destruct` to
determine whether to destructors need to be called
(see [@../../libs/type_traits/examples/trivial_destructor_example.cpp trivial_destructor_example.cpp]):
(see [@../../examples/trivial_destructor_example.cpp trivial_destructor_example.cpp]):
//
// algorithm destroy_array:
@ -153,7 +153,7 @@ same as `std::iter_swap` does), however if they are proxying iterators
then takes special care over the swap to ensure that the algorithm
works correctly for both proxying iterators, and even iterators of
different types
(see [@../../libs/type_traits/examples/iter_swap_example.cpp iter_swap_example.cpp]):
(see [@../../examples/iter_swap_example.cpp iter_swap_example.cpp]):
//
// iter_swap:
@ -203,7 +203,8 @@ different types
[section:to_double Convert Numeric Types and Enums to double]
Demonstrates a conversion of
[@../../libs/numeric/conversion/doc/definitions.html#numtypes Numeric Types]
[@../../../../libs/numeric/conversion/doc/html/boost_numericconversion/definitions.html#boost_numericconversion.definitions.numeric_types
Numeric Types]
and enum types to double:
template<class T>

2
doc/intrinsics.qbk
View File

@ -41,7 +41,7 @@ The following traits classes are dependent on one or more of the above:
* __is_stateless
The hooks for compiler-intrinsic support are defined in
[@../../boost/type_traits/intrinsics.hpp boost/type_traits/intrinsics.hpp], adding support for new compilers is simply
[@../../../../boost/type_traits/intrinsics.hpp boost/type_traits/intrinsics.hpp], adding support for new compilers is simply
a matter of defining one of more of the following macros:
[table Macros for Compiler Intrinsics

8
doc/mpl.qbk
View File

@ -8,13 +8,13 @@
[section:mpl MPL Interoperability]
All the value based traits in this library conform to MPL's requirements
for an [@../../libs/mpl/doc/refmanual/integral-constant.html Integral Constant type]: that includes a number of rather intrusive
for an [@../../../../libs/mpl/doc/refmanual/integral-constant.html Integral Constant type]: that includes a number of rather intrusive
workarounds for broken compilers.
Purely as an implementation detail, this
means that `__true_type` inherits from [@../../libs/mpl/doc/refmanual/bool.html `boost::mpl::true_`], `__false_type` inherits
from [@../../libs/mpl/doc/refmanual/bool.html `boost::mpl::false_`], and `__integral_constant<T, v>` inherits from
[@../../libs/mpl/doc/refmanual/integral-c.html `boost::mpl::integral_c<T,v>`] (provided `T` is not `bool`)
means that `__true_type` inherits from [@../../../../libs/mpl/doc/refmanual/bool.html `boost::mpl::true_`], `__false_type` inherits
from [@../../../../libs/mpl/doc/refmanual/bool.html `boost::mpl::false_`], and `__integral_constant<T, v>` inherits from
[@../../../../libs/mpl/doc/refmanual/integral-c.html `boost::mpl::integral_c<T,v>`] (provided `T` is not `bool`)
[endsect]