IteratorRange is a cheap, throwaway container to implement support for
range-based for loops if the underlying containers doesn't provide
standard begin() / end () methods.

Test (almost) all methods requested by the STL
(as documented on http://www.cplusplus.com/reference/iterator/ForwardIterator/ )

Test whether std::iterator_traits is properly specialized.

Andreas Nüßing authored 10 years ago and Christoph Grüninger committed 10 years ago

When creating a project and generating the config.h.cmake file, duneproject
surrounds the inserted text with {begin,end} $NAME. $NAME is set to $PROJECT
without a leading "dune[-_]" and $PROJECT is the module name specified by the
user (e.g. $PROJECT==dune-grid, $NAME==grid).
When DuneMacro.cmake generates the config.h.cmake for the created project in
the build-directory, it searches the config.h.cmake file in the source
directory of the project for {begin,end} $ProjectName which is set to
DUNE_MOD_NAME, which is the module name specified in the corresponding
dune.module file (e.g. dune-grid).
This leads to DuneMacro not finding and therefore ignoring the block in the
source config.h.cmake of the new project.

Gcc 4.6 cannot generate default move constructor for classes containing a
DynamicVector because there is no move constructor and the copy constructor
is non-trivial.
This patch fixes this, by adding move semantics.

If duncontrol detects an installed dune-common module, then it always
assumed that it contains a lib/dunecontrol
subdirectory. Unfortunately, this does not hold for older dune-common
modules and dunecontrol will error out later with a message like

/usr/local/lib/dunecontrol: file not found
Execution of dunecontrol terminated due to errors!

With this commit we fix this by actually checking whether the
lib/dunecontrol subdirectoy exists before adding it to
DUNE_CONTROL_PATH.

Thanks a lot to wuhao sife for reporting this problem.

NDEBUG is undefined (allows to tests asserts without doubling call to all
interface methods).

NDEBUG needs to be undefined and DUNE_INTERFACECHECK needs to be defined
to check the correct implementation of CRT interface methods.

Steffen Persvold authored 10 years ago and Markus Blatt committed 10 years ago

getrusage() is a very expensive system call and involves several
kernel locks. This prevents multithreaded applications from scaling
effectively. Using std:chrono::high_resolution_clock is portable
and very low cost in most cases.

This avoids compiler warning about implicitly rounded to zero

This reverts commit cf4bf4d8.

The epxlicit cast isn't needed anymore as we have a fix for the
ambiguous operator overload.

The bug affected operators: +=, -=, *=, /=. It has been fixed by using:
enable_if<is_convertible<ParamType, FieldVector::valueType>, ...>

This was used for backwards compatibility only.

Complained by autoconf 1.14, cf. FS#1462.
Thanks to Claus for the heads-up.

Like 2a4965d9 for autotools.
Cf. FS#1445

Cf. FS#1461.

The variable is was set and used by dunecontrol but not by duneproject.

It is INCLUDE_DIRECTORIES and not COMPILE_DIRECTORIES.

Previously, parmetis flags were not added as we used PARMETIS_COMPILE_FLAGS
which does not exist. This patch now sets the properties COMPILE_DEFINITIONS
and INCLUDE_DIRECTORIES for the targets and uses the correct values.

Needed to build the documentation only for make doc.
Avoid name clashes by adding MANGLE_TARGET_NAMES.
With CMake 3.0.0 no more warnings are emitted by
building the documentation.

Whitespace changes where necessary to please the git commit hook.

Previously only dune-foo/bar/*/test worked.
Now dune-foo/test works, too.

oelements stores longs which need to be converted to pointers before freeing.
Previously we actually free the entries of the array oelements and not the
stored pointers.

There might be liftime issues with the allocated memory when copying
a pool. Therefore I added a check whether the memory was actually
allocated by the pool when freeing it.

(the problem are operators of the type FieldVector<double,1> *= int)
clang fails and gcc (4.7) warns about
ISO C++ saying that these operators are aambiguous

With g++-4.4 I got the following errors:

fmatrix.hh:106: error: no type named ‘const_iterator’ in ‘class std::initializer_list<std::initializer_list<int> >’

Looking into the header there is indeed the const_iterator (demanded by the standard)
missing. Therefore I refactored the code to use std::copy_n and thus am omitting the iterator
type.

At the same time I made the actual copying safer for the case that the initializer_list
is of different size and people compile with -DNDEBUG. The assertion for the size is still
left in there. Remove the assert or the size computation at your discretion.