aboutsummaryrefslogtreecommitdiffstats
path: root/doc/gawktexi.in
diff options
context:
space:
mode:
authorArnold D. Robbins <arnold@skeeve.com>2016-03-27 21:39:01 +0300
committerArnold D. Robbins <arnold@skeeve.com>2016-03-27 21:39:01 +0300
commit1a4eaf4f7cbef6e407fe49437c8176e1650baa88 (patch)
tree789df4d9511eda8c7f612696c1b89ef39c60a6e0 /doc/gawktexi.in
parent3a154919fe4c0e820f989e2bb347d6f8b87a7a79 (diff)
downloadegawk-1a4eaf4f7cbef6e407fe49437c8176e1650baa88.tar.gz
egawk-1a4eaf4f7cbef6e407fe49437c8176e1650baa88.tar.bz2
egawk-1a4eaf4f7cbef6e407fe49437c8176e1650baa88.zip
Doc update about comments in pretty printing.
Diffstat (limited to 'doc/gawktexi.in')
-rw-r--r--doc/gawktexi.in7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/gawktexi.in b/doc/gawktexi.in
index d420ad68..3e0f6bba 100644
--- a/doc/gawktexi.in
+++ b/doc/gawktexi.in
@@ -27422,7 +27422,12 @@ There is a significant difference between the output created when
profiling, and that created when pretty-printing. Pretty-printed output
preserves the original comments that were in the program, although their
placement may not correspond exactly to their original locations in the
-source code.
+source code.@footnote{@command{gawk} does the best it can to preserve
+the distinction between comments at the end of a statement and comments
+on lines by themselves. Due to implementation constraints, it does not
+always do so correctly, particularly for @code{switch} statements. The
+@command{gawk} maintainers hope to improve this in a subsequent
+release.}
However, as a deliberate design decision, profiling output @emph{omits}
the original program's comments. This allows you to focus on the