|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
Please report any bugs to email@example.com.
indent is run twice on a file, with the same profile,
it should never change that file the second time. With the
current design of
indent, this can not be guaranteed,
and it has not been extensively tested.
indent does not understand C. In some cases this leads to
the inability to join lines. The result is that running a file
indent is irreversible, even if the used input
file was the result of running
indent with a given profile
While an attempt was made to get
indent working for C++, it
will not do a good job on any C++ source except the very simplest.
indent does not look at the given ‘--line-length’ option
when writing comments to the output file. This results often in comments
being put far to the right. In order to prohibit
joining a broken line that has a comment at the end, make sure that the
comments start on the first line of the break.
indent does not count lines and comments (see the ‘-v’
indent is turned off with
/* *INDENT-OFF* */.
Comments of the form
/*UPPERCASE*/ are not treated as comment but as an
identifier, causing them to be joined with the next line. This renders
comments of this type useless, unless they are embedded in the code to
|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]|
This document was generated by david on December, 15 2008 using texi2html 1.78.