|
-Home | +Home | Libraries | -People | -FAQ | +People | +FAQ | More |
Boost.FunctionTypes uses tag types to encode properties that are not types per se, such as calling convention or whether a function is variadic or cv- @@ -85,11 +84,7 @@
| - | + | Copyright © 2004 -2007 Tobias Schwinger |
|
-Home | +Home | Libraries | -People | -FAQ | +People | +FAQ | More |
Thanks go to the following people for supporting the development of this library in one or the other way: @@ -79,11 +78,7 @@
| - | + | Copyright © 2004 -2007 Tobias Schwinger |
|
-Home | +Home | Libraries | -People | -FAQ | +People | +FAQ | More |
Boost.FunctionTypes provides functionality to classify, decompose and synthesize
function, function pointer, function reference and pointer to member types.
@@ -57,34 +56,35 @@
constant called value.
-is_function_pointer< bool(*)(int) >::value // == true +is_function_pointer< bool(*)(int) >::value // == true -function_arity< bool(*)(int) >::value // == 1 +function_arity< bool(*)(int) >::value // == 1
Templates that encapsulate properties that are single types contain a type
member called type.
-function_type< mpl::vector<bool,int> >::type // is bool(int) +function_type< mpl::vector<bool,int> >::type // is bool(int) -result_type< bool(&)(int) >::type // is bool +result_type< bool(&)(int) >::type // is bool
Templates that encapsulate properties that are type lists model an MPL-compatible type sequence.
-parameter_types< bool(int) > // models an MPL sequence +parameter_types< bool(int) > // models an MPL sequence
| - | + | Copyright © 2004 -2007 Tobias Schwinger |
|
-Home | +Home | Libraries | -People | -FAQ | +People | +FAQ | More |
The library does not define the required members of class templates in case of an error. This technique causes the compiler to stop displaying diagnostics @@ -41,10 +40,10 @@ The library's components have limited error conditions, so problematic input can be spotted easily.
-MPL provides algorithms on Sequences, so transformations (such as turning by-value parameter types into const references for optimized forwarding or computing @@ -54,20 +53,20 @@ other Boost libraries (most importantly Fusion), so another reason is interoperability.
-Despite their syntax, pointer to member object types can be seen as dereferencing functionals.
-
This-pointer, this-reference or just
the object (or maybe even a smart pointer to the object) plus adjustments of
@@ -80,10 +79,10 @@
client to adjust the class type before the sequence is formed and then treat
all parameters uniformly.
Let's consider the alternatives.
@@ -99,12 +98,12 @@ parameters do not work within MPL lambda expressions and can cause problems with older compilers. -Yes, but it isn't immediately obvious as the set of possible MPL sequences isn't inherently disjoint from the set of callable builtin types. @@ -114,23 +113,25 @@ idea, because builtin types are accessible before the headers that make the type a sequence have been included, which can easily violate the ODR.
-this parameter count for the function arity
of member functions?
- It was found preferable that the following condition holds:
-mpl::size< parameter_types<T> >::value == function_arity<T>::value +mpl::size< parameter_types<T> >::value == function_arity<T>::value-
A cv-qualified pointer is still a pointer. It usually doesn't matter and even if it does, it's a job for Boost.TypeTraits. @@ -138,11 +139,7 @@
| - | + | Copyright © 2004 -2007 Tobias Schwinger |
|
-Home | +Home | Libraries | -People | -FAQ | +People | +FAQ | More |
| - | + | Copyright © 2004 -2007 Tobias Schwinger |
 |
-Home | +Home | Libraries | -People | -FAQ | +People | +FAQ | More |
-template<typename T, typename Tag = null_tag> +template<typename T, typename Tag = null_tag> struct is_function;
@@ -90,11 +93,12 @@
-template<typename T, typename Tag = null_tag> +template<typename T, typename Tag = null_tag> struct is_function_pointer;
@@ -133,11 +137,12 @@
-template<typename T, typename Tag = null_tag> +template<typename T, typename Tag = null_tag> struct is_function_reference;
@@ -176,11 +181,12 @@
-template<typename T, typename Tag = null_tag> +template<typename T, typename Tag = null_tag> struct is_member_pointer;
@@ -219,9 +225,9 @@
template<typename T> struct is_member_object_pointer; @@ -257,11 +263,12 @@-template<typename T, typename Tag = null_tag> +template<typename T, typename Tag = null_tag> struct is_member_function_pointer;@@ -300,11 +307,12 @@
-template<typename T, typename Tag = null_tag> +template<typename T, typename Tag = null_tag> struct is_callable_builtin;@@ -343,11 +351,12 @@
-template<typename T, typename Tag = null_tag> +template<typename T, typename Tag = null_tag> struct is_nonmember_callable_builtin;@@ -388,11 +397,7 @@
| - | + | Copyright © 2004 -2007 Tobias Schwinger |
|
-Home | +Home | Libraries | -People | -FAQ | +People | +FAQ | More |
template<typename F> struct result_type; @@ -75,9 +78,9 @@template<typename F, class ClassTransform = add_reference<_> > struct parameter_types; @@ -121,9 +124,9 @@template<typename F> struct function_arity; @@ -166,9 +169,9 @@template<typename T, class ClassTransform = add_reference<_> > struct components; @@ -213,17 +216,14 @@If
Tis no callable builtin type, the component types - are an empty sequence and the Tag's meaning is equivalent to thenull_tag. + are an empty sequence and the Tag's meaning is equivalent to thenull_tag.
| - | + | Copyright © 2004 -2007 Tobias Schwinger |
|
-Home | +Home | Libraries | -People | -FAQ | +People | +FAQ | More |
Expands to a numeric value that describes the maximum function arity supported by the library. @@ -67,16 +66,17 @@
Expands to a sequence
of ternary tuples
(these data types are defined in the documentation
of the Boost Preprocessor library). Each sequence element describes
one calling convention specifier. The first element in each tuple is the
- macro suffix for BOOST_FT_CC_*,
+ macro suffix for BOOST_FT_CC_*,
the second element is the name of the tag that describes the calling convention
and the third is the name of the specifier. The specifier is allowed to
be an empty string, so the third tuple element is either BOOST_PP_EMPTY
@@ -106,13 +106,15 @@
- Enables a specific calling convention. * denotes the macro suffix, as defined
- by BOOST_FT_CC_NAMES
- or BOOST_FT_BUILTIN_CC_NAMES.
+ Enables a specific calling convention. * dentoes the macro suffix, as defined
+ by BOOST_FT_CC_NAMES
+ or BOOST_FT_BUILTIN_CC_NAMES.
The macro expands to a list of restrictions, separated by the |
@@ -147,9 +149,9 @@
Defining this macro causes the following macros to be defined, if not defined already: @@ -162,9 +164,9 @@
This macro allows to change the syntax of callable builtin types. It is useful to handle the compiler specific placement of the calling convention @@ -180,9 +182,9 @@
Set to void for compilers that insist on a void
parameter for nullary function types, empty by default.
@@ -190,9 +192,9 @@
Disables support for cv-qualified function types. Cv-qualified function types are illegal by the current standard version, but there is a pending @@ -207,9 +209,9 @@
Makes the compiler preprocess as much as possible of the library code (rather than loading already-preprocessed header files) if defined. @@ -217,27 +219,24 @@
Makes the compiler preprocess the loop over possible names for custom calling conventions (rather than loading an already-preprocessed header file) if defined.
- This macro is defined automatically if BOOST_FT_CC_NAMES
+ This macro is defined automatically if BOOST_FT_CC_NAMES
has been defined.
| - | + | Copyright © 2004 -2007 Tobias Schwinger |
|
-Home | +Home | Libraries | -People | -FAQ | +People | +FAQ | More |
-template<typename Types, typename Tag = null_tag> +template<typename Types, typename Tag = null_tag> struct function_type;
@@ -81,11 +84,12 @@
-template<typename Types, typename Tag = null_tag> +template<typename Types, typename Tag = null_tag> struct function_pointer;
@@ -123,11 +127,12 @@
-template<typename Types, typename Tag = null_tag> +template<typename Types, typename Tag = null_tag> struct function_reference;
@@ -165,11 +170,12 @@
-template<typename Types, typename Tag = null_tag> +template<typename Types, typename Tag = null_tag> struct member_function_pointer;
@@ -214,11 +220,7 @@
| - | + | Copyright © 2004 -2007 Tobias Schwinger |
|
-Home | +Home | Libraries | -People | -FAQ | +People | +FAQ | More |
typedef unspecified variadic;@@ -73,9 +73,9 @@
typedef unspecified non_variadic;@@ -91,9 +91,9 @@
typedef unspecified default_cc;@@ -109,9 +109,9 @@
typedef unspecified const_qualified;@@ -127,9 +127,9 @@
typedef unspecified non_const;@@ -145,9 +145,9 @@
typedef unspecified volatile_qualified;@@ -163,9 +163,9 @@
typedef unspecified non_volatile;@@ -181,8 +181,7 @@
typedef unspecified non_cv;@@ -200,9 +199,9 @@
typedef unspecified const_non_volatile;@@ -220,9 +219,9 @@
typedef unspecified volatile_non_const;@@ -240,9 +239,9 @@
typedef unspecified cv_qualified;@@ -260,9 +259,9 @@
typedef unspecified null_tag;@@ -278,8 +277,7 @@
template<class Tag1, class Tag2, class Tag3 = null_tag, class Tag4 = null_tag> @@ -312,11 +310,7 @@
| - | + | Copyright © 2004 -2007 Tobias Schwinger |
|
-Home | +Home | Libraries | -People | -FAQ | +People | +FAQ | More |
Generic libraries that accept callable arguments are common in C++. Accepting a callable argument of builin type often involves a lot of repetitive code @@ -144,7 +143,8 @@ arguments from a type sequence in a single expression:
-static_cast<function_pointer<Seq>::type>(& overloaded) +static_cast<function_pointer<Seq>::type>(& overloaded)
This technique can be occasionally more flexible than template argument deduction @@ -165,11 +165,7 @@
| - | + | Copyright © 2004 -2007 Tobias Schwinger |
 |
-Home | +Home | Libraries | -People | -FAQ | +People | +FAQ | More |
Copyright © 2004 -2007 Tobias Schwinger
Distributed under the Boost Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
@@ -46,8 +46,8 @@Last revised: March 14, 2008 at 18:36:46 +0000 |
-+ | Last revised: November 05, 2007 at 18:24:58 +0100 |
+
