]> git.proxmox.com Git - ceph.git/blame - ceph/src/boost/libs/local_function/doc/getting_started.qbk
bump version to 12.2.2-pve1
[ceph.git] / ceph / src / boost / libs / local_function / doc / getting_started.qbk
CommitLineData
7c673cae
FG
1
2[/ Copyright (C) 2009-2012 Lorenzo Caminiti ]
3[/ Distributed under the Boost Software License, Version 1.0 ]
4[/ (see accompanying file LICENSE_1_0.txt or a copy at ]
5[/ http://www.boost.org/LICENSE_1_0.txt) ]
6[/ Home at http://www.boost.org/libs/local_function ]
7
8[section Getting Started]
9
10This section explains how to setup a system to use this library.
11
12[section This Documentation]
13
14Programmers should have enough knowledge to use this library after reading the __Introduction__, __Getting_Started__, and __Tutorial__ sections.
15The __Advanced_Topics__ and __Reference__ sections can be consulted at a later point to gain a more advanced knowledge of the library.
16All the other sections of this documentation can be considered optional.
17
18Some footnotes are marked by the word "*Rationale*".
19They explain reasons behind decisions made during the design and implementation of this library.
20
21In most of the examples presented in this documentation, the Boost.Detail/LightweightTest (=boost/detail/lightweight_test.hpp=) macro `BOOST_TEST` is used to check correctness conditions.
22The `BOOST_TEST` macro is conceptually similar to `assert` but a failure of the checked condition does not abort the program, instead it makes `boost::report_errors` return a non-zero program exit code.
23[footnote
24*Rationale.*
25Using Boost.Detail/LightweightTest allows to add the examples to the library regression tests so to make sure that they always compile and run correctly.
26]
27
28[endsect]
29
30[section Compilers and Platforms]
31
32The implementation of this library uses preprocessor and template meta-programming (as supported by __Boost_Preprocessor__ and __Boost_MPL__), templates with partial specializations and function pointers (similarly to __Boost_Function__), and automatic type deduction (as supported by __Boost_Typeof__).
33The authors originally developed and tested the library on:
34
35# GNU Compiler Collection (GCC) C++ 4.5.1 on Ubuntu Linux 10.
36# GCC 4.3.4 and 4.5.3 (with and without __CXX11__ features enabled `-std=c++0x`) on Cygwin.
37# Miscrosoft Visual C++ (MSVC) 8.0 on Windows XP and Windows 7.
38
39See the library [@http://www.boost.org/development/tests/release/developer/local_function.html regressions test results] for detailed information on supported compilers and platforms.
40
41[endsect]
42
43[section Installation]
44
45This library is composed of header files only.
46Therefore there is no pre-compiled object file which needs to be installed or linked.
47Programmers can simply instruct the C++ compiler where to find the library header files (`-I` option for GCC, `/I` option for MSVC, etc) and they can start compiling code using this library.
48
49The library implementation uses __Boost_Typeof__ to automatically deduce the types of bound variables (see the __Tutorial__ section).
50In order to compile code in type-of emulation mode, all types should be properly registered using `BOOST_TYPEOF_REGISTER_TYPE` and `BOOST_TYPEOF_REGISTER_TEMPLATE`, or appropriate __Boost_Typeof__ headers should be included (see the source code of most examples presented in this documentation).
51
52The followings are part of the library private API, they are not documented, and they should not be directly used by programmers:
53[footnote
54*Rationale.*
55This library concatenates symbols specified by the programmers (e.g., the local function name) with other symbols (e.g., special prefixes or file line numbers) to make internal symbols with unique names to avoid name clashes.
56These symbols are separated by the letter "`X`" when they are concatenated so they read more easily during debugging (the underscore character "`_`" could not be used instead of the letter "`X`" because if the original symbols already contained a leading or trailing underscore, the concatenation could result in a symbol with double underscores "`__`" which is reserved by the C++ standard).
57The "aux" symbols are private to this library while the "detail" symbols may be used within Boost by other libraries but they are still not part of this library public API.
58]
59
60* Any symbol defined by files within the =boost/local_function/aux_/= or =boost/local_function/detail/= directory (these header files should not be directly included by programmers).
61* Any symbol within the `boost::local_function::aux` or `boost::local_function::detail` namespace.
62* Any symbol prefixed by `boost_local_function_aux_...` or `boost_local_function_detail_...` (regardless of its namespace).
63* Any symbol prefixed by `BOOST_LOCAL_FUNCTION_AUX_...` or `BOOST_LOCAL_FUNCTION_DETAIL_...` (regardless of its namespace).
64
65Some of the library behaviour can be changed at compile-time by defining special /configuration macros/.
66If a configuration macro is left undefined, the library will use an appropriate default value for it.
67All configuration macros are defined in the header file [headerref boost/local_function/config.hpp].
68It is strongly recommended not to change the library configuration macro definitions unless strictly necessary.
69
70[endsect]
71
72[endsect]
73