See also flyspray/FS#1669

A FieldMatrix can still have a DiagonalMatrix assigned to it through the
new DenseMatrixAssigner specialisation. The restriction from general
DenseMatrix implementations to the FieldMatrix class is removed in the
process.

The functionality is retained in the form of a DenseMatrixAssigner
specialisation, except for C-style matrices.

See also flyspray/FS#1669 and #11

The point of the matter is that posix_memalign() is not allowed in this
context according to the relevant standards, so we use mmap() instad.

`mprotect` can only be used for `mmap`'ed memory

Makes testdebugallocator pass on OS X, too.

See merge request !43

mprotect violations are required to lead to a SIGSEGV on Linux.
OS X is more permissive, allowing for both SIGSEGV and SIGBUS.

And practice, the tests generate a SIGBUS for me, causing the tests to
fail. Confusingly, ctest describes the problem as

  Exception: SegFault

which I assume they use as a catch-all term.

The combination of `posix_memalign` and `mprotect` does not work as
expected on OS X, see also !43.

[Cleanup] Fix GCC warning by properly initializing member



See merge request !41

feature/ use std::is_convertible istead of Dune::Conversion



See merge request !37

Feature/debugstream destructor exception



See merge request !35

C++11 defaults destructors to noexcept.
Good catch, GCC 6!

[CMake] Get rid of deprecated check_cxx_accepts_flag()

The CMake module TestCXXAcceptsFlag and the accompanying function
check_cxx_accepts_flag() have been deprecated since CMake 3.0, the
replacements are CheckCXXCompilerFlag and check_cxx_compiler_flag().

Thanks to Dirk Ribbrock for reporting the problem via email.

See merge request !39

The CMake module TestCXXAcceptsFlag and the accompanying function
check_cxx_accepts_flag() have been deprecated since CMake 3.0, the
replacements are CheckCXXCompilerFlag and check_cxx_compiler_flag().

Thanks to Dirk Ribbrock for reporting the problem via email.

BitSetVector: Add and test bounds checking

See also Flyspray/FS#1030.

See merge request !34

Fix warnings

This addresses warnings about unitialised base classes and superfluous use of the keyword `const`.

See merge request !38

fmatrixtest: Use initializer lists

The old implementation was a kludge that wanted to use initializer lists badly, obviously, but couldn't. Now we can.

Cleanup only, no functional changes.

See merge request !36

This addresses warnings such as

  'const' type qualifier on return type has no effect

Use <array> instead of <dune/common/array>

See also #13.

See merge request !33

[cmake] install boundschecking.hh

Merge request !17 added a new header file boundschecking.hh but forgot to add it to the list of installed headers in CMakeLists.txt.

See merge request !32

[FS#1030] Add, use, and test DUNE_ASSERT_BOUNDS

If `DUNE_CHECK_BOUNDS` is defined, `DUNE_ASSERT_BOUNDS` checks if a condition holds; otherwise, it does nothing. It is meant to be used for conditions that assure writes and reads do not occur outside of memory limits or pre-defined patterns and related conditions.

Replacement for `assert` in relevant context; guarded by a single universal define rather than existing class- or module- specific ones.

See merge request !17

Felix Gruber authored 9 years ago and Christoph Grüninger committed 9 years ago

I still don't understand why, but GCC was spilling deprecation warnings
for Dune::enable_if even if we were only using std::enable_if.

Thus I removed the deprecation of the enable_if struct and only
deprecate the type within. That should still be enough as this
deprecation warning gets triggered when enable_if is used to aid in
overload resolution and the boolean parameter of enable_if is true.

Felix Gruber authored 9 years ago and Christoph Grüninger committed 9 years ago

My previous wrapper implementation around std::enable_if didn't work
when B was false, as type was then defined to a type that was SFINAEd
away.