Now that the <cassert> include has been removed from the debug mode includes,
the question that immediately comes to mind is: should we throw instead of
assert?
Advantages:
1) in the testsuite, we could check for the proper exception, instead of
xfailing on the expected abort call. This would also be possible in user code.
2) verbose terminate handler would print out all the info that stdout gets now.
Something to think about.
--
Summary: should debug mode throw instead of assert?
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: bkoz at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23888
