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 core/dune-common#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.

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

Using inheritance for the deprecated wrapper class unfortunately only
worked on GCC, so we had to define the type or value of the type trait
explicitly to deprecate it.

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

Since we cannot deprecate using statements, I changed all using
statements for std type traits into thin wrapper classes that I then
deprecated.

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

This is not needed anymore, as the testet type traits are directly
imported from std:: and can thus be assumed to be correct.

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

Is ConstVolatileTraits still used anywhere? I would propose to
deprecate it and replace it with std::is_volatile, std::is_const,
std::remove_cv, etc.

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

They can be replaced by std::is_base_of, std::is_const and
std::is_volatile, respectively.

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

Now that we require a C++11-compliant compiler, we can use
the std type traits to construct our own.