Re: Whats happening without _GLIBCXX_ASSERT in testsuite?

[Benjamin Kosnik <bkoz at redhat dot com>]

> I apologise. Re-reading this mail and that mail, I now see my confusion 
> was that I believed that the "test" variable method was supposed to be a 
> valid method of running the existing testsuite and getting back success 
> / failure, instead of providing a method (now depricated) in which the 
> testsuite could be written (taking notice of the value "test" takes). 
> I'll try to pay more attention in future.

Don't worry about it. 

Like Paolo, I think this macro has outlived its usefulness. 

Back in the stone age, we used this technique to set breakpoints on
huge testsuite files. Now that we have more reasonable test files, this
is really not useful, and _GLIBCXX_ASSERT could just be removed, and
replaced with assert, without the bool test variable.

If you want to remove all of these uses, go ahead. Let's do it all at once though.

best,
-benjamin