The information has been provided by the MatrixDimensions struct since roughly the end of 2010.
Correspondingly, the methods rowdim and coldim have been removed from the istl matrix implementations.
Apparently, we forgot to remove them from the Matrix class.

This patch fixes the errornous commits
e8d16384
1a2f4d0f

The introduced range checks were plain wring, as they neglected the nested structure of the
BlockVector. We now use `b.dim()` to get the flat size.

This fixes flyspray/FS#1724.

The standard leaves (the effect of instantiating) complex<T> for more
general T unspecified.

This includes the behaviour of its rows, thus the
CompressedBlockVectorWindow class

I already wanted to use those when implementing the UMFPack
integration into the overlapping schwarz, but our compiler
requirements were not sufficient at the time.

Apparently, this has been rotting away for quite some time. Adapt the
calls to the Pardiso library. Use the C instead of the Fortran interface.
Use correct method for determining the block size of the matrix.

Bug introduced in the fix of flyspray/FS#1331 and !2
revealed my `make build_tests`.

Some exceptions were caught and did not fail the test.

If somebody tries to use pardiso despite it not being found,
he should ge t a linker error instead of an exception.
All other bindings handle it that way.

Fixed flyspray/FS#351

There are some tests, which are hard to port in the paamg directory.
They want to explicitly test _without_ direct solver. Previously,
you simply did not add the flags for the direct solver packages.
add_dune_test relies on all flags, so we need a way to disable components
again. That will be implemented as part of dune_add_executable. For
now, we build the targets ourselves and hand them to dune_add_test.

This partially fixes FS#1724.

Similar to commit e8d16384 which
added the same for UMFPack.
This avoids strange bugs when using the setSubMatrix method: that method
automatically removes rows and columns from the matrix, and expects
_the user_ to do the same for the x and b vectors.

There are some tests, which are hard to port in the paamg directory.
They want to explicitly test _without_ direct solver. Previously,
you simply did not add the flags for the direct solver packages.
add_dune_test relies on all flags, so we need a way to disable components
again. That will be implemented as part of dune_add_executable. For
now, we build the targets ourselves and hand them to dune_add_test.

These header are no longer used.

This avoids strange bugs when using the setSubMatrix method: that method
automatically removes rows and columns from the matrix, and expects _the user_
to do the same for the x and b vectors.

This a littel more natural then int. Furthermore it allows
to use the index constants from dune-typetree.

This a littel more natural then int. Furthermore it allows
to use the index constants from dune-typetree.

In commit 3e405a0b a parameter 'eps'
was introduced for testAggregate(). However this parameter is not
supplied in the call (breaking the test) and it is never used
in the method.

Boost is no longer needed in dune-istl.