update boost
This commit is contained in:
@@ -24,7 +24,7 @@
|
||||
#include <boost/type_traits/is_const.hpp>
|
||||
#include <boost/mpl/if.hpp>
|
||||
#include <boost/mpl/not.hpp>
|
||||
#include <boost/utility/enable_if.hpp>
|
||||
#include <boost/core/enable_if.hpp>
|
||||
|
||||
|
||||
/******************************************************************************
|
||||
|
||||
@@ -20,7 +20,7 @@
|
||||
|
||||
#include <boost/bimap/relation/support/is_tag_of_member_at.hpp>
|
||||
#include <boost/bimap/detail/debug/static_error.hpp>
|
||||
#include <boost/utility/enable_if.hpp>
|
||||
#include <boost/core/enable_if.hpp>
|
||||
#include <boost/preprocessor/cat.hpp>
|
||||
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@
|
||||
#include <boost/type_traits/is_const.hpp>
|
||||
#include <boost/utility/addressof.hpp>
|
||||
#include <boost/mpl/not.hpp>
|
||||
#include <boost/utility/enable_if.hpp>
|
||||
#include <boost/core/enable_if.hpp>
|
||||
|
||||
namespace boost {
|
||||
namespace bimaps {
|
||||
|
||||
@@ -21,7 +21,7 @@
|
||||
|
||||
#include <boost/bimap/relation/support/is_tag_of_member_at.hpp>
|
||||
#include <boost/bimap/detail/debug/static_error.hpp>
|
||||
#include <boost/utility/enable_if.hpp>
|
||||
#include <boost/core/enable_if.hpp>
|
||||
#include <boost/preprocessor/cat.hpp>
|
||||
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ namespace relation {
|
||||
/// \brief member_at::side idiom to access relation values and types using metaprogramming.
|
||||
/**
|
||||
|
||||
This tags are used to specify which member you want to acces when using a metafunction over
|
||||
This tags are used to specify which member you want to access when using a metafunction over
|
||||
a symmetrical type. The idea is to be able to write code like:
|
||||
|
||||
\code
|
||||
@@ -44,7 +44,7 @@ namespace member_at {
|
||||
|
||||
/// \brief Member at left tag
|
||||
/**
|
||||
See also member_at, rigth.
|
||||
See also member_at, right.
|
||||
**/
|
||||
|
||||
struct left {};
|
||||
|
||||
@@ -23,7 +23,7 @@
|
||||
#include <boost/call_traits.hpp>
|
||||
|
||||
#ifndef BOOST_BIMAP_DISABLE_SERIALIZATION
|
||||
#include <boost/serialization/nvp.hpp>
|
||||
#include <boost/core/serialization.hpp>
|
||||
#endif // BOOST_BIMAP_DISABLE_SERIALIZATION
|
||||
|
||||
#include <boost/functional/hash/hash.hpp>
|
||||
|
||||
@@ -26,7 +26,7 @@
|
||||
|
||||
#include <boost/call_traits.hpp>
|
||||
|
||||
#include <boost/utility/enable_if.hpp>
|
||||
#include <boost/core/enable_if.hpp>
|
||||
#include <boost/type_traits/is_same.hpp>
|
||||
#include <boost/mpl/if.hpp>
|
||||
#include <boost/mpl/vector.hpp>
|
||||
@@ -254,7 +254,7 @@ class mutant_relation;
|
||||
/// \brief A std::pair signature compatible class that allows you to control
|
||||
/// the internal structure of the data.
|
||||
/**
|
||||
This class allows you to specify the order in wich the two data types will be
|
||||
This class allows you to specify the order in which the two data types will be
|
||||
in the layout of the class.
|
||||
**/
|
||||
|
||||
|
||||
@@ -60,13 +60,13 @@ namespace relation {
|
||||
namespace support {
|
||||
|
||||
// Since it is very error-prone to directly write the hole bunch
|
||||
// of relation accesor. They are buil from litle macro blocks that
|
||||
// of relation accesor. They are built from little macro blocks that
|
||||
// are both more readable, leading to self docummenting code and a
|
||||
// lot more easier to understand and mantain.
|
||||
// lot more easier to understand and maintain.
|
||||
// It is very important to note that the three building blocks have
|
||||
// to laid in the same namespace in order to work. There is also
|
||||
// important to keep them in order.
|
||||
// The forward declaration are not necesary but they help a lot to
|
||||
// The forward declaration are not necessary but they help a lot to
|
||||
// the reader, as they undercover what is the signature of the
|
||||
// result code.
|
||||
// In the end, it is not quicker to do it in this way because you
|
||||
|
||||
@@ -22,12 +22,12 @@
|
||||
#include <boost/type_traits/is_same.hpp>
|
||||
|
||||
#include <boost/mpl/bool.hpp>
|
||||
#include <boost/utility/enable_if.hpp>
|
||||
#include <boost/core/enable_if.hpp>
|
||||
#include <boost/bimap/relation/support/member_with_tag.hpp>
|
||||
|
||||
/** \struct boost::bimaps::relation::support::is_tag_of_member_at_left
|
||||
|
||||
\brief Metafunction to test if a user tag is refering to the left member.
|
||||
\brief Metafunction to test if a user tag is referring to the left member.
|
||||
|
||||
\code
|
||||
|
||||
@@ -53,7 +53,7 @@ See also member_with_tag, member_at, is_tag_of_member_at_right.
|
||||
|
||||
/** \struct boost::bimaps::relation::support::is_tag_of_member_at_right
|
||||
|
||||
\brief Metafunction to test if a user tag is refering to the left member.
|
||||
\brief Metafunction to test if a user tag is referring to the left member.
|
||||
|
||||
\code
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@
|
||||
|
||||
#include <boost/bimap/relation/member_at.hpp>
|
||||
#include <boost/bimap/detail/debug/static_error.hpp>
|
||||
#include <boost/utility/enable_if.hpp>
|
||||
#include <boost/core/enable_if.hpp>
|
||||
#include <boost/type_traits/is_same.hpp>
|
||||
#include <boost/mpl/bool.hpp>
|
||||
#include <boost/mpl/not.hpp>
|
||||
|
||||
@@ -54,13 +54,13 @@ namespace support {
|
||||
|
||||
|
||||
// Since it is very error-prone to directly write the hole bunch
|
||||
// of relation accesor. They are buil from litle macro blocks that
|
||||
// of relation accesor. They are built from little macro blocks that
|
||||
// are both more readable, leading to self docummenting code and a
|
||||
// lot more easier to understand and mantain.
|
||||
// lot more easier to understand and maintain.
|
||||
// It is very important to note that the three building blocks have
|
||||
// to laid in the same namespace in order to work. There is also
|
||||
// important to keep them in order.
|
||||
// The forward declaration are not necesary but they help a lot to
|
||||
// The forward declaration are not necessary but they help a lot to
|
||||
// the reader, as they undercover what is the signature of the
|
||||
// result code.
|
||||
// In the end, it is not quicker to do it in this way because you
|
||||
|
||||
@@ -32,7 +32,7 @@ namespace boost {
|
||||
namespace bimaps {
|
||||
namespace relation {
|
||||
|
||||
/// \brief Base of symetrical tagged types.
|
||||
/// \brief Base of symmetrical tagged types.
|
||||
/**
|
||||
|
||||
**/
|
||||
|
||||
Reference in New Issue
Block a user