Please report any bugs to bug-indent@gnu.org.
When 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
through indent is irreversible, even if the used input file was
the result of running indent with a given profile
('.indent.pro').
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 indent
from 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' option)
when 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 begin with.
