<li> If we can not enumerate all possible template arguments (e.g., vector
types -- because users might want to define their own vector kinds) but at
least know a few common usage cases, then the function is put into a
-<code>.templates.h</code> file. We #include it into the <code>.cc</code> file
+<code>.templates.h</code> file. We \#include it into the <code>.cc</code> file
and instantiate the functions for all of the common arguments. For almost all
users, this will be just fine -- they only use the (vector, matrix, ...) types
we already instantiate, and for them the <code>.templates.h</code> file will not
be of any interest. It will also not slow down their compilations because
-nothing they see will #include the <code>.templates.h</code> file. But users who
+nothing they see will \#include the <code>.templates.h</code> file. But users who
define their own (vector, matrix, ...) types can instantiate the template
functions with their own user-defined types by including the
<code>.templates.h</code> files.
<li> 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),
the definitions of functions are provided at the bottom of the header
-file with declarations. The definitions should be guarded with <code>#ifndef
-DOXYGEN ... #endif</code> to prevent Doxygen from picking them up.</li>
+file with declarations. The definitions should be guarded with <code>\#ifndef
+DOXYGEN ... \#endif</code> to prevent Doxygen from picking them up.</li>
</ol>
* parallel::distributed::Triangulation .
* </dd>
*
- * @see @ref boundary "The module on boundaries".
- *
*
* <dt class="glossary">@anchor GlossCoarseMesh <b>Coarse mesh</b></dt>
* <dd>
* </dd>
*
*
- * <dt class="glossary">@anchor GlossDimension <b>Dimensions @p dim and @p spacedim</b></dt>
+ * <dt class="glossary">@anchor GlossDimension <b>Dimensions `dim` and `spacedim`</b></dt>
*
* <dd> Many classes and functions in deal.II have two template parameters,
* @p dim and @p spacedim. An example is the basic Triangulation class:
* template <int dim, int spacedim=dim>
* class Triangulation {...};
* @endcode
- * In all of these contexts where you see @p dim and @p spacedim referenced,
+ * In all of these contexts where you see `dim` and `spacedim` referenced,
* these arguments have the following meaning:
*
* <ul>
* access is thus not linear. Furthermore, the support for multi-component
* systems becomes transparent if we provide a <i>start index</i> to every
* single component separately. Thus, the `row_starts` field is of length
- * `n_cell_batches()*VectorizedArray<Number>::size()*n_components`.
+ * `n_cell_batches()*VectorizedArray<Number>::%size()*n_components`.
* </li>
* <li> The translation between components within a system of multiple base
* elements is controlled by the four variables
</p>
<li> <p>
- Improved: <code>PreconditionBlockSOR</code><code
- class="member">::Tvmult(...)</code> is implemented.
+ Improved: <code>PreconditionBlockSOR::Tvmult()</code> is implemented.
<br>
(GK 2000/07/07)
</p>
</p>
<li> <p>
- New: Function <code>VectorTools</code><code
- class="member">::compute_mean_value</code> integrates the mean
- value of one component of a finite element function.
+ New: Function <code>VectorTools::compute_mean_value()</code> integrates
+ the mean value of one component of a finite element function.
<br>
(GK 2000/07/12)
</p>
</p>
<li> <p>
- New: <code>FE*Values::get_quadrature</code>
- returns a reference to the quadrature formula used by a
+ New: <code>FEValues::get_quadrature()</code> and
+ <code>FEFaceValuesBase::get_quadrature()</code>
+ return a reference to the quadrature formula used by a
FEValues object.
<br>
(WB 2001/06/21)
Changed: Previously, we just set the preprocessor variable
<code>DEAL_II_USE_MT</code>, when <code>--with-multithreading</code> was
given as argument to <code>./configure</code>. Tests in the code
- therefore looked like <code>#ifdef DEAL_II_USE_MT</code>. This has been
+ therefore looked like <code>\#ifdef DEAL_II_USE_MT</code>. This has been
changed so that the variable is always defined, but its value is now
equal to <code>1</code>
when multithreading was requested, and zero otherwise. The reason for
conditions, and need not interleave if-else clauses from regular code
and the preprocessor, if conditions involve both the state of this
preprocessor variable and the run-time state of your program. However,
- this change requires that all appearances of <code>#ifdef
- DEAL_II_USE_MT</code> be changed to <code>#if DEAL_II_USE_MT ==
+ this change requires that all appearances of <code>\#ifdef
+ DEAL_II_USE_MT</code> be changed to <code>\#if DEAL_II_USE_MT ==
1</code>, since the variable is now defined unconditionally.
<br>
(WB 2002/11/14)
</p>
<li> <p>
- Fixed: On CygWin, one header files has a <code>#define quad
+ Fixed: On CygWin, one header files has a <code>\#define quad
quad_t</code>. This is annoying, since we have local variables and
member functions with the name <code>quad</code>, and in fact it breaks
compilation on those versions of CygWin that has this. Fortunately, the
</p>
<li> <p> Changed: The class <code
- class="member">Table<2>::fill</code> function, which is also
+ class="member">Table::fill()</code> function, which is also
inherited from the <code>FullMatrix</code> class, used to
work also when the size of the matrix was zero, by simply not copying
something. This led to difficult to detect errors. It is therefore no
class="member">Triangulation<1>::n_quads</code> now returns 0,
instead of throwing an assertion, as before. The same holds for
similar functions like <code
- class="member">Triangulation<dim>::n_hexs</code> that now
+ class="member">Triangulation::n_hexs</code> that now
returns 0 for <code>dim<3</code>.
<br>
(RH 2002/06/14)
elements of a matrix or vector to zero without changing its size, the
recommended way is to use the more obvious notation <code>vector=0</code> and <code>matrix=0</code>. To
reset the elements of a table over arbitrary objects, use
- <code>Table<T>::reset_values()</code>.
+ <code>Table::reset_values()</code>.
<br>
(WB 2004/05/10)
</p>
<li> <p> Moved and changed: The header file
<tt>include/numerics/dof_renumbering.h</tt> has been moved to the
directory <tt>include/dofs</tt>, where it logically
- belongs. Furthermore, the sorting parameter of the function <code>DoFRenumbering</code><code>::component_wise</code> has changed its meaning. See
- the reference documentation for details.
+ belongs. Furthermore, the sorting parameter of the function
+ <code>DoFRenumbering::component_wise()</code> has changed its meaning.
+ See the reference documentation for details.
<br>
(GK 2003/07/03)
</p>
<li> <p>
Fixed: <code
- class="member">DataOutBase<2,3>::write_tecplot</code>
+ class="member">DataOutBase::write_tecplot</code> for dim=2 and spacedim=3
sometimes did not write the variable name <code>z</code> when
only outputting faces of cells. This is now fixed.
<br>
</p>
<li> <p>
- Fixed: <code>DataOutBase<2,3>::write_tecplot_binary</code>
- did not write the <code>z</code> coordinates. This is now
- fixed.
+ Fixed: <code>DataOutBase::write_tecplot_binary()</code> with
+ dim=2 and spacedim=3 did not write the <code>z</code> coordinates.
+ This is now fixed.
<br>
(RH 2005/09/28)
</p>
</p>
<li> <p>Fixed: A local variable in
- <code>TriaAccessor<3,3>::measure</code> was
+ <code>TriaAccessor::measure()</code> was
erroneously marked as static could lead to
wrong results and crashes in multithreaded mode. This is now fixed.
<br>
<li> <p>
Extended: <code >DerivativeApproximation</code> now offers access to the
full tensor of derivatives of orders one, two and three. This
- information can be requested for a single cell by means of the <code>DerivativeApproximation</code><code>::approximate_derivative_tensor</code> function. If the
- norm of this tensor is required later on, the new <code >DerivativeApproximation</code><code>::derivative_norm</code> function can be used. Note, that
- for second order derivatives, this returns the largest eigenvalue
- instead of the Frobenius norm, which is returned by the <code >Tensor<rank_,dim></code><code>::norm</code> function.
+ information can be requested for a single cell by means of the
+ <code>DerivativeApproximation::approximate_derivative_tensor()</code>
+ function. If the norm of this tensor is required later on, the new
+ <code>DerivativeApproximation::derivative_norm()</code> function can be
+ used. Note, that for second order derivatives, this returns the largest
+ eigenvalue instead of the Frobenius norm, which is returned by the
+ <code >Tensor::()norm</code> function.
<br>
(Tobias Leicht 2006/08/03)
</p>
</p>
<li> <p>
- Fixed: <code >Triangulation<dim>::fix_coarsen_flags</code>
+ Fixed: <code >Triangulation::fix_coarsen_flags()</code>
has been modified to allow coarsening in all possible cases. Up
to now, coarsening was forbidden, if the neighbor cell was not refined
but had the <code>refine_flag</code> set, whereas it was allowed, if
</p>
<li> <p>
- New: The <code>GridIn<dim>::read_netcdf(string
- &filename)</code> function reads grids from NetCDF files. The
+ New: The <code>GridIn::read_netcdf()</code> function reads grids from NetCDF files. The
only data format currently supported is the <tt>TAU grid
format</tt>.
<br>
</p>
<li> <p>
- Fixed: The <code>GridIn<dim>::read(filename, format)</code>
+ Fixed: The <code>GridIn::read()</code>
function ran into an exception when called with
<tt>Default</tt> format and a filename which does not include
<tt>/</tt>. This is now fixed.
(Matthias Maier, 2013/11/20)
</li>
- <li> Changed: when a dealii::Exception is thrown, defer the symbol lookup of the
+ <li> Changed: when a dealii::%Exception is thrown, defer the symbol lookup of the
stack trace to when it is needed. This improves performance if what() is never
called.
<br>
<li> Changed: The project configuration no longer exports
<code>[...]/include/deal.II</code>. Thus it is now mandatory to prefix
all includes of deal.II headers with <code>deal.II/</code>, i.e.
- <code>#include <deal.II/[...]></code>.
+ <code>\#include <deal.II/[...]></code>.
<br>
(Matthias Maier, 2015/01/19)
</li>
classes. You should use the versions with a VectorOperation
argument instead.
- Vector::scale.
- - TrilinosWrappers::*Vector*::compress with an Epetra_CombineMode
+ - TrilinosWrappers::*Vector*::%compress with an Epetra_CombineMode
argument.
- SparsityPattern and ChunkSparsityPattern functions that take an
<code>optimize_diagonal</code> argument.
(Wolfgang Bangerth, 2015/01/16)
</li>
- <li> New: dealii::multithread_info.n_cpus returns the correct number of CPU
+ <li> New: MultithreadInfo::n_cpus() returns the correct number of CPU
on FreeBSD.
<br>
(Bruno Turcksin, 2015/01/14)
inconvenience this causes.
</p>
-<ol>
-
-</ol>
-
<!-- ----------- GENERAL IMPROVEMENTS ----------------- -->
<a name="general"></a>
<h3>General</h3>
-<ol>
-
-</ol>
-
<!-- ----------- SPECIFIC IMPROVEMENTS ----------------- -->
which returns the buffer of the packed data.
parallel::distributed::Triangulation::notify_ready_to_unpack()
requires `std::function<void(const cell_iterator &, const CellStatus,
- const boost::iterator_range<std::vector<char>::const_iterator &>`, where
+ const boost::iterator_range<std::vector<char>::%const_iterator &>`, where
the last argument describes an iterator range, from which the callback
function is allowed to read.
<br>