From: Wolfgang Bangerth
Date: Sat, 9 May 2015 03:10:12 +0000 (-0500)
Subject: Also add a changelog entry.
X-Git-Tag: v8.3.0-rc1~184^2~4
X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=642a398f5a70b2d953f3a7931fd4b1e39c3428c6;p=dealii.git
Also add a changelog entry.
---
diff --git a/doc/news/changes.h b/doc/news/changes.h
index bd42faa46d..aee4e94d26 100644
--- a/doc/news/changes.h
+++ b/doc/news/changes.h
@@ -38,6 +38,27 @@ inconvenience this causes.
+ - Changed: Functions such as FEValuesBase::get_function_values() that
+ extracted the values of functions at the quadrature points of a cell
+ implicitly always assumed that
double
is a reasonable
+ type to store the result in. This, however, is not true if the solution
+ vector's underlying scalar type was, for example,
+ std::complex@
. All of the functions of
+ FEValuesBase as well as of the various FEValuesViews class that extract
+ values from solution vectors have been changed so that they now return
+ their results in vectors that use the same underlying scalar type
+ (float, double, or std::complex) as was used in the solution vector.
+
+ Most user codes will be entirely unaffected by this because they simply
+ use the default vector types which all store their data as doubles.
+ You may have to adjust your code, though, if you use non-standard
+ types such as Vector@ for solution vectors, or use
+ complex-valued data types. This includes compiling PETSc with
+ complex scalars.
+
+ (David Davydov, 2015/05/08)
+
+
- Removed: The generic, templated vmult, Tvmult, etc. -interfaces of
LAPACKFullMatrix - they were never implemented.