From 78eba00f6bbadca6ef87975d4535e70e0eae087e Mon Sep 17 00:00:00 2001 From: Daniel James Date: Sat, 15 Mar 2008 12:59:21 +0000 Subject: [PATCH] Update type traits links for new location. [SVN r43621] --- doc/credits.qbk | 4 ++-- doc/examples.qbk | 11 ++++++----- doc/intrinsics.qbk | 2 +- doc/mpl.qbk | 8 ++++---- 4 files changed, 13 insertions(+), 12 deletions(-) diff --git a/doc/credits.qbk b/doc/credits.qbk index f8aab31..2c6c2cd 100644 --- a/doc/credits.qbk +++ b/doc/credits.qbk @@ -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 diff --git a/doc/examples.qbk b/doc/examples.qbk index 386571c..32729d9 100644 --- a/doc/examples.qbk +++ b/doc/examples.qbk @@ -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 diff --git a/doc/intrinsics.qbk b/doc/intrinsics.qbk index 12f20e1..d8a0734 100644 --- a/doc/intrinsics.qbk +++ b/doc/intrinsics.qbk @@ -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 diff --git a/doc/mpl.qbk b/doc/mpl.qbk index a9255c8..cc023d6 100644 --- a/doc/mpl.qbk +++ b/doc/mpl.qbk @@ -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` inherits from -[@../../libs/mpl/doc/refmanual/integral-c.html `boost::mpl::integral_c`] (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` inherits from +[@../../../../libs/mpl/doc/refmanual/integral-c.html `boost::mpl::integral_c`] (provided `T` is not `bool`) [endsect]