This is the mail archive of the
mailing list for the libstdc++ project.
Re: [patch] Remove invalid test on non-const empty strings
Jonathan Wakely wrote:
Debug mode was written to the letter of the standard, not including anyI think this is an "obvious" but at same time crucial observation, in
v3 extensions. IMHO this makes it very useful, in the same way as
-ansi -pedantic, for checking you haven't made any assumptions that
aren't guaranteed by the standard.
the concepts of "regression testsuite" and of "debug-mode" are *different*.
The first one, as we already discussed, serves the purpose of avoiding
and point out as soon as possible (unexpected) changes of behavior, very
beyond what the standard says. Indeed, very often, in the compiler area
in the library area, fixes and improvements are accompanied by tweaks to
testcases, if only to change expected error messages. This is ok, from
testsuite point of view.
Therefore, all in all, I believe it's a mistake trying at any cost to
obtain a clean
regression testsuite in debug mode. At the very least we should think more
about the issue and the real meaning of the two concepts.
In my opinion, our attitude as C++ runtime library writers should be not
different than the attitude of normal users, wrt "debug-mode": an useful
find non-portable assumptions and real errors in our code, nothing less,
more. In particular, should not change the way we write regression tests.