[Dune] [#1030] Bounds checking

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1030 - Bounds checking
User who did this - Elias Pipping (pipping)

----------
To reiterate:

It would be desirable to integrate optional bounds checking into all
of the above classes.

What could be discussed is the means by which those checks should be
made optional; both with respect to what bounds checking is already in
place and any future additions.

In particular:

(1) Any code that is passed to the function or macro assert() is
    automatically guarded by "#ifdef NDEBUG". Is that good enough?
    If so, all we need to do for the above-mentioned classes is add
    assert() to four places; the other four can stay the way they are
    If not, we ll have to decide on a define that should guard bounds
    checking.

(2) Do we want per-class defines like DUNE_FMatrix_WITH_CHECKING?

(3) Do we want per-module defines like DUNE_ISTL_WITH_CHECKING?

(4) Assuming we decide again (1), (2), and (3) and decide on
    e.g. DUNE_WITH_CHECKING, should assertions still use assert() and
    thus be disabled through NDEBUG? Not using assert() would leave
    us with more flexibility.
----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=1030#comment3095

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.