Work on doc. Added notations & C++ intro

doc/CMakeLists.txt

@@ -107,7 +107,7 @@ install(DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/themes/triqs DESTINATION share/tri
 
 # PDF documentation
 if (Build_PDF_Documentation)
- add_dependencies(docs_sphinx_pdf_cpp triqs )
+ add_dependencies(docs_sphinx_pdf triqs )
  install(FILES ${sphinx_top_pdf} DESTINATION share/doc/triqs/)
 endif()
 

doc/reference/c++/contents.rst

@@ -9,12 +9,13 @@ C++
 .. toctree::
    :maxdepth: 1
 
+   conventions
    using_the_lib/contents
    arrays/contents
    gf/contents
    clef/contents
    mctools/intro
-   det_manip/det_manip
+   det_manip/contents
    parameters/parameters
    utilities/contents
 

doc/reference/c++/conventions.rst

@@ -0,0 +1,43 @@
+C++11/14 & notations
+=====================
+
+C++11/C++14
+---------------
+
+TRIQS is a C++11 library. It *requires* a last generation C++ compiler (Cf :ref:`require_cxx_compilers`).
+
+Indeed, the development of C++ is very dynamic these years.
+The language and its usage is changing very profoundly with the introduction of several 
+notions (e.g. move semantics, type deduction, lambda, variadic templates  ...).
+Moreover, C++11 compliant compilers are now widely available, with gcc and clang.
+
+A major consequence of this evolution is that writing libraries
+has become much more accessible, at a *much* lower cost in development time,
+with clearer, shorter and more readable code, hence maintainable.
+Efficient techniques which were considered before as complex and reserved to professional C++ experts
+are now becoming simple to implement, like e.g. expression templates.
+
+The implementation of most of the TRIQS library (e.g. clef, arrays) would be either impossible or at least 
+much more complex and time consuming (with a lot of abstruse boost-like construction)
+in previous versions of C++.
+
+Besides, this evolution is not finished.
+The new coming standard, C++14, expected to be adopted and implemented very soon, 
+will still make it a lot better. In particular, the concept support (template constraints)
+will hopefully solve the most problematic issue with metaprogramming techniques, i.e. the lack of concept
+check at compile time, resulting in long and obscur error messages from the compiler when *using* the library.
+Hence, TRIQS will move to C++14 as soon as compilers are available.
+
+Notation
+----------
+
+In the documentation, we make use in particular of the C++14 concept notation for template.
+For example ::
+
+  template<ImmutableArray A> void f(A const & a);
+
+means that f is a template ::
+  
+  template<typename A> void f(A const & a);
+ 
+which is enabled or valid only for types A which models the `ImmutableArray` concept.

doc/reference/c++/det_manip/contents.rst

@@ -2,7 +2,7 @@
 
 Manipulations of determinants
 =============================
-
+ 
 .. warning::
 
    This library is stable, but documentation is still a bit spartan ...

doc/reference/c++/mctools/intro.rst

@@ -1,13 +1,14 @@
 .. _montecarlo:
 
-The Monte Carlo class
-=====================
+Tools for Monte Carlo
+=========================
 
-The TRIQS library has a class called ``mc_generic`` which allows you to write
+The TRIQS library provide simple tools for Monte Carlo codes, like  a class called ``mc_generic`` which allows you to write
 Monte Carlo algorithms in a simple framework. The class takes care of the basic
 mechanics which is common to any Monte Carlo method so that you can focus on
 the implementation details of your specific algorithm.
 
+
 .. toctree::
    :maxdepth: 2