Commit 6f8b5e0c by Jonathan Wakely Committed by Jonathan Wakely

faq.xml (faq): Refer to clauses instead of chapters.

	* doc/xml/faq.xml (faq): Refer to clauses instead of chapters.
	* doc/xml/manual/appendix_contributing.xml (contrib.design_notes):
	Likewise.
	* doc/xml/manual/backwards_compatibility.xml (backwards.third):
	Likewise.
	* doc/xml/manual/test.xml (test.organization.layout): Likewise.

From-SVN: r208873
parent 25d24c42
...@@ -2,6 +2,13 @@ ...@@ -2,6 +2,13 @@
* doc/xml/manual/io.xml (std.io.objects): Additional markup. * doc/xml/manual/io.xml (std.io.objects): Additional markup.
* doc/xml/faq.xml (faq): Refer to clauses instead of chapters.
* doc/xml/manual/appendix_contributing.xml (contrib.design_notes):
Likewise.
* doc/xml/manual/backwards_compatibility.xml (backwards.third):
Likewise.
* doc/xml/manual/test.xml (test.organization.layout): Likewise.
2014-03-27 Jonathan Wakely <jwakely@redhat.com> 2014-03-27 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/60612 PR libstdc++/60612
......
...@@ -32,7 +32,7 @@ ...@@ -32,7 +32,7 @@
<para> <para>
The GNU Standard C++ Library v3 is an ongoing project to The GNU Standard C++ Library v3 is an ongoing project to
implement the ISO 14882 Standard C++ library as described in implement the ISO 14882 Standard C++ library as described in
chapters 17 through 27 and annex D. For those who want to see clauses 17 through 27 and annex D. For those who want to see
exactly how far the project has come, or just want the latest exactly how far the project has come, or just want the latest
bleeding-edge code, the up-to-date source is available over bleeding-edge code, the up-to-date source is available over
anonymous SVN, and can even be browsed over anonymous SVN, and can even be browsed over
......
...@@ -1113,7 +1113,7 @@ indicate a place that may require attention for multi-thread safety. ...@@ -1113,7 +1113,7 @@ indicate a place that may require attention for multi-thread safety.
Fixing these cases will require an audit of all inline functions Fixing these cases will require an audit of all inline functions
defined in the library to determine which merit inlining, and moving defined in the library to determine which merit inlining, and moving
the rest out of line. This is an issue mainly in chapters 23, 25, and the rest out of line. This is an issue mainly in clauses 23, 25, and
27. Of course it can be done incrementally, and we should generally 27. Of course it can be done incrementally, and we should generally
accept patches that move large functions out of line and into ".tcc" accept patches that move large functions out of line and into ".tcc"
files, which can later be pulled into a repository. Compiler/linker files, which can later be pulled into a repository. Compiler/linker
...@@ -1327,7 +1327,7 @@ indicate a place that may require attention for multi-thread safety. ...@@ -1327,7 +1327,7 @@ indicate a place that may require attention for multi-thread safety.
must be replaced with something more rationally behaved.) must be replaced with something more rationally behaved.)
All the C headers need the treatment above; in the standard these All the C headers need the treatment above; in the standard these
headers are mentioned in various chapters. Below, I have only headers are mentioned in various clauses. Below, I have only
mentioned those that present interesting implementation issues. mentioned those that present interesting implementation issues.
The components identified as "mostly complete", below, have not been The components identified as "mostly complete", below, have not been
...@@ -1456,7 +1456,7 @@ indicate a place that may require attention for multi-thread safety. ...@@ -1456,7 +1456,7 @@ indicate a place that may require attention for multi-thread safety.
files to improve link-time behavior is extremely unsatisfactory, files to improve link-time behavior is extremely unsatisfactory,
literally tripling library-build time with no commensurate improvement literally tripling library-build time with no commensurate improvement
in static program link sizes. It must be redone. (Similar work is in static program link sizes. It must be redone. (Similar work is
needed for some components in chapters 22 and 27.) needed for some components in clauses 22 and 27.)
Other work needed for strings is MT-safety, as discussed under the Other work needed for strings is MT-safety, as discussed under the
chapter 20 heading. chapter 20 heading.
......
...@@ -588,7 +588,7 @@ libstdc++-v3. ...@@ -588,7 +588,7 @@ libstdc++-v3.
</para> </para>
<para>The subset commonly known as the Standard Template Library <para>The subset commonly known as the Standard Template Library
(chapters 23 through 25, mostly) is adapted from the final release (clauses 23 through 25, mostly) is adapted from the final release
of the SGI STL (version 3.3), with extensive changes. of the SGI STL (version 3.3), with extensive changes.
</para> </para>
......
...@@ -28,7 +28,7 @@ regressions, ABI, and performance. ...@@ -28,7 +28,7 @@ regressions, ABI, and performance.
<para> <para>
The directory <emphasis>libsrcdir/testsuite</emphasis> contains the The directory <emphasis>libsrcdir/testsuite</emphasis> contains the
individual test cases organized in sub-directories corresponding to individual test cases organized in sub-directories corresponding to
chapters of the C++ standard (detailed below), the dejagnu test clauses of the C++ standard (detailed below), the dejagnu test
harness support files, and sources to various testsuite utilities harness support files, and sources to various testsuite utilities
that are packaged in a separate testing library. that are packaged in a separate testing library.
</para> </para>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment