Add a FIXME in the doc for @sup. One day...

1 files changed, 4 insertions, 0 deletions

diff --git a/doc/gawk.texi b/doc/gawk.texi
index e5b39dd0..27aaa74f 100644
--- a/doc/gawk.texi
+++ b/doc/gawk.texi
@@ -11782,6 +11782,7 @@ has the value four, but it changes the value of @code{foo} to five.
 In other words, the operator returns the old value of the variable,
 but with the side effect of incrementing it.
 
+@c FIXME: Use @sup here for superscript
 The post-increment @samp{foo++} is nearly the same as writing @samp{(foo
 += 1) - 1}.  It is not perfectly equivalent because all numbers in
 @command{awk} are floating point---in floating point, @samp{foo + 1 - 1} does
@@ -18558,6 +18559,7 @@ which is sufficient to represent times through
 2038-01-19 03:14:07 UTC.  Many systems support a wider range of timestamps,
 including negative timestamps that represent times before the
 epoch.
+@c FIXME: Use @sup here for superscript
 
 @cindex @command{date} utility, GNU
 @cindex time, retrieving
@@ -30210,6 +30212,7 @@ signed. The possible ranges of values are shown in @ref{table-numeric-ranges}.
 @end ifnottex
 @ifdocbook
 @item Single-precision floating point (approximate) @tab
+@c FIXME: Use @sup here for superscript
 @docbook
 1.175494<superscript>-38</superscript>
 @end docbook
@@ -30828,6 +30831,7 @@ the following computes
 @end docbook
 the result of which is beyond the
 limits of ordinary hardware double-precision floating-point values:
+@c FIXME: Use @sup here for superscript
 
 @example
 $ @kbd{gawk -M 'BEGIN @{}