.

will be generated. You may view the manual page with: nroff -man .

| less'. A typical entry in a Makefile or Makefile.am is: DB2MAN = /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl XP = xsltproc -''-nonet -''-param man.charmap.use.subset "0" manpage.1: manpage.xml $(XP) $(DB2MAN) $< The xsltproc binary is found in the xsltproc package. The XSL files are in docbook-xsl. A description of the parameters you can use can be found in the docbook-xsl-doc-* packages. Please remember that if you create the nroff version in one of the debian/rules file targets (such as build), you will need to include xsltproc and docbook-xsl in your Build-Depends control field. Alternatively use the xmlto command/package. That will also automatically pull in xsltproc and docbook-xsl. Notes for using docbook2x: docbook2x-man does not automatically create the AUTHOR(S) and COPYRIGHT sections. In this case, please add them manually as ... . To disable the automatic creation of the AUTHOR(S) and COPYRIGHT sections read /usr/share/doc/docbook-xsl/doc/manpages/authors.html. This file can be found in the docbook-xsl-doc-html package. Validation can be done using: `xmllint -''-noout -''-valid manpage.xml` General documentation about man-pages and man-page-formatting: man(1), man(7), http://www.tldp.org/HOWTO/Man-Page/ --> ]> &dhpackage; &dhfirstname; &dhsurname; Wrote this manpage for the Debian system.

&dhemail;

2008 &dhusername; This manual page was written for the Debian system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or (at your option) any later version published by the Free Software Foundation. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. &dhucpackage; &dhsection; &dhpackage; Simple syntax checking of C/C++. &dhpackage; --all --force --help -I[dir] --quiet --style --unused-functions --verbose -j[jobs] --xml file or path ... A tool for static C/C++ code analysis Intended to complement the checking of the compiler. Checks for: memory leaks, mismatching allocation-deallocation, buffer overrun, and many more. Analyze given C/C++ files for common errors. -a --all Normally a message is only shown if cppcheck is sure it has found a bug. When this option is given, all messages are shown. -f --force Force checking of files that have a lot of configurations. Error is printed if such a file is found so there is no reason to use this by default. -h --help Print help text. -I [dir] Give include path. Give several -I parameters to give several paths. First given path is checked first. If paths are relative to source files, this is not needed. -q --quiet Only print something when there is an error. -s --style Check coding style. --unused-functions Check if there are unused functions -v --verbose More detailed error reports -j [jobs] Start [jobs] threads to do the checking work. --xml Write results in xml to error stream The program was written by Daniel Marjamäki, Reijo Tomperi, Nicolas Le Cam, Leandro Penz, Kimmo Varis and Vesa Pikki Full list of features: http://cppcheck.wiki.sourceforge.net/