Home
last modified time | relevance | path

Searched refs:variadic (Results 1 – 25 of 272) sorted by relevance

1234567891011

/third_party/boost/libs/vmd/doc/
Dvmd_variadic_macros.qbk8 [section:vmd_vmacros Using variadic macros]
15 information when passed to a variadic macro I call 'variadic macro data',
16 which gives its name to this library. The more general term 'variadic data'
23 The Boost PP library has support for variadic macros and uses its
26 the compiler being used supports variadic macros. When BOOST_PP_VARIADICS
27 is set to 1 the compiler supports variadic macros, otherwise when
28 BOOST_PP_VARIADICS is set to 0 the compiler does not support variadic macros.
32 determine if a compiler has support for variadic macros.
34 [heading Determining variadic macro support]
36 The VMD library automatically determines whether variadic macro support
[all …]
Dvmd_design.qbk12 functionality, and I realized that if I could use variadic macros with
14 Therefore the initial main design goal of this library was to interoperate variadic macro data
18 adding variadic macro data support to Boost PP. While this was being done,
19 but the variadic macro data support had not yet been finalized in Boost PP,
20 I still maintained the library in two modes, either its own variadic data
21 functionality or deferring to the implementation of variadic macros in the
24 Once support for variadic data had been added to Boost PP I stripped
25 down the functionality of this library to only include variadic macro
40 without the use of variadic macros. But I had kept these features at a
41 minimum because of the difficulty of using variadic macros with compilers,
[all …]
Dvmd_internal.qbk11 to determine or change the way variadic macros are used in the library.
14 It is used to denote whether variadic data support exists for the particular compiler
15 the end-user is using. VMD also uses this macro to determine whether variadic
17 to determine whether or not variadic macros are supported. Furthermore
20 used as not supporting or supporting variadic macros. If a compiler does
21 not support variadic macro none of the macros in VMD are defined.
Dvmd_sequence_convert.qbk11 data type. Likewise you can also convert a sequence to variadic data even though the
12 Boost PP data types have much greater functionality than variadic data in Boost PP.
14 To convert a sequence to a Boost PP data type or variadic data the macros to be used are:
20 * BOOST_VMD_ENUM(sequence) to convert the sequence to variadic data
35 a seq, tuple, or variadic data; the result is an empty array or list when
56 …BOOST_VMD_ENUM(SEQUENCE_MULTI_2) will return multi-element variadic data 'BOOST_VMD_TYPE_SEQ,(2,(5…
Dvmd_examples.qbk50 # Convert our variadic parameters to a tuple since access to tuple
74 'name' of the 'default' case. In the variadic parameters the
128 The macro used is called BOOST_TTI_TEMPLATE. The macro has both a variadic version and
129 a non-variadic version.
131 In the non-variadic version the macro always takes two parameters for introspecting
138 the non-variadic macro would be:
144 Choosing a Boost PP tuple was not an option since for non-variadic macros there is no
147 For the variadic version variadic parameters are used so the notation would be:
149 BOOST_TTI_TEMPLATE(MyTemplate,class,int) // uses variadic parameters
153 But for compatibility with the non-variadic version the end-user
[all …]
Dvmd_compilers.qbk26 take a single parameter rather than variadic data because this
27 version of VC++ does not accept variadic data which may be empty.
30 variadic macro support for Boost PP as represented by the BOOST_PP_VARIADICS macro.
Dvmd_useful.qbk8 [section:vmd_useful Useful variadic macros not in Boost PP]
13 Another area of functionality of VMD involves useful variadic macros, based
15 already in Boost PP. These variadic macros can be divided into sections
/third_party/boost/libs/function_types/test/classification/
Dis_variadic.cpp33 ft::is_callable_builtin< func, ft::variadic >
45 ft::is_callable_builtin< nv_func, ft::variadic >
57 ft::is_callable_builtin< func_ptr, ft::variadic>
69 ft::is_callable_builtin< nv_func_ptr, ft::variadic>
85 ft::is_callable_builtin< mem_func_ptr, ft::variadic >
97 ft::is_callable_builtin< nv_mem_func_ptr, ft::variadic >
125 ft::is_callable_builtin< C, ft::variadic >
137 ft::is_callable_builtin< mem_ptr, ft::variadic >
/third_party/boost/libs/tti/doc/
Dtti_detail_has_template.qbk46 [heading Variadic and non-variadic macro usage]
49 supporting variadic macros or not supporting variadic macros.
52 supports variadic macros by checking the value of the macro
55 macro. A value of 1 indicates the compiler supports variadic macros
56 while a value of 0 indicates the compiler does not support variadic
60 normally support variadic macros. Even before the latest C++11 standard
61 a number of C++ compilers already supported variadic macros. If you feel
62 your compiler supports variadic macros and BOOST_PP_VARIADIC is 0 even
66 [heading Non-variadic macro usage]
68 We start with syntax for compilers not supporting variadic macros since this
[all …]
Dtti_detail.qbk106 Using variadic macros:
110 Not using variadic macros:
126 Using variadic macros:
128 [macroref BOOST_TTI_HAS_TEMPLATE](name,...[footnote The template parameters as variadic data.])
130 Not using variadic macros:
188 Using variadic macros:
190 …EMBER_FUNCTION_TEMPLATE](name,...[footnote The instantiated template parameters as variadic data.])
192 Not using variadic macros:
260 Using variadic macros:
262 …EMBER_FUNCTION_TEMPLATE](name,...[footnote The instantiated template parameters as variadic data.])
[all …]
/third_party/boost/libs/mpl/doc/src/refmanual/
DVariadicSequence.rst10 *variadic* and *numbered* forms. If ``seq`` is a generic name for some
11 |Variadic Sequence|, its *variadic form* allows us to specify a sequence of
32 .. The variadic form of sequence ``seq`` is defined in
111 .. |variadic| replace:: `variadic`_ substdef in See also
112 .. _`variadic`: `Variadic Sequence`_ target in See also
114 .. |variadic forms| replace:: `variadic forms`_
115 .. _`variadic forms`: `Variadic Sequence`_
/third_party/boost/libs/local_function/doc/
Dno_variadic_macros.qbk10 This section illustrates an alternative syntax for compilers without variadic macro support.
15 However, in the rare case that programmers need to use this library on a compiler without variadic …
19 Instead of the comma-separated list that we have seen so far which requires variadic macros:
23 For example, the following syntax is accepted on all compilers with and without variadic macros (se…
27 However, on compilers with variadic macros the comma-separated syntax we have seen so far is prefer…
31 …accept both syntaxes on compilers with variadic macros and only the sequence syntax on compilers w…
32 …tion parameter list is always specified using `void` on compilers with and without variadic macros:
/third_party/boost/libs/function_types/test/custom_ccs/
Dproperty_tag.cpp15 typedef ft::tag<ft::variadic,ft::non_volatile,ft::non_const,ft::default_cc> tag1;
17 typedef ft::tag<ft::cv_qualified,ft::variadic> tag3;
19 typedef ft::tag<ft::variadic,ft::volatile_non_const> tag5;
20 typedef ft::tag<ft::volatile_qualified,ft::non_const,ft::variadic> tag6;
24 BOOST_MPL_ASSERT((ft::has_property_tag<tag1, ft::variadic>));
55 BOOST_MPL_ASSERT_NOT((ft::has_property_tag<tag7, ft::variadic>));
/third_party/boost/libs/function_types/test/synthesis/
Dvariadic_function_synthesis.cpp29 ft::function_type<mpl::vector<int>, ft::variadic>::type, expected_v_1
37 ft::function_pointer<mpl::vector<int>, ft::variadic>::type, expected_v_1 *
46 ft::function_reference<mpl::vector<int>, ft::variadic>::type, expected_v_1 &
55 ft::member_function_pointer<mpl::vector<int,C>, ft::variadic>::type
/third_party/boost/libs/tti/test/
DJamfile.v215 <toolset>gcc-4.3.0:<cxxflags>-Wno-variadic-macros
16 <toolset>gcc-4.4.0:<cxxflags>-Wno-variadic-macros
17 <toolset>gcc-4.4.7:<cxxflags>-Wno-variadic-macros
18 <toolset>gcc-4.5.0:<cxxflags>-Wno-variadic-macros
20 <toolset>gcc-4.5.2:<cxxflags>-Wno-variadic-macros
21 <toolset>gcc-4.6.0:<cxxflags>-Wno-variadic-macros
22 <toolset>gcc-4.6.1:<cxxflags>-Wno-variadic-macros
23 <toolset>gcc-4.6.2:<cxxflags>-Wno-variadic-macros
24 <toolset>gcc-4.6.3:<cxxflags>-Wno-variadic-macros
25 <toolset>gcc-4.7.0:<cxxflags>-Wno-variadic-macros
[all …]
/third_party/boost/libs/chrono/build/
DJamfile.v238 #<toolset>gcc:<cxxflags>-Wno-variadic-macros
39 <toolset>gcc-4:<cxxflags>-Wno-variadic-macros
40 <toolset>gcc-5:<cxxflags>-Wno-variadic-macros
44 #<toolset>darwin:<cxxflags>-Wno-variadic-macros
45 <toolset>darwin-4:<cxxflags>-Wno-variadic-macros
46 <toolset>darwin-5:<cxxflags>-Wno-variadic-macros
53 <toolset>clang:<cxxflags>-Wno-variadic-macros
/third_party/boost/boost/function_types/detail/pp_retag_default_cc/
Dmaster.hpp29 # define BOOST_PP_VALUE non_member|member|non_variadic|variadic
65 # define BOOST_PP_VALUE default_cc_|non_member|variadic
75 # define BOOST_PP_VALUE default_cc_|member|variadic
/third_party/boost/libs/preprocessor/test/
DJamfile.v210 <toolset>gcc-4.3.0:<cxxflags>-Wno-variadic-macros
12 <toolset>gcc-4.4.0:<cxxflags>-Wno-variadic-macros
14 <toolset>gcc-4.5.0:<cxxflags>-Wno-variadic-macros
17 <toolset>gcc-4.5.2:<cxxflags>-Wno-variadic-macros
54 [ compile variadic.cpp ]
134 [ compile variadic.c
/third_party/boost/libs/hana/include/boost/hana/detail/variadic/
Dreverse_apply.hpp17 BOOST_HANA_NAMESPACE_BEGIN namespace detail { namespace variadic { namespace
20 return detail::variadic::reverse_apply_unrolled(
/third_party/boost/boost/hana/detail/variadic/
Dreverse_apply.hpp17 BOOST_HANA_NAMESPACE_BEGIN namespace detail { namespace variadic { namespace
20 return detail::variadic::reverse_apply_unrolled(
/third_party/boost/libs/fusion/doc/
Dcontainer.qbk89 For C++11 compilers, the variadic function interface has no upper bound.
91 For C++03 compilers, the The variadic form accepts `0` to
242 For C++11 compilers, the variadic function interface has no upper bound.
244 For C++03 compilers, the variadic class interface accepts `0` to
329 For C++11 compilers, the variadic class interface has no upper bound.
331 For C++03 compilers, the variadic class interface accepts `0` to
544 For C++11 compilers, the variadic function interface has no upper bound.
546 For C++03 compilers, the variadic class interface accepts `0` to
628 For C++11 compilers, the variadic function interface has no upper bound.
630 For C++03 compilers, the variadic class interface accepts `0` to
[all …]
/third_party/boost/libs/hana/test/detail/variadic/
Dreverse_apply.cpp63 check(hana::detail::variadic::reverse_apply); in main()
65 return hana::detail::variadic::reverse_apply_flat(f, x...); in main()
68 return hana::detail::variadic::reverse_apply_unrolled(f, x...); in main()
/third_party/boost/boost/hana/detail/variadic/reverse_apply/
Dflat.hpp19 BOOST_HANA_NAMESPACE_BEGIN namespace detail { namespace variadic { namespace
25 detail::variadic::at<sizeof...(x) - i - 1>( in reverse_apply_flat_helper()
/third_party/boost/libs/hana/include/boost/hana/detail/variadic/reverse_apply/
Dflat.hpp19 BOOST_HANA_NAMESPACE_BEGIN namespace detail { namespace variadic { namespace
25 detail::variadic::at<sizeof...(x) - i - 1>( in reverse_apply_flat_helper()
/third_party/boost/libs/lexical_cast/test/
DJamfile.v223 …Not a lexical_cast related warning: boost/preprocessor/variadic/elem.hpp:29:46: warning: variadic …
24 <toolset>clang:<cxxflags>-Wno-variadic-macros
25 <toolset>gcc:<cxxflags>-Wno-variadic-macros

1234567891011