1 <section xmlns="http://docbook.org/ns/docbook" version="5.0"
2 xml:id="appendix.porting.doc" xreflabel="Documentation Hacking">
3 <?dbhtml filename="documentation_hacking.html"?>
5 <info><title>Writing and Generating Documentation</title>
7 <keyword>ISO C++</keyword>
8 <keyword>documentation</keyword>
9 <keyword>style</keyword>
10 <keyword>docbook</keyword>
11 <keyword>doxygen</keyword>
15 <section xml:id="doc.intro">
17 <title>Introduction</title>
20 Documentation for the GNU C++ Library is created from three
21 independent sources: a manual, a FAQ, and an API reference.
24 The sub-directory <filename class="directory">doc</filename>
25 within the main source directory contains
26 <filename>Makefile.am</filename> and
27 <filename>Makefile.in</filename>, which provide rules for
28 generating documentation, described in excruciating detail
29 below. The <filename class="directory">doc</filename>
30 sub-directory also contains three directories: <filename
31 class="directory">doxygen</filename>, which contains scripts and
32 fragments for <command>doxygen</command>, <filename
33 class="directory">html</filename>, which contains an html
34 version of the manual, and <filename
35 class="directory">xml</filename>, which contains an xml version
39 Diverging from established documentation conventions in the rest
40 of the GCC project, libstdc++ does not use Texinfo as a markup
41 language. Instead, Docbook is used to create the manual and the
42 FAQ, and Doxygen is used to construct the API
43 reference. Although divergent, this conforms to the GNU Project
44 recommendations as long as the output is of sufficient quality,
46 <link xmlns:xlink="http://www.w3.org/1999/xlink"
47 xlink:href="http://www.gnu.org/prep/standards/standards.html#Documentation">
52 <section xml:id="doc.generation">
54 <title>Generating Documentation</title>
58 Certain Makefile rules are required by the GNU Coding
59 Standards. These standard rules generate HTML, PDF, XML, or man
60 files. For each of the generative rules, there is an additional
61 install rule that is used to install any generated documentation
62 files into the prescribed installation directory. Files are
63 installed into <filename class="directory">share/doc</filename>
64 or <filename class="directory">share/man</filename> directories.
68 The standard Makefile rules are conditionally supported, based
69 on the results of examining the host environment for
70 prerequisites at configuration time. If requirements are not
71 found, the rule is aliased to a dummy rule that does nothing,
72 and produces no documentation. If the requirements are found,
73 the rule forwards to a private rule that produces the requested
78 For more details on what prerequisites were found and where,
79 please consult the file <filename>config.log</filename> in the
80 libstdc++ build directory. Compare this log to what is expected
81 for the relevant Makefile conditionals:
82 <literal>BUILD_INFO</literal>, <literal>BUILD_XML</literal>,
83 <literal>BUILD_HTML</literal>, <literal>BUILD_MAN</literal>,
84 <literal>BUILD_PDF</literal>, and <literal>BUILD_EPUB</literal>.
88 Supported Makefile rules:
94 <emphasis>make html</emphasis>
97 <emphasis>make install-html</emphasis>
101 Generates multi-page HTML documentation, and installs it
102 in the following directories:
105 <filename>doc/libstdc++/libstdc++-api.html</filename>
108 <filename>doc/libstdc++/libstdc++-manual.html</filename>
115 <emphasis>make pdf</emphasis>
118 <emphasis>make install-pdf</emphasis>
122 Generates indexed PDF documentation, and installs it as
126 <filename>doc/libstdc++/libstdc++-api.pdf</filename>
129 <filename>doc/libstdc++/libstdc++-manual.pdf</filename>
136 <emphasis>make man</emphasis>
139 <emphasis>make install-man</emphasis>
143 Generates man pages, and installs it in the following directory:
146 <filename class="directory">man/man3/</filename>
149 The generated man pages are namespace-qualified, so to look at
150 the man page for <classname>vector</classname>, one would use
151 <command>man std::vector</command>.
158 <emphasis>make epub</emphasis>
161 <emphasis>make install-epub</emphasis>
165 Generates documentation in the ebook/portable electronic
166 reader format called Epub, and installs it as the
170 <filename>doc/libstdc++/libstdc++-manual.epub</filename>
177 <emphasis>make xml</emphasis>
180 <emphasis>make install-xml</emphasis>
184 Generates single-file XML documentation, and installs it
185 as the following files:
188 <filename>doc/libstdc++/libstdc++-api-single.xml</filename>
191 <filename>doc/libstdc++/libstdc++-manual-single.xml</filename>
198 Makefile rules for several other formats are explicitly not
199 supported, and are always aliased to dummy rules. These
200 unsupported formats are: <emphasis>info</emphasis>,
201 <emphasis>ps</emphasis>, and <emphasis>dvi</emphasis>.
205 <section xml:id="doc.doxygen"><info><title>Doxygen</title></info>
207 <section xml:id="doxygen.prereq"><info><title>Prerequisites</title></info>
210 <title>Doxygen Prerequisites</title>
212 <tgroup cols="3" align="center" colsep="1" rowsep="1">
213 <colspec colname="c1"/>
214 <colspec colname="c2"/>
215 <colspec colname="c3"/>
220 <entry>Version</entry>
221 <entry>Required By</entry>
228 <entry>coreutils</entry>
240 <entry>doxygen</entry>
241 <entry>1.7.6.1</entry>
246 <entry>graphviz</entry>
248 <entry>graphical hierarchies</entry>
252 <entry>pdflatex</entry>
253 <entry>2007-59</entry>
254 <entry>pdf output</entry>
263 Prerequisite tools are Bash 2.0 or later,
264 <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.doxygen.org/">Doxygen</link>, and
265 the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.gnu.org/software/coreutils/">GNU
266 coreutils</link>. (GNU versions of find, xargs, and possibly
267 sed and grep are used, just because the GNU versions make
272 To generate the pretty pictures and hierarchy
274 <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.graphviz.org">Graphviz</link> package
275 will need to be installed. For PDF
276 output, <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.tug.org/applications/pdftex/">
277 pdflatex</link> is required.
281 Be warned the PDF file generated via doxygen is extremely
282 large. At last count, the PDF file is over three thousand
283 pages. Generating this document taxes the underlying TeX
284 formatting system, and will require the expansion of TeX's memory
285 capacity. Specifically, the <literal>pool_size</literal>
286 variable in the configuration file <filename>texmf.cnf</filename> may
287 need to be increased by a minimum factor of two.
291 <section xml:id="doxygen.rules"><info><title>Generating the Doxygen Files</title></info>
294 The following Makefile rules run Doxygen to generate HTML
295 docs, XML docs, XML docs as a single file, PDF docs, and the
296 man pages. These rules are not conditional! If the required
297 tools are not found, or are the wrong versions, the rule may
302 <screen><userinput>make doc-html-doxygen</userinput></screen>
306 <screen><userinput>make doc-xml-doxygen</userinput></screen>
310 <screen><userinput>make doc-xml-single-doxygen</userinput></screen>
314 <screen><userinput>make doc-pdf-doxygen</userinput></screen>
318 <screen><userinput>make doc-man-doxygen</userinput></screen>
322 Generated files are output into separate sub directories of
323 <filename class="directory">doc/doxygen/</filename> in the
324 build directory, based on the output format. For instance, the
325 HTML docs will be in <filename class="directory">doc/doxygen/html</filename>.
329 Careful observers will see that the Makefile rules simply call
330 a script from the source tree, <filename>run_doxygen</filename>, which
331 does the actual work of running Doxygen and then (most
332 importantly) massaging the output files. If for some reason
333 you prefer to not go through the Makefile, you can call this
334 script directly. (Start by passing <literal>--help</literal>.)
338 If you wish to tweak the Doxygen settings, do so by editing
339 <filename>doc/doxygen/user.cfg.in</filename>. Notes to fellow
340 library hackers are written in triple-# comments.
345 <section xml:id="doxygen.debug">
346 <info><title>Debugging Generation</title></info>
349 Sometimes, mis-configuration of the pre-requisite tools can
350 lead to errors when attempting to build the
351 documentation. Here are some of the obvious errors, and ways
352 to fix some common issues that may appear quite cryptic.
356 First, if using a rule like <code>make pdf</code>, try to
357 narrow down the scope of the error to either docbook
358 (<code>make doc-pdf-docbook</code>) or doxygen (<code>make
359 doc-pdf-doxygen</code>).
362 Working on the doxygen path only, closely examine the
363 contents of the following build directory:
364 <filename>build/target/libstdc++-v3/doc/doxygen/latex</filename>.
365 Pay attention to three files enclosed within, annotated as follows.
371 <emphasis>refman.tex</emphasis>
375 The actual latex file, or partial latex file. This is generated
376 via <command>doxygen</command>, and is the LaTeX version of the
377 Doxygen XML file <filename>libstdc++-api.xml</filename>. Go to a specific
378 line, and look at the genrated LaTeX, and try to deduce what
379 markup in <filename>libstdc++-api.xml</filename> is causing it.
385 <emphasis>refman.out</emphasis>
389 A log of the compilation of the converted LaTeX form to pdf. This
390 is a linear list, from the beginning of the
391 <filename>refman.tex</filename> file: the last entry of this file
392 should be the end of the LaTeX file. If it is truncated, then you
393 know that the last entry is the last part of the generated LaTeX
394 source file that is valid. Often this file contains an error with
395 a specific line number of <filename>refman.tex</filename> that is
396 incorrect, or will have clues at the end of the file with the dump
397 of the memory usage of LaTeX.
403 If the error at hand is not obvious after examination, a
404 fall-back strategy is to start commenting out the doxygen
405 input sources, which can be found in
406 <filename>doc/doxygen/user.cfg.in</filename>, look for the
407 <literal>INPUT</literal> tag. Start by commenting out whole
408 directories of header files, until the offending header is
409 identified. Then, read the latex log files to try and find
410 surround text, and look for that in the offending header.
415 <section xml:id="doxygen.markup"><info><title>Markup</title></info>
419 In general, libstdc++ files should be formatted according to
420 the rules found in the
421 <link linkend="contrib.coding_style">Coding Standard</link>. Before
422 any doxygen-specific formatting tweaks are made, please try to
423 make sure that the initial formatting is sound.
427 Adding Doxygen markup to a file (informally called
428 <quote>doxygenating</quote>) is very simple. The Doxygen manual can be
430 <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.stack.nl/~dimitri/doxygen/download.html#latestman">here</link>.
431 We try to use a very-recent version of Doxygen.
436 <classname>deque</classname>/<classname>vector</classname>/<classname>list</classname>
437 and <classname>std::pair</classname> as examples. For
438 functions, see their member functions, and the free functions
439 in <filename>stl_algobase.h</filename>. Member functions of
440 other container-like types should read similarly to these
445 Some commentary to accompany
446 the first list in the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.stack.nl/~dimitri/doxygen/manual/docblocks.html">Special
447 Documentation Blocks</link> section of the Doxygen manual:
450 <orderedlist inheritnum="ignore" continuation="restarts">
452 <para>For longer comments, use the Javadoc style...</para>
457 ...not the Qt style. The intermediate *'s are preferred.
463 Use the triple-slash style only for one-line comments (the
464 <quote>brief</quote> mode).
470 This is disgusting. Don't do this.
476 Some specific guidelines:
480 Use the @-style of commands, not the !-style. Please be
481 careful about whitespace in your markup comments. Most of the
482 time it doesn't matter; doxygen absorbs most whitespace, and
483 both HTML and *roff are agnostic about whitespace. However,
484 in <pre> blocks and @code/@endcode sections, spacing can
485 have <quote>interesting</quote> effects.
489 Use either kind of grouping, as
490 appropriate. <filename>doxygroups.cc</filename> exists for this
491 purpose. See <filename>stl_iterator.h</filename> for a good example
492 of the <quote>other</quote> kind of grouping.
496 Please use markup tags like @p and @a when referring to things
497 such as the names of function parameters. Use @e for emphasis
498 when necessary. Use @c to refer to other standard names.
499 (Examples of all these abound in the present code.)
503 Complicated math functions should use the multi-line
504 format. An example from <filename>random.h</filename>:
508 <literallayout class="normal">
510 * @brief A model of a linear congruential random number generator.
513 * x_{i+1}\leftarrow(ax_{i} + c) \bmod m
520 One area of note is the markup required for
521 <literal>@file</literal> markup in header files. Two details
522 are important: for filenames that have the same name in
523 multiple directories, include part of the installed path to
524 disambiguate. For example:
528 <literallayout class="normal">
529 /** @file debug/vector
530 * This file is a GNU debug extension to the Standard C++ Library.
536 The other relevant detail for header files is the use of a
537 libstdc++-specific doxygen alias that helps distinguish
538 between public header files (like <filename>random</filename>)
539 from implementation or private header files (like
540 <filename>bits/c++config.h</filename>.) This alias is spelled
541 <literal>@headername</literal> and can take one or two
542 arguments that detail the public header file or files that
543 should be included to use the contents of the file. All header
544 files that are not intended for direct inclusion must use
545 <literal>headername</literal> in the <literal>file</literal>
550 <literallayout class="normal">
551 /** @file bits/basic_string.h
552 * This is an internal header file, included by other library headers.
553 * Do not attempt to use it directly. @headername{string}
559 Be careful about using certain, special characters when
560 writing Doxygen comments. Single and double quotes, and
561 separators in filenames are two common trouble spots. When in
562 doubt, consult the following table.
566 <title>HTML to Doxygen Markup Comparison</title>
568 <tgroup cols="2" align="left" colsep="1" rowsep="1">
569 <colspec colname="c1"/>
570 <colspec colname="c2"/>
575 <entry>Doxygen</entry>
596 <entry><i></entry>
597 <entry>@a word</entry>
601 <entry><b></entry>
602 <entry>@b word</entry>
606 <entry><code></entry>
607 <entry>@c word</entry>
611 <entry><em></entry>
612 <entry>@a word</entry>
616 <entry><em></entry>
617 <entry><em>two words or more</em></entry>
629 <section xml:id="doc.docbook"><info><title>Docbook</title></info>
632 <section xml:id="docbook.prereq"><info><title>Prerequisites</title></info>
636 <title>Docbook Prerequisites</title>
638 <tgroup cols="3" align="center" colsep="1" rowsep="1">
639 <colspec colname="c1"/>
640 <colspec colname="c2"/>
641 <colspec colname="c3"/>
646 <entry>Version</entry>
647 <entry>Required By</entry>
654 <entry>docbook5-style-xsl</entry>
655 <entry>1.76.1</entry>
660 <entry>xsltproc</entry>
661 <entry>1.1.26</entry>
666 <entry>xmllint</entry>
668 <entry>validation</entry>
672 <entry>dblatex</entry>
674 <entry>pdf output</entry>
678 <entry>pdflatex</entry>
679 <entry>2007-59</entry>
680 <entry>pdf output</entry>
684 <entry>docbook2X</entry>
686 <entry>info output</entry>
690 <entry>epub3 stylesheets</entry>
692 <entry>epub output</entry>
700 Editing the DocBook sources requires an XML editor. Many
701 exist: some notable options
702 include <command>emacs</command>, <application>Kate</application>,
703 or <application>Conglomerate</application>.
707 Some editors support special <quote>XML Validation</quote>
708 modes that can validate the file as it is
709 produced. Recommended is the <command>nXML Mode</command>
710 for <command>emacs</command>.
714 Besides an editor, additional DocBook files and XML tools are
719 Access to the DocBook 5.0 stylesheets and schema is required. The
720 stylesheets are usually packaged by vendor, in something
721 like <filename>docbook5-style-xsl</filename>. To exactly match
722 generated output, please use a version of the stylesheets
724 to <filename>docbook5-style-xsl-1.75.2-3</filename>. The
725 installation directory for this package corresponds to
726 the <literal>XSL_STYLE_DIR</literal>
727 in <filename>doc/Makefile.am</filename> and defaults
728 to <filename class="directory">/usr/share/sgml/docbook/xsl-ns-stylesheets</filename>.
732 For processing XML, an XSLT processor and some style
733 sheets are necessary. Defaults are <command>xsltproc</command>
734 provided by <filename>libxslt</filename>.
738 For validating the XML document, you'll need
739 something like <command>xmllint</command> and access to the
740 relevant DocBook schema. These are provided
741 by a vendor package like <filename>libxml2</filename> and <filename>docbook5-schemas-5.0-4</filename>
745 For PDF output, something that transforms valid Docbook XML to PDF is
746 required. Possible solutions include <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://dblatex.sourceforge.net">dblatex</link>,
747 <command>xmlto</command>, or <command>prince</command>. Of
748 these, <command>dblatex</command> is the default. Other
749 options are listed on the DocBook web <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://wiki.docbook.org/topic/DocBookPublishingTools">pages</link>. Please
750 consult the <email>libstdc++@gcc.gnu.org</email> list when
751 preparing printed manuals for current best practice and
756 For Texinfo output, something that transforms valid Docbook
757 XML to Texinfo is required. The default choice is <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://docbook2x.sourceforge.net/">docbook2X</link>.
761 For epub output, the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://sourceforge.net/projects/docbook/files/epub3/">stylesheets</link> for EPUB3 are required. These stylesheets are still in development. To validate the created file, <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://code.google.com/p/epubcheck/">epubcheck</link> is necessary.
765 <section xml:id="docbook.rules"><info><title>Generating the DocBook Files</title></info>
769 The following Makefile rules generate (in order): an HTML
770 version of all the DocBook documentation, a PDF version of the
771 same, and a single XML document. These rules are not
772 conditional! If the required tools are not found, or are the
773 wrong versions, the rule may end in an error.
777 <screen><userinput>make doc-html-docbook</userinput></screen>
781 <screen><userinput>make doc-pdf-docbook</userinput></screen>
785 <screen><userinput>make doc-xml-single-docbook</userinput></screen>
789 Generated files are output into separate sub directores of
790 <filename class="directory">doc/docbook/</filename> in the
791 build directory, based on the output format. For instance, the
792 HTML docs will be in <filename
793 class="directory">doc/docbook/html</filename>.
797 If the Docbook stylesheets are installed in a custom location,
798 one can use the variable <literal>XSL_STYLE_DIR</literal> to
799 override the Makefile defaults. For example:
804 make <literal>XSL_STYLE_DIR="/usr/share/xml/docbook/stylesheet/nwalsh"</literal> doc-html-docbook
810 <section xml:id="docbook.debug">
811 <info><title>Debugging Generation</title></info>
814 Sometimes, mis-configuration of the pre-requisite tools can
815 lead to errors when attempting to build the
816 documentation. Here are some of the obvious errors, and ways
817 to fix some common issues that may appear quite cryptic.
821 First, if using a rule like <code>make pdf</code>, try to
822 narrow down the scope of the error to either docbook
823 (<code>make doc-pdf-docbook</code>) or doxygen (<code>make
824 doc-pdf-doxygen</code>).
828 Working on the docbook path only, closely examine the
829 contents of the following build directory:
830 <filename>build/target/libstdc++-v3/doc/docbook/latex</filename>.
831 Pay attention to three files enclosed within, annotated as follows.
838 <emphasis>spine.tex</emphasis>
842 The actual latex file, or partial latex file. This is generated
843 via <command>dblatex</command>, and is the LaTeX version of the
844 DocBook XML file <filename>spine.xml</filename>. Go to a specific
845 line, and look at the genrated LaTeX, and try to deduce what
846 markup in <filename>spine.xml</filename> is causing it.
852 <emphasis>spine.out</emphasis>
856 A log of the conversion from the XML form to the LaTeX form. This
857 is a linear list, from the beginning of the
858 <filename>spine.xml</filename> file: the last entry of this file
859 should be the end of the DocBook file. If it is truncated, then
860 you know that the last entry is the last part of the XML source
861 file that is valid. The error is after this point.
868 <emphasis>spine.log</emphasis>
872 A log of the compilation of the converted LaTeX form to pdf. This
873 is a linear list, from the beginning of the
874 <filename>spine.tex</filename> file: the last entry of this file
875 should be the end of the LaTeX file. If it is truncated, then you
876 know that the last entry is the last part of the generated LaTeX
877 source file that is valid. Often this file contains an error with
878 a specific line number of <filename>spine.tex</filename> that is
886 If the error at hand is not obvious after examination, or if one
887 encounters the inscruitable <quote>Incomplete
888 \ifmmode</quote> error, a fall-back strategy is to start
889 commenting out parts of the XML document (regardless of what
890 this does to over-all document validity). Start by
891 commenting out each of the largest parts of the
892 <filename>spine.xml</filename> file, section by section,
893 until the offending section is identified.
899 <section xml:id="docbook.validation"><info><title>Editing and Validation</title></info>
902 After editing the xml sources, please make sure that the XML
903 documentation and markup is still valid. This can be
904 done easily, with the following validation rule:
908 <userinput>make doc-xml-validate-docbook</userinput>
912 This is equivalent to doing:
917 xmllint --noout --valid <filename>xml/index.xml</filename>
922 Please note that individual sections and chapters of the
923 manual can be validated by substituting the file desired for
924 <filename>xml/index.xml</filename> in the command
925 above. Reducing scope in this manner can be helpful when
926 validation on the entire manual fails.
930 All Docbook xml sources should always validate. No excuses!
935 <section xml:id="docbook.examples"><info><title>File Organization and Basics</title></info>
938 <literallayout class="normal">
939 <emphasis>Which files are important</emphasis>
941 All Docbook files are in the directory
944 Inside this directory, the files of importance:
945 spine.xml - index to documentation set
946 manual/spine.xml - index to manual
947 manual/*.xml - individual chapters and sections of the manual
948 faq.xml - index to FAQ
949 api.xml - index to source level / API
951 All *.txml files are template xml files, i.e., otherwise empty files with
952 the correct structure, suitable for filling in with new information.
954 <emphasis>Canonical Writing Style</emphasis>
958 member function template
959 (via C++ Templates, Vandevoorde)
961 class in namespace std: allocator, not std::allocator
963 header file: iostream, not <iostream>
966 <emphasis>General structure</emphasis>
1001 <section xml:id="docbook.markup"><info><title>Markup By Example</title></info>
1005 Complete details on Docbook markup can be found in the DocBook
1007 <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.docbook.org/tdg/en/html/part2.html">online</link>.
1008 An incomplete reference for HTML to Docbook conversion is
1009 detailed in the table below.
1013 <title>HTML to Docbook XML Markup Comparison</title>
1015 <tgroup cols="2" align="left" colsep="1" rowsep="1">
1016 <colspec colname="c1"/>
1017 <colspec colname="c2"/>
1022 <entry>Docbook</entry>
1028 <entry><p></entry>
1029 <entry><para></entry>
1032 <entry><pre></entry>
1033 <entry><computeroutput>, <programlisting>,
1034 <literallayout></entry>
1037 <entry><ul></entry>
1038 <entry><itemizedlist></entry>
1041 <entry><ol></entry>
1042 <entry><orderedlist></entry>
1045 <entry><il></entry>
1046 <entry><listitem></entry>
1049 <entry><dl></entry>
1050 <entry><variablelist></entry>
1053 <entry><dt></entry>
1054 <entry><term></entry>
1057 <entry><dd></entry>
1058 <entry><listitem></entry>
1062 <entry><a href=""></entry>
1063 <entry><ulink url=""></entry>
1066 <entry><code></entry>
1067 <entry><literal>, <programlisting></entry>
1070 <entry><strong></entry>
1071 <entry><emphasis></entry>
1074 <entry><em></entry>
1075 <entry><emphasis></entry>
1079 <entry><quote></entry>
1086 And examples of detailed markup for which there are no real HTML
1087 equivalents are listed in the table below.
1091 <title>Docbook XML Element Use</title>
1093 <tgroup cols="2" align="left" colsep="1" rowsep="1">
1094 <colspec colname="c1"/>
1095 <colspec colname="c2"/>
1099 <entry>Element</entry>
1106 <entry><structname></entry>
1107 <entry><structname>char_traits</structname></entry>
1110 <entry><classname></entry>
1111 <entry><classname>string</classname></entry>
1114 <entry><function></entry>
1116 <para><function>clear()</function></para>
1117 <para><function>fs.clear()</function></para>
1121 <entry><type></entry>
1122 <entry><type>long long</type></entry>
1125 <entry><varname></entry>
1126 <entry><varname>fs</varname></entry>
1129 <entry><literal></entry>
1131 <para><literal>-Weffc++</literal></para>
1132 <para><literal>rel_ops</literal></para>
1136 <entry><constant></entry>
1138 <para><constant>_GNU_SOURCE</constant></para>
1139 <para><constant>3.0</constant></para>
1143 <entry><command></entry>
1144 <entry><command>g++</command></entry>
1147 <entry><errortext></entry>
1148 <entry><errortext>In instantiation of</errortext></entry>
1151 <entry><filename></entry>
1153 <para><filename class="headerfile">ctype.h</filename></para>
1154 <para><filename class="directory">/home/gcc/build</filename></para>
1155 <para><filename class="libraryfile">libstdc++.so</filename></para>