With this patch it is possible to request CMake for building
by setting USE_CMAKE=yes in an option file.

In one of the latest patches I introduced a bug which caused
the --builddir option of dunecontrol to not make any effect.
This patch fixes this.

There is no obvious reason to quote one variable and not the other.
If more CMP0019 warnings are found, they have to be fixed in the same
way.
This was only an issue with CMake 2.8.11 or newer.

Because C++11 implements this differently, and we now have an
stl-compliant implementation to switch to.

I would deprecate isPointer and isReference too, but I can't find
a way to do it.

These are replacements for TypeTraits::isPointer, TypeTraits::isReference,
TypeTraits::PointeeType.  They reimplement what is available in the
C++11 standard library, and are expected to supersede the TypeTraits
class eventually.

Note: this patch does not pull in the corresponding stl implementation.

That's easier to maintain.

This fixes the parsing of git config options.
Be aware that you can use shell code in these options!
Thanks to Steffen Müthig for this fix!

If not found, our own fallback implementation will be used.

A previous commit introduced a check whether the element to-be-touched
is actually contained in the container.  That patch caused the test
to fail.  The new patch fixes this.

The two classes PushBackTuple and PushFrontTuple are both implemented
using a long list of template specializations.  This makes for a lot
of code, and it also limits the maximum tuple size that can be used.
Using variadic templates (FYI: available since gcc-4.3) instead
allows a generic implementation in only a few lines of code, and
only the compiler being the upper limit on tuple size.

An implementation using variadic templates has already been given
in the documentation of PushBackTuple/PushFrontTuple.  This patch
starts to actually use that implementation, provided that
HAVE_VARIADIC_TEMPLATES is set.  Otherwise the old implementation
is used.

MPICH has stepped up its versioning scheme, jumping from MPICH2 1.x
to MPICH 3.x, but has stayed compatible to the older MPICH2 versions.
Unfortunately, the macro MPICH2_VERSION used by mpi_config.m4 to detect
the package has been renamed to MPICH_VERSION.

This patch fixes the problem by adding a separate test for MPICH_VERSION
ana making sure that the macro starts with the letter "3".

It has been obsolete since Doxygen 1.8.1

Previously a value specified on the command line was always
overwritten by a value set in an options file. This patch
fixes this together with overwriting the build directory with
the default build-cmake when --use-cmake was specified.

Because the latter uses the C++11 standard library naming.

The C++11 standard library offers the functionality of SelectType,
it is, however, called 'conditional'.  This patch adds a copy
of our SelectType implementation with the class names changed
to match the ones used in C++11.  The old SelectType implementation
gets deprecated.

This fixes FS#1324.
Thanks to Arne Morten Kvarving for the patch.

The default constructor of the FieldVector has intentionally avoided calling a
constructor for the contained data to eliminate the potential overhead of that
initialization.
During implementation of a new creation mode of the BCRSMatrix, it was discovered
that this behavior is problematic due to its inconsistency: If the data type
contained in the FieldVector is a non-trivial type, a default-constructed
FieldVector will be fully initialized. On the other hand, with a primitive data
type it will be in an uninitialized state, potentially causing undefined behavior.

As this behavior might be very unintuitive for users and made implementing the new,
more efficient creation method for the BCRS matrix very difficult to implement, this
patch changes the FieldVector default constructor to always default-construct its
contents regardless of its type. While this change does introduce a possible
performance regression (for primitive types, the compiler now has to zero out the
memory), the overhead has been measured to be minimal.

The actual implementation prefers to use the new C++11 unified initialization
syntax and falls back to std::fill for older compilers. The distinction was made
because newer compilers generate much more efficient code when using unified
initialization, and for user-defined types, this approach avoids first calling the
default constructors and then the copy assignment operator.