[multiple changes]
2002-09-13 Andy Felt <afelt@uwsp.edu> * docs/html/17_intro/howto.html: Update link. 2002-09-13 Phil Edwards <pme@gcc.gnu.org> * docs/doxygen/run_doxygen: Massage man page for Iterator_types.3. * docs/html/faq/index.html: Whitespace fixes. From-SVN: r57125
This commit is contained in:
parent
907aee69e2
commit
61e6e65a6a
4 changed files with 29 additions and 19 deletions
|
@ -1,3 +1,12 @@
|
||||||
|
2002-09-13 Andy Felt <afelt@uwsp.edu>
|
||||||
|
|
||||||
|
* docs/html/17_intro/howto.html: Update link.
|
||||||
|
|
||||||
|
2002-09-13 Phil Edwards <pme@gcc.gnu.org>
|
||||||
|
|
||||||
|
* docs/doxygen/run_doxygen: Massage man page for Iterator_types.3.
|
||||||
|
* docs/html/faq/index.html: Whitespace fixes.
|
||||||
|
|
||||||
2002-09-12 Benjamin Kosnik <bkoz@redhat.com>
|
2002-09-12 Benjamin Kosnik <bkoz@redhat.com>
|
||||||
|
|
||||||
* libmath/Makefile.am (LIBTOOL): Use --tag CC always for this
|
* libmath/Makefile.am (LIBTOOL): Use --tag CC always for this
|
||||||
|
|
|
@ -219,7 +219,8 @@ rm stdheader
|
||||||
# implementations of man(1), e.g., Linux's. We need to have another top-level
|
# implementations of man(1), e.g., Linux's. We need to have another top-level
|
||||||
# *roff tag to /stop/ the .SH NAME entry.
|
# *roff tag to /stop/ the .SH NAME entry.
|
||||||
#problematic=`egrep --files-without-match '^\.SH SYNOPSIS' [A-Z]*.3`
|
#problematic=`egrep --files-without-match '^\.SH SYNOPSIS' [A-Z]*.3`
|
||||||
problematic='Containers.3 Sequences.3 Assoc_containers.3 Allocators.3'
|
problematic='Containers.3 Sequences.3 Assoc_containers.3 Allocators.3
|
||||||
|
Iterator_types.3'
|
||||||
for f in $problematic; do
|
for f in $problematic; do
|
||||||
sed '/^\.SH NAME/{
|
sed '/^\.SH NAME/{
|
||||||
n
|
n
|
||||||
|
|
|
@ -158,7 +158,7 @@
|
||||||
<p>For those of you new to ISO C++98, no, that isn't a typo, the headers
|
<p>For those of you new to ISO C++98, no, that isn't a typo, the headers
|
||||||
really have new names. Marshall Cline's C++ FAQ Lite has a good
|
really have new names. Marshall Cline's C++ FAQ Lite has a good
|
||||||
explanation in
|
explanation in
|
||||||
<a href="http://www.cerfnet.com/~mpcline/On-Line-C++-FAQ/coding-standards.html#[25.4]">item [25.4]</a>.
|
<a href="http://www.parashift.com/c++-faq-lite/coding-standards.html#faq-26.4">item [26.4]</a>.
|
||||||
</p>
|
</p>
|
||||||
<p>Return <a href="#top">to top of page</a> or
|
<p>Return <a href="#top">to top of page</a> or
|
||||||
<a href="../faq/index.html">to the FAQ</a>.
|
<a href="../faq/index.html">to the FAQ</a>.
|
||||||
|
|
|
@ -166,8 +166,8 @@
|
||||||
<p>The libstdc++ project is contributed to by several developers
|
<p>The libstdc++ project is contributed to by several developers
|
||||||
all over the world, in the same way as GCC or Linux.
|
all over the world, in the same way as GCC or Linux.
|
||||||
Benjamin Kosnik, Gabriel Dos Reis, Phil Edwards, Ulrich Drepper,
|
Benjamin Kosnik, Gabriel Dos Reis, Phil Edwards, Ulrich Drepper,
|
||||||
Loren James Rittle, and Paolo Carlini are the lead maintainers of
|
Loren James Rittle, and Paolo Carlini are the lead maintainers of
|
||||||
the CVS archive.
|
the CVS archive.
|
||||||
</p>
|
</p>
|
||||||
<p>Development and discussion is held on the libstdc++ mailing
|
<p>Development and discussion is held on the libstdc++ mailing
|
||||||
list. Subscribing to the list, or searching the list
|
list. Subscribing to the list, or searching the list
|
||||||
|
@ -642,8 +642,8 @@ New:
|
||||||
</p>
|
</p>
|
||||||
<p><a name="4_4_iostreamclear"><strong>reopening a stream fails</strong>
|
<p><a name="4_4_iostreamclear"><strong>reopening a stream fails</strong>
|
||||||
</a> Did I just say that -Weffc++ was our biggest false-bug report?
|
</a> Did I just say that -Weffc++ was our biggest false-bug report?
|
||||||
I lied. (It used to be.) Today it seems to be reports that after
|
I lied. (It used to be.) Today it seems to be reports that after
|
||||||
executing a sequence like
|
executing a sequence like
|
||||||
</p>
|
</p>
|
||||||
<pre>
|
<pre>
|
||||||
#include <fstream>
|
#include <fstream>
|
||||||
|
@ -715,23 +715,23 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
|
||||||
requires a separate patch for libstdc++-v3.
|
requires a separate patch for libstdc++-v3.
|
||||||
</p>
|
</p>
|
||||||
<p><a name="4_4_checks"><strong>concept checks</strong></a>
|
<p><a name="4_4_checks"><strong>concept checks</strong></a>
|
||||||
If you see compilation errors containing messages about
|
If you see compilation errors containing messages about
|
||||||
<code> <em>foo</em>Concept </code>and a<code> constraints </code>
|
<code> <em>foo</em>Concept </code>and a<code> constraints </code>
|
||||||
member function, then most likely you have violated one of the
|
member function, then most likely you have violated one of the
|
||||||
requirements for types used during instantiation of template
|
requirements for types used during instantiation of template
|
||||||
containers and functions. For example, EqualityComparableConcept
|
containers and functions. For example, EqualityComparableConcept
|
||||||
appears if your types must be comparable with == and you have not
|
appears if your types must be comparable with == and you have not
|
||||||
provided this capability (a typo, or wrong visibility, or you
|
provided this capability (a typo, or wrong visibility, or you
|
||||||
just plain forgot, etc).
|
just plain forgot, etc).
|
||||||
</p>
|
</p>
|
||||||
<p>More information, including how to optionally enable/disable the
|
<p>More information, including how to optionally enable/disable the
|
||||||
checks, is available
|
checks, is available
|
||||||
<a href="../19_diagnostics/howto.html#3">here</a>.
|
<a href="../19_diagnostics/howto.html#3">here</a>.
|
||||||
</p>
|
</p>
|
||||||
<p><a name="4_4_dlsym"><strong>dlopen/dlsym</strong></a>
|
<p><a name="4_4_dlsym"><strong>dlopen/dlsym</strong></a>
|
||||||
If you are using the C++ library across dynamically-loaded
|
If you are using the C++ library across dynamically-loaded
|
||||||
objects, make certain that you are passing the correct options
|
objects, make certain that you are passing the correct options
|
||||||
when compiling and linking:
|
when compiling and linking:
|
||||||
</p>
|
</p>
|
||||||
<pre>
|
<pre>
|
||||||
// compile the library components
|
// compile the library components
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue