* producing a <i>set of flags</i> amounts to setting multiple bits
* in an integer, which is facilitated using the operation
* <code>update_gradients | update_JxW_values</code> (in other words, and
- * maybe slightly confusingly so, the operation "this operation <i>and</i> that
- * operation" is represented by the expression "single-bit-in-an-integer-for-this-operation
- * <i>binary-or</i> single-bit-in-an-integer-for-that-operation"). To
+ * maybe slightly confusingly so, the operation @"this operation <i>and</i> that
+ * operation@" is represented by the expression @"single-bit-in-an-integer-for-this-operation
+ * <i>binary-or</i> single-bit-in-an-integer-for-that-operation@"). To
* make operations cheaper, FEValues and the mapping and finite element objects
* it depends on really only compute those pieces of information that you
* have specified in the update flags (plus some information necessary to
<li> Removed: The constructor of the Utilities::MPI::MPI_InitFinalize
class used to interpret a last argument equal to numbers::invalid_unsigned_int
- as "<i>create as many threads as there are processor cores on the current
- system</i>" for each MPI process. If there were multiple MPI processes on a
+ as @"<i>create as many threads as there are processor cores on the current
+ system</i>@" for each MPI process. If there were multiple MPI processes on a
given node, this would lead to (sometimes massive) overallocation of resources
because <i>every</i> MPI process would create as many threads as there are cores.
This has now been changed: an argument equal to numbers::invalid_unsigned_int
- is now interpreted as "<i>subdivide the available cores between all MPI
+ is now interpreted as @"<i>subdivide the available cores between all MPI
processes running on the current system and let each process create as many
- threads as cores were allocated to it</i>".
+ threads as cores were allocated to it</i>@".
<br>
(Wolfgang Bangerth, 2014/09/16)
</li>