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/docblocks.html">Special
447 Documentation Blocks</link> section of
451 <orderedlist inheritnum="ignore" continuation="restarts">
453 <para>For longer comments, use the Javadoc style...</para>
458 ...not the Qt style. The intermediate *'s are preferred.
464 Use the triple-slash style only for one-line comments (the
465 <quote>brief</quote> mode).
471 This is disgusting. Don't do this.
477 Some specific guidelines:
481 Use the @-style of commands, not the !-style. Please be
482 careful about whitespace in your markup comments. Most of the
483 time it doesn't matter; doxygen absorbs most whitespace, and
484 both HTML and *roff are agnostic about whitespace. However,
485 in <pre> blocks and @code/@endcode sections, spacing can
486 have <quote>interesting</quote> effects.
490 Use either kind of grouping, as
491 appropriate. <filename>doxygroups.cc</filename> exists for this
492 purpose. See <filename>stl_iterator.h</filename> for a good example
493 of the <quote>other</quote> kind of grouping.
497 Please use markup tags like @p and @a when referring to things
498 such as the names of function parameters. Use @e for emphasis
499 when necessary. Use @c to refer to other standard names.
500 (Examples of all these abound in the present code.)
504 Complicated math functions should use the multi-line
505 format. An example from <filename>random.h</filename>:
509 <literallayout class="normal">
511 * @brief A model of a linear congruential random number generator.
514 * x_{i+1}\leftarrow(ax_{i} + c) \bmod m
521 One area of note is the markup required for
522 <literal>@file</literal> markup in header files. Two details
523 are important: for filenames that have the same name in
524 multiple directories, include part of the installed path to
525 disambiguate. For example:
529 <literallayout class="normal">
530 /** @file debug/vector
531 * This file is a GNU debug extension to the Standard C++ Library.
537 The other relevant detail for header files is the use of a
538 libstdc++-specific doxygen alias that helps distinguish
539 between public header files (like <filename>random</filename>)
540 from implementation or private header files (like
541 <filename>bits/c++config.h</filename>.) This alias is spelled
542 <literal>@headername</literal> and can take one or two
543 arguments that detail the public header file or files that
544 should be included to use the contents of the file. All header
545 files that are not intended for direct inclusion must use
546 <literal>headername</literal> in the <literal>file</literal>
551 <literallayout class="normal">
552 /** @file bits/basic_string.h
553 * This is an internal header file, included by other library headers.
554 * Do not attempt to use it directly. @headername{string}
560 Be careful about using certain, special characters when
561 writing Doxygen comments. Single and double quotes, and
562 separators in filenames are two common trouble spots. When in
563 doubt, consult the following table.
567 <title>HTML to Doxygen Markup Comparison</title>
569 <tgroup cols="2" align="left" colsep="1" rowsep="1">
570 <colspec colname="c1"/>
571 <colspec colname="c2"/>
576 <entry>Doxygen</entry>
597 <entry><i></entry>
598 <entry>@a word</entry>
602 <entry><b></entry>
603 <entry>@b word</entry>
607 <entry><code></entry>
608 <entry>@c word</entry>
612 <entry><em></entry>
613 <entry>@a word</entry>
617 <entry><em></entry>
618 <entry><em>two words or more</em></entry>
630 <section xml:id="doc.docbook"><info><title>Docbook</title></info>
633 <section xml:id="docbook.prereq"><info><title>Prerequisites</title></info>
637 <title>Docbook Prerequisites</title>
639 <tgroup cols="3" align="center" colsep="1" rowsep="1">
640 <colspec colname="c1"/>
641 <colspec colname="c2"/>
642 <colspec colname="c3"/>
647 <entry>Version</entry>
648 <entry>Required By</entry>
655 <entry>docbook5-style-xsl</entry>
656 <entry>1.76.1</entry>
661 <entry>xsltproc</entry>
662 <entry>1.1.26</entry>
667 <entry>xmllint</entry>
669 <entry>validation</entry>
673 <entry>dblatex</entry>
675 <entry>pdf output</entry>
679 <entry>pdflatex</entry>
680 <entry>2007-59</entry>
681 <entry>pdf output</entry>
685 <entry>docbook2X</entry>
687 <entry>info output</entry>
691 <entry>epub3 stylesheets</entry>
693 <entry>epub output</entry>
701 Editing the DocBook sources requires an XML editor. Many
702 exist: some notable options
703 include <command>emacs</command>, <application>Kate</application>,
704 or <application>Conglomerate</application>.
708 Some editors support special <quote>XML Validation</quote>
709 modes that can validate the file as it is
710 produced. Recommended is the <command>nXML Mode</command>
711 for <command>emacs</command>.
715 Besides an editor, additional DocBook files and XML tools are
720 Access to the DocBook 5.0 stylesheets and schema is required. The
721 stylesheets are usually packaged by vendor, in something
722 like <filename>docbook5-style-xsl</filename>. To exactly match
723 generated output, please use a version of the stylesheets
725 to <filename>docbook5-style-xsl-1.75.2-3</filename>. The
726 installation directory for this package corresponds to
727 the <literal>XSL_STYLE_DIR</literal>
728 in <filename>doc/Makefile.am</filename> and defaults
729 to <filename class="directory">/usr/share/sgml/docbook/xsl-ns-stylesheets</filename>.
733 For processing XML, an XSLT processor and some style
734 sheets are necessary. Defaults are <command>xsltproc</command>
735 provided by <filename>libxslt</filename>.
739 For validating the XML document, you'll need
740 something like <command>xmllint</command> and access to the
741 relevant DocBook schema. These are provided
742 by a vendor package like <filename>libxml2</filename> and <filename>docbook5-schemas-5.0-4</filename>
746 For PDF output, something that transforms valid Docbook XML to PDF is
747 required. Possible solutions include <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://dblatex.sourceforge.net">dblatex</link>,
748 <command>xmlto</command>, or <command>prince</command>. Of
749 these, <command>dblatex</command> is the default. Other
750 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
751 consult the <email>libstdc++@gcc.gnu.org</email> list when
752 preparing printed manuals for current best practice and
757 For Texinfo output, something that transforms valid Docbook
758 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>.
762 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.
766 <section xml:id="docbook.rules"><info><title>Generating the DocBook Files</title></info>
770 The following Makefile rules generate (in order): an HTML
771 version of all the DocBook documentation, a PDF version of the
772 same, and a single XML document. These rules are not
773 conditional! If the required tools are not found, or are the
774 wrong versions, the rule may end in an error.
778 <screen><userinput>make doc-html-docbook</userinput></screen>
782 <screen><userinput>make doc-pdf-docbook</userinput></screen>
786 <screen><userinput>make doc-xml-single-docbook</userinput></screen>
790 Generated files are output into separate sub directores of
791 <filename class="directory">doc/docbook/</filename> in the
792 build directory, based on the output format. For instance, the
793 HTML docs will be in <filename
794 class="directory">doc/docbook/html</filename>.
798 If the Docbook stylesheets are installed in a custom location,
799 one can use the variable <literal>XSL_STYLE_DIR</literal> to
800 override the Makefile defaults. For example:
805 make <literal>XSL_STYLE_DIR="/usr/share/xml/docbook/stylesheet/nwalsh"</literal> doc-html-docbook
811 <section xml:id="docbook.debug">
812 <info><title>Debugging Generation</title></info>
815 Sometimes, mis-configuration of the pre-requisite tools can
816 lead to errors when attempting to build the
817 documentation. Here are some of the obvious errors, and ways
818 to fix some common issues that may appear quite cryptic.
822 First, if using a rule like <code>make pdf</code>, try to
823 narrow down the scope of the error to either docbook
824 (<code>make doc-pdf-docbook</code>) or doxygen (<code>make
825 doc-pdf-doxygen</code>).
829 Working on the docbook path only, closely examine the
830 contents of the following build directory:
831 <filename>build/target/libstdc++-v3/doc/docbook/latex</filename>.
832 Pay attention to three files enclosed within, annotated as follows.
839 <emphasis>spine.tex</emphasis>
843 The actual latex file, or partial latex file. This is generated
844 via <command>dblatex</command>, and is the LaTeX version of the
845 DocBook XML file <filename>spine.xml</filename>. Go to a specific
846 line, and look at the genrated LaTeX, and try to deduce what
847 markup in <filename>spine.xml</filename> is causing it.
853 <emphasis>spine.out</emphasis>
857 A log of the conversion from the XML form to the LaTeX form. This
858 is a linear list, from the beginning of the
859 <filename>spine.xml</filename> file: the last entry of this file
860 should be the end of the DocBook file. If it is truncated, then
861 you know that the last entry is the last part of the XML source
862 file that is valid. The error is after this point.
869 <emphasis>spine.log</emphasis>
873 A log of the compilation of the converted LaTeX form to pdf. This
874 is a linear list, from the beginning of the
875 <filename>spine.tex</filename> file: the last entry of this file
876 should be the end of the LaTeX file. If it is truncated, then you
877 know that the last entry is the last part of the generated LaTeX
878 source file that is valid. Often this file contains an error with
879 a specific line number of <filename>spine.tex</filename> that is
887 If the error at hand is not obvious after examination, or if one
888 encounters the inscruitable <quote>Incomplete
889 \ifmmode</quote> error, a fall-back strategy is to start
890 commenting out parts of the XML document (regardless of what
891 this does to over-all document validity). Start by
892 commenting out each of the largest parts of the
893 <filename>spine.xml</filename> file, section by section,
894 until the offending section is identified.
900 <section xml:id="docbook.validation"><info><title>Editing and Validation</title></info>
903 After editing the xml sources, please make sure that the XML
904 documentation and markup is still valid. This can be
905 done easily, with the following validation rule:
909 <userinput>make doc-xml-validate-docbook</userinput>
913 This is equivalent to doing:
918 xmllint --noout --valid <filename>xml/index.xml</filename>
923 Please note that individual sections and chapters of the
924 manual can be validated by substituting the file desired for
925 <filename>xml/index.xml</filename> in the command
926 above. Reducing scope in this manner can be helpful when
927 validation on the entire manual fails.
931 All Docbook xml sources should always validate. No excuses!
936 <section xml:id="docbook.examples"><info><title>File Organization and Basics</title></info>
939 <literallayout class="normal">
940 <emphasis>Which files are important</emphasis>
942 All Docbook files are in the directory
945 Inside this directory, the files of importance:
946 spine.xml - index to documentation set
947 manual/spine.xml - index to manual
948 manual/*.xml - individual chapters and sections of the manual
949 faq.xml - index to FAQ
950 api.xml - index to source level / API
952 All *.txml files are template xml files, i.e., otherwise empty files with
953 the correct structure, suitable for filling in with new information.
955 <emphasis>Canonical Writing Style</emphasis>
959 member function template
960 (via C++ Templates, Vandevoorde)
962 class in namespace std: allocator, not std::allocator
964 header file: iostream, not <iostream>
967 <emphasis>General structure</emphasis>
1002 <section xml:id="docbook.markup"><info><title>Markup By Example</title></info>
1006 Complete details on Docbook markup can be found in the DocBook
1008 <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.docbook.org/tdg/en/html/part2.html">online</link>.
1009 An incomplete reference for HTML to Docbook conversion is
1010 detailed in the table below.
1014 <title>HTML to Docbook XML Markup Comparison</title>
1016 <tgroup cols="2" align="left" colsep="1" rowsep="1">
1017 <colspec colname="c1"/>
1018 <colspec colname="c2"/>
1023 <entry>Docbook</entry>
1029 <entry><p></entry>
1030 <entry><para></entry>
1033 <entry><pre></entry>
1034 <entry><computeroutput>, <programlisting>,
1035 <literallayout></entry>
1038 <entry><ul></entry>
1039 <entry><itemizedlist></entry>
1042 <entry><ol></entry>
1043 <entry><orderedlist></entry>
1046 <entry><il></entry>
1047 <entry><listitem></entry>
1050 <entry><dl></entry>
1051 <entry><variablelist></entry>
1054 <entry><dt></entry>
1055 <entry><term></entry>
1058 <entry><dd></entry>
1059 <entry><listitem></entry>
1063 <entry><a href=""></entry>
1064 <entry><ulink url=""></entry>
1067 <entry><code></entry>
1068 <entry><literal>, <programlisting></entry>
1071 <entry><strong></entry>
1072 <entry><emphasis></entry>
1075 <entry><em></entry>
1076 <entry><emphasis></entry>
1080 <entry><quote></entry>
1087 And examples of detailed markup for which there are no real HTML
1088 equivalents are listed in the table below.
1092 <title>Docbook XML Element Use</title>
1094 <tgroup cols="2" align="left" colsep="1" rowsep="1">
1095 <colspec colname="c1"/>
1096 <colspec colname="c2"/>
1100 <entry>Element</entry>
1107 <entry><structname></entry>
1108 <entry><structname>char_traits</structname></entry>
1111 <entry><classname></entry>
1112 <entry><classname>string</classname></entry>
1115 <entry><function></entry>
1117 <para><function>clear()</function></para>
1118 <para><function>fs.clear()</function></para>
1122 <entry><type></entry>
1123 <entry><type>long long</type></entry>
1126 <entry><varname></entry>
1127 <entry><varname>fs</varname></entry>
1130 <entry><literal></entry>
1132 <para><literal>-Weffc++</literal></para>
1133 <para><literal>rel_ops</literal></para>
1137 <entry><constant></entry>
1139 <para><constant>_GNU_SOURCE</constant></para>
1140 <para><constant>3.0</constant></para>
1144 <entry><command></entry>
1145 <entry><command>g++</command></entry>
1148 <entry><errortext></entry>
1149 <entry><errortext>In instantiation of</errortext></entry>
1152 <entry><filename></entry>
1154 <para><filename class="headerfile">ctype.h</filename></para>
1155 <para><filename class="directory">/home/gcc/build</filename></para>
1156 <para><filename class="libraryfile">libstdc++.so</filename></para>