From b647064f3a804f8d2b6a934680cd352c8b6e4587 Mon Sep 17 00:00:00 2001 From: Denis Davydov Date: Thu, 27 Oct 2016 19:52:31 +0200 Subject: [PATCH] update text --- doc/doxygen/headers/coding_conventions.h | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/doc/doxygen/headers/coding_conventions.h b/doc/doxygen/headers/coding_conventions.h index 8f193211f8..ab72494b63 100644 --- a/doc/doxygen/headers/coding_conventions.h +++ b/doc/doxygen/headers/coding_conventions.h @@ -185,7 +185,7 @@ instantiate, and for them the .templates.h file will not be of any It will also not slow down their compilations because nothing they see will #include the .templates.h file. But users who define their own (vector, matrix, ...) types can instantiate the template functions with their -own user-defined types by #includeing the .templates.h files. +own user-defined types by including the .templates.h files.
  • Finally, if we can not assume in advance which values template arguments will take (e.g., any class derived from Subscriptor can be used as an argument), @@ -196,10 +196,12 @@ file with declarations. The definitions should be guarded with #ifndef DOX

    For the first two cases, instantiation instructions are defined in .inst.in -files. These files are processed by custom CMake scripts to generate .inst files -using lists of parameters (vector classes, dimensions, tensor ranks, etc) -defined in cmake/config/template-arguments.in. It is those .inst -files that are eventually included from the corresponding .cc files.

    +files. They are processed by a binary called expand_instantiations (built from +cmake/scripts/expand_instantiations.cc) and the parameters are +defined dynamically through cmake depending on your configuration (see +share/deal.II/template-arguments in your build directory). +It is those .inst files that are eventually included from the +corresponding .cc files.

    Defensive programming

    -- 2.39.5