From 970a90b365e64d51a7e83088ac91deb629fac9a4 Mon Sep 17 00:00:00 2001
From: John Maddock Occationally the end user may need to provide their own specialization for one
of the type traits - typically where intrinsic compiler support is required to
implement a specific trait fully. These specializations should derive
- from boost::true_type or boost::false_type as appropriate:
# include <boost/type_traits/is_pod.hpp> # include <boost/type_traits/is_class.hpp> # include <boost/type_traits/is_union.hpp> @@ -870,16 +870,16 @@ namespace boost { template<> struct is_pod<my_pod> - : public true_type{}; + : public mpl::true_{}; template<> struct is_pod<my_union> - : public true_type{}; + : public mpl::true_{}; template<> struct is_union<my_union> - : public true_type{}; + : public mpl::true_{}; template<> struct is_class<my_union> - : public false_type{}; + : public mpl::false_{}; }diff --git a/test/udt_specialisations.cpp b/test/udt_specialisations.cpp index 7554f3d..ba45d74 100644 --- a/test/udt_specialisations.cpp +++ b/test/udt_specialisations.cpp @@ -20,16 +20,16 @@ namespace tt { template<> struct is_pod