This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
[libstdc++] GLIBCPP -> GLIBCXX in docs
- From: Phil Edwards <phil at jaj dot com>
- To: libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Mon, 28 Jul 2003 00:14:36 -0400
- Subject: [libstdc++] GLIBCPP -> GLIBCXX in docs
The one part of the rename that hadn't been done yet.
2003-07-28 Phil Edwards <pme@gcc.gnu.org>
* docs/doxygen/user.cfg.in, docs/html/abi.txt, docs/html/debug.html,
docs/html/test.html, docs/html/17_intro/headers_cc.txt,
docs/html/17_intro/howto.html, docs/html/ext/howto.html: Change
GLIBCPP to GLIBCXX (and explain as needed).
Index: docs/doxygen/user.cfg.in
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/doxygen/user.cfg.in,v
retrieving revision 1.25
diff -u -3 -p -r1.25 user.cfg.in
--- docs/doxygen/user.cfg.in 30 May 2003 19:12:55 -0000 1.25
+++ docs/doxygen/user.cfg.in 28 Jul 2003 04:12:16 -0000
@@ -869,13 +869,13 @@ INCLUDE_FILE_PATTERNS =
### The class_requires macros are kludges because SKIP_FUNCTION_MACROS is
### completely broken, and the presence of the macros confuses the parser.
-PREDEFINED = _GLIBCPP_DEPRECATED \
- _GLIBCPP_USE_WCHAR_T \
- _GLIBCPP_USE_LONG_LONG \
- __glibcpp_class_requires="//" \
- __glibcpp_class_requires2="//" \
- __glibcpp_class_requires3="//" \
- __glibcpp_class_requires4="//"
+PREDEFINED = _GLIBCXX_DEPRECATED \
+ _GLIBCXX_USE_WCHAR_T \
+ _GLIBCXX_USE_LONG_LONG \
+ __glibcxx_class_requires="//" \
+ __glibcxx_class_requires2="//" \
+ __glibcxx_class_requires3="//" \
+ __glibcxx_class_requires4="//"
# If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then
# this tag can be used to specify a list of macro names that should be expanded.
Index: docs/html/abi.txt
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/abi.txt,v
retrieving revision 1.8
diff -u -3 -p -r1.8 abi.txt
--- docs/html/abi.txt 15 Oct 2002 04:22:11 -0000 1.8
+++ docs/html/abi.txt 28 Jul 2003 04:12:16 -0000
@@ -108,8 +108,8 @@ I. What is an ABI? What's covered? What'
gcc-3.2.x: 102
- - Incremental bumping of a library pre-defined macro,
- __GLIBCPP__. This macro is defined as the date the library was
+ - Incremental bumping of a library pre-defined macro, __GLIBCPP__ or
+ __GLIBCXX__. This macro is defined as the date the library was
released, in compressed ISO date format, as an unsigned long.
This macro is defined in the file "c++config" in the
@@ -130,7 +130,7 @@ I. What is an ABI? What's covered? What'
- Incremental bumping of a library pre-defined macro,
_GLIBCPP_VERSION. This macro is defined as the released version of
the library, as a string literal. This is only implemented in
- gcc-3.1.0 releases and higher.
+ gcc-3.1.0 releases and higher, and changed to _GLIBCXX_VERSION in 3.4.
This macro is defined in the file "c++config" in the
"libstdc++-v3/include/bits" directory and is generated
@@ -200,7 +200,7 @@ I. What is an ABI? What's covered? What'
--enable-symvers.
In particular, libstdc++-v3/acinclude.m4 has a macro called
- GLIBCPP_ENABLE_SYMVERS that defaults to yes (or the argument passed
+ GLIBCXX_ENABLE_SYMVERS that defaults to yes (or the argument passed
in via --enable-symvers=foo). At that point, the macro attempts to
make sure that all the requirement for symbol versioning are in
place. For more information, please consult acinclude.m4.
Index: docs/html/debug.html
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/debug.html,v
retrieving revision 1.3
diff -u -3 -p -r1.3 debug.html
--- docs/html/debug.html 13 Mar 2003 00:15:59 -0000 1.3
+++ docs/html/debug.html 28 Jul 2003 04:12:16 -0000
@@ -105,7 +105,7 @@
there are different kinds of allocation schemes that can be used by
<code> std::allocator </code>. For implementation details, see this
<a href="ext/howto.html#3"> document</a> and look specifically for
- <code>GLIBCPP_FORCE_NEW</code>.
+ <code>GLIBCXX_FORCE_NEW</code>.
</p>
<p>In a nutshell, the default allocator used by <code>
@@ -120,7 +120,7 @@
C++ tools: the first that can do this is valgrind 1.0.4, but later
versions should work at least as well. Second of all, use a
completely unoptimized build to avoid confusing valgrind. Third,
- use GLIBCPP_FORCE_NEW to keep extraneous pool allocation noise from
+ use GLIBCXX_FORCE_NEW to keep extraneous pool allocation noise from
cluttering debug information.
</p>
Index: docs/html/test.html
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/test.html,v
retrieving revision 1.3
diff -u -3 -p -r1.3 test.html
--- docs/html/test.html 24 Jun 2003 20:33:29 -0000 1.3
+++ docs/html/test.html 28 Jul 2003 04:12:16 -0000
@@ -451,7 +451,7 @@ Example 4: Testing for compilation error
<em>testsuite_wchar_t </em>
<p> This file indicates that the host system can run the wchar_t
tests, and corresponds to the macro definition <code>
- _GLIBCPP_USE_WCHAR_T</code> in the file c++config.h.
+ _GLIBCXX_USE_WCHAR_T</code> in the file c++config.h.
</p>
</li>
</ul>
Index: docs/html/17_intro/headers_cc.txt
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/17_intro/headers_cc.txt,v
retrieving revision 1.2
diff -u -3 -p -r1.2 headers_cc.txt
--- docs/html/17_intro/headers_cc.txt 15 Sep 2001 00:41:10 -0000 1.2
+++ docs/html/17_intro/headers_cc.txt 28 Jul 2003 04:12:16 -0000
@@ -75,7 +75,7 @@
// "C" headers that might not work if wchar_t support is disabled.
#include <bits/c++config.h>
-#if _GLIBCPP_USE_WCHAR_T
+#if _GLIBCXX_USE_WCHAR_T
#include <cwchar>
#include <cwctype>
#endif
Index: docs/html/17_intro/howto.html
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/17_intro/howto.html,v
retrieving revision 1.29
diff -u -3 -p -r1.29 howto.html
--- docs/html/17_intro/howto.html 24 Apr 2003 20:39:49 -0000 1.29
+++ docs/html/17_intro/howto.html 28 Jul 2003 04:12:16 -0000
@@ -291,7 +291,8 @@
<a href="../configopts.html">the configuration step</a>, with the
various --enable/--disable choices being translated to #define/#undef).
</p>
- <p>All library macros begin with <code>_GLIBCPP_</code>. The fact that
+ <p>All library macros begin with <code>_GLIBCPP_</code> in earlier
+ versions, and <code>_GLIBCXX_</code> in later versions. The fact that
these symbols start with a leading underscore should give you a clue
that (by default) they aren't meant to be changed by the user. :-)
</p>
@@ -310,9 +311,10 @@
The default state of the symbol is listed. "Configurable"
(or "Not configurable") means that the symbol is initially
chosen (or not) based on --enable/--disable options at configure time.
+ For 3.1 through 3.3, the prefixes are <code>_GLIBCPP_</code>.
</p>
<dl>
- <dt><code>_GLIBCPP_DEPRECATED</code></dt>
+ <dt><code>_GLIBCXX_DEPRECATED</code></dt>
<dd>Undefined by default. Not configurable. Turning this on enables
older ARM-style iostreams code, and other anachronisms. This may be
useful in updating old C++ programs which no longer meet the
@@ -331,7 +333,7 @@
you might try undefining this macro.
</dd>
-->
- <dt><code>_GLIBCPP_CONCEPT_CHECKS</code></dt>
+ <dt><code>_GLIBCXX_CONCEPT_CHECKS</code></dt>
<dd>Undefined by default. Configurable. When defined, performs
compile-time checking on certain template instantiations to detect
violations of the requirements of the standard. This is described
Index: docs/html/ext/howto.html
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/ext/howto.html,v
retrieving revision 1.32
diff -u -3 -p -r1.32 howto.html
--- docs/html/ext/howto.html 16 Jul 2003 17:06:35 -0000 1.32
+++ docs/html/ext/howto.html 28 Jul 2003 04:12:17 -0000
@@ -414,7 +414,7 @@
<p>
If a DR is not listed here, we may simply not have gotten to it yet;
feel free to submit a patch. Search the include/bits and src
- directories for appearances of _GLIBCPP_RESOLVE_LIB_DEFECTS for
+ directories for appearances of _GLIBCXX_RESOLVE_LIB_DEFECTS for
examples of style. Note that we usually do not make changes to the code
until an issue has reached <a href="lwg-active.html#DR">DR</a> status.
</p>