|
Boost-Commit : |
Subject: [Boost-commit] svn:boost r68797 - in sandbox/tti/libs/tti/doc: . html
From: eldiener_at_[hidden]
Date: 2011-02-11 21:31:07
Author: eldiener
Date: 2011-02-11 21:31:07 EST (Fri, 11 Feb 2011)
New Revision: 68797
URL: http://svn.boost.org/trac/boost/changeset/68797
Log:
Update doc to reflect boost::tti namespace consistently.
Removed:
sandbox/tti/libs/tti/doc/html/
Text files modified:
sandbox/tti/libs/tti/doc/tti_detail.qbk | 2 +-
sandbox/tti/libs/tti/doc/tti_functionality.qbk | 6 +++---
sandbox/tti/libs/tti/doc/tti_metafunctions.qbk | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
Modified: sandbox/tti/libs/tti/doc/tti_detail.qbk
==============================================================================
--- sandbox/tti/libs/tti/doc/tti_detail.qbk (original)
+++ sandbox/tti/libs/tti/doc/tti_detail.qbk 2011-02-11 21:31:07 EST (Fri, 11 Feb 2011)
@@ -1,6 +1,6 @@
[section:tti_detail Macro Metafunctions]
-The TTI library uses macros to create metafunctions, in the top-level 'tti' namespace,
+The TTI library uses macros to create metafunctions, in the boost::tti' namespace,
for introspecting an inner element by name. Each macro for a particular type of inner
element has two forms, the simple one where the first macro parameter designating the
'name' of the inner element is used to create the name of the metafunction, and the
Modified: sandbox/tti/libs/tti/doc/tti_functionality.qbk
==============================================================================
--- sandbox/tti/libs/tti/doc/tti_functionality.qbk (original)
+++ sandbox/tti/libs/tti/doc/tti_functionality.qbk 2011-02-11 21:31:07 EST (Fri, 11 Feb 2011)
@@ -21,8 +21,8 @@
introspect the information that is needed. The name itself of the inner element is always passed
to the macro as a macro parameter, but other macro parameters may also be needed in some cases.
-All of the macros start with the prefix BOOST\_TTI\_, create their metafunctions in a top-level
-namespace called 'tti', and come in two forms:
+All of the macros start with the prefix BOOST\_TTI\_, create their metafunctions in a
+namespace called 'boost::tti', and come in two forms:
# In the simplest form the 'name' of the inner element is used directly to generate the name
of the metafunction as well as serving as the 'name' to introspect. To generate the name of
@@ -33,7 +33,7 @@
# In the slightly more complicated form, which I call the complex form, the macro starts with
BOOST\_TTI\_TRAIT\_ and a 'trait' name is passed as the first parameter, with the 'name' of the inner
element as the second parameter. The 'trait' name serves only to completely name the metafunction in
- the tti namespace. As an example, for the macro BOOST\_TTI\_TRAIT\_HAS\_TYPE(MyTrait,MyType) the name of
+ the boost::tti namespace. As an example, for the macro BOOST\_TTI\_TRAIT\_HAS\_TYPE(MyTrait,MyType) the name of
the metafunction is 'boost::tti::MyTrait' and it will look for an inner type called 'MyType'. Every
macro has a corresponding complex form.
Modified: sandbox/tti/libs/tti/doc/tti_metafunctions.qbk
==============================================================================
--- sandbox/tti/libs/tti/doc/tti_metafunctions.qbk (original)
+++ sandbox/tti/libs/tti/doc/tti_metafunctions.qbk 2011-02-11 21:31:07 EST (Fri, 11 Feb 2011)
@@ -58,7 +58,7 @@
existence the metaprogrammer is introspecting. A more detailed explanation can be found
in the reference section, and examples of usage can be found in the
[link sectti_usingNTM "Using the Nullary Type Metafunctions"] section.
-All of the metafunctions are in the top-level 'tti' namespace,
+All of the metafunctions are in the top-level 'boost::tti' namespace,
all have a particular name based on the type of its functionality, and all begin with the prefix
'mf_' so as not to conflict with the macro metafunction names generated by the library.
Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk