Re: [libstdc++ PATCH] libstdc++ debug mode (fourth try)

[Doug Gregor <dgregor at apple dot com>]

Here's v5, which incorporates the requested changes with one exception: 
I have removed this sentence that you had added:

 "In addition, it should be possible to use both debug mode and release 
mode standard library entities in one translation unit."

Each translation unit is compiled in either debug mode or release mode. 
There's no way to mix them in a single translation unit.

Tested on i686-pc-linux-gnu and powerpc-apple-darwin; no new 
regressions in either debug or release mode.

	Doug

Attachment: debugmode-v5.ChangeLog
Description: Binary data

Attachment: debugmode-v5.patch.gz
Description: GNU Zip compressed data

On Tuesday, August 5, 2003, at 8:22AM, Benjamin Kosnik wrote:
> - some documentation tweaks, see attached
>
> - safe_iterator.tcc copyright info needs to match other files
>
> - _GLIBCXX_STRINGIFY used once, please consolidate and remove
>
> - _GLIBCXX_RELEASE_CLASS(Name) (and similarly _GLIBCXX_DEBUG_CLASS) can
> incorporate the Name, removing duplication, please change to
>
> #  define _GLIBCXX_RELEASE_CLASS(_N) 
> __attribute__((__link_name__(#_N))) _N
>
> - replace _GLIBCXX_DEBUG_NAMESPACE_CLOSE with }, kill the macro
>
> - change
>
> #  define _GLIBCXX_DEBUG_NAMESPACE_OPEN(_Ns) namespace __gnu_debug {
>
> to
>
> #  define _GLIBCXX_NAMESPACE_DEBUG(_Ns) __gnu_debug
>
> and modify the code to be
>
> namespace _GLIBCXX_NAMESPACE_DEBUG
> {
>
> - for include/debug/vector, can't you just use a using declaration
> instead of re-defining vector in namespace __gnu_debug (and we'll just
> say in the docs that __gnu_debug::vector cannot be specialized?)
>
> -benjamin
>
>
> <p.20030805-1>