std::pairs of iterators, and raw
arrays (and more), such that the same generic code can work with them all.
The basic idea is to add another layer of indirection using metafunctions and
+href="../../mpl/doc/refmanual/metafunction.html">metafunctions and
free-standing functions so syntactic and/or semantic differences can be removed.
@@ -130,7 +130,7 @@ class=identifier>assign(
By using the free-standing functions and metafunctions, the code automatically
+href="../../mpl/doc/refmanual/metafunction.html">metafunctions, the code automatically
works for all the types supported by this library; now and in the future.
Notice that we have to
provide two version of find() since we cannot forward a non-const
diff --git a/doc/range.html b/doc/range.html
index 704b68a..71c9720 100755
--- a/doc/range.html
+++ b/doc/range.html
@@ -81,7 +81,7 @@ category of the underlying iterator type. Therefore
for more information about naming of ranges.
The concepts described below specifies associated types as -metafunctions and all +metafunctions and all functions as free-standing functions to allow for a layer of indirection.
Notice that these metafunctions must be defined in namespace diff --git a/doc/style.html b/doc/style.html index ff5d10f..9a5617e 100755 --- a/doc/style.html +++ b/doc/style.html @@ -19,7 +19,7 @@
- The use of a consistent terminology is as important for Ranges + The use of a consistent terminology is as important for Ranges and range-based algorithms as it is for iterators and iterator-based algorithms. If a conventional set of names are adopted, we can avoid misunderstandings and write generic function prototypes that are self-documenting. diff --git a/index.html b/index.html index dd268ca..e04f0fa 100755 --- a/index.html +++ b/index.html @@ -39,7 +39,7 @@