diff options
author | Eric S. Raymond <esr@thyrsus.com> | 2014-06-03 18:32:53 -0400 |
---|---|---|
committer | Eric S. Raymond <esr@thyrsus.com> | 2014-06-03 18:32:53 -0400 |
commit | 47be3b18b2317ca54ee0129a61cc803bf52947a4 (patch) | |
tree | 13db11cbd6d58025e8c49d6e2cf2ba68f4d03987 | |
parent | f3491dfaa2581beecde58e1f69bc4cb6f4280352 (diff) | |
download | deheader-47be3b18b2317ca54ee0129a61cc803bf52947a4.tar.gz deheader-47be3b18b2317ca54ee0129a61cc803bf52947a4.tar.bz2 deheader-47be3b18b2317ca54ee0129a61cc803bf52947a4.tar.xz deheader-47be3b18b2317ca54ee0129a61cc803bf52947a4.zip |
Documentation polishing.
-rw-r--r-- | control | 2 | ||||
-rw-r--r-- | deheader.xml | 14 |
2 files changed, 8 insertions, 8 deletions
@@ -3,7 +3,7 @@ Package: deheader -Description: find (optionally remove) unneeded includes in C or C++ sourcefiles +Description: find (optionally remove) unneeded includes in C or C++ sourcefiles. deheader analyzes C and C++ files to determine which header inclusions can be removed while still allowing them to compile. This may result in substantial improvements in compilation time, especially on large C++ projects; it also diff --git a/deheader.xml b/deheader.xml index 711980e..c375279 100644 --- a/deheader.xml +++ b/deheader.xml @@ -80,7 +80,7 @@ given and headers removed.</para> <para>At verbosity level 0, only messages indicating removable headers are issued. At verbosity 1, test compilations are timed and progess indicated with a twirling-baton prompt. At verbosity level 2, you get -vebose progress messages on the analysis. At verbosity level 3, you +verbose progress messages on the analysis. At verbosity level 3, you see the output from the make and compilation commands.</para> <para>If the -q (--quiet) option flag was not set, the last line of the @@ -148,13 +148,13 @@ Takes a Python regular expression.</para> <refsect1 id='bugs'><title>BUGS</title> -<para>Rarely, test-compiling after running with <option>-r</option> will -sometimes show that this tool removed some headers that are actually -required for your build. This can happen because +<para>Very rarely, test-compiling after running with +<option>-r</option> may show that this tool removed some headers that +are actually required for your build. This can happen because <command>deheader</command> doesn't know about all the strange things -your build system gets up to, and the problem of analyzing your build to -understand them would be Turing-complete. Simply revert the altered -files and continue.</para> +your build system gets up to, and the problem of analyzing your build +to understand them would be Turing-complete. Simply revert the +altered files and continue.</para> <para>Due to minor variations in system headers, it is possible your program may not port correctly to other Unix variants after being |