From 2be4714cc5fe2a9c9a90d2e881c2e34cb6bd82c1 Mon Sep 17 00:00:00 2001 From: Felix Gruber Date: Fri, 20 Mar 2015 22:42:27 +0100 Subject: [PATCH] fix typos in the documentation --- doc/index.html | 2 +- doc/tutorial/incomplete-support-for.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/index.html b/doc/index.html index 3b9fc7e..fb94a45 100644 --- a/doc/index.html +++ b/doc/index.html @@ -35,7 +35,7 @@ metafunctions. It provides a conceptual foundation and an extensive set of powerful and coherent tools that make doing explict metaprogramming in C++ as easy and enjoyable as possible within the current language.

There are several places to start when getting familiar with the library, -depending on what your know about metaprogramming in general and +depending on what you know about metaprogramming in general and C++ template metaprogramming in particular. Starting with Boost version 1.32, the MPL comes with both an in-depth tutorial on its fundamental concepts and an annotated reference manual covering all concepts diff --git a/doc/tutorial/incomplete-support-for.html b/doc/tutorial/incomplete-support-for.html index 991283d..4e30f13 100644 --- a/doc/tutorial/incomplete-support-for.html +++ b/doc/tutorial/incomplete-support-for.html @@ -113,7 +113,7 @@ arguments), which comes down to the follwing two criteria:

placeholders do contain these).

If these two hold, you can safely put BOOST_MPL_AUX_LAMBDA_SUPPORT inside -your metafunction and forget about the issue. If not, your are out of luck and +your metafunction and forget about the issue. If not, you are out of luck and probably have to write a metafunction class instead.

The good news are that most of the MPL's own metafunctions and Boost.Type Traits templates are "placeholder-safe" and have the workaround applied to them, so