+2010-09-08 Eric Blake <eblake@redhat.com>
+
+ docs: mention traditional awk limitation
+ * doc/autoconf.texi (Limitations of Usual Tools) <awk>: Mention
+ that traditional awk lacks ENVIRON. Add reference to awk manual.
+ (Particular Programs) <AC_PROG_AWK>: Add reference to awk section.
+ Reported by Ralf Wildenhues.
+
2010-09-07 Eric Blake <eblake@redhat.com>
docs: mention bash vs. POSIXLY_CORRECT
It tries @code{gawk} first because that is reported to be the
best implementation. The result can be overridden by setting the
variable @code{AWK} or the cache variable @code{ac_cv_prog_AWK}.
+
+Using this macro is sufficient to avoid the pitfalls of traditional
+@command{awk} (@pxref{awk, , Limitations of Usual Tools}).
@end defmac
@defmac AC_PROG_GREP
@c This table includes things like `@command{expr} (|)', so we can't
@c use @table @command.
@table @asis
+@anchor{awk}
@item @command{awk}
@c ----------------
@prindex @command{awk}
conform to Posix. Nowadays @code{AC_PROG_AWK} (@pxref{Particular
Programs}) finds you an Awk that doesn't have these problems, but if
for some reason you prefer not to use @code{AC_PROG_AWK} you may need to
-address them.
+address them. For more detailed descriptions, see @ref{Language
+History, , @command{awk} language history, gawk, GNU Awk User's Guide}.
Traditional Awk does not support multidimensional arrays or user-defined
functions.
@code{@var{a}?@var{b}:@var{c}}, @code{!@var{a}}, @code{@var{a}^@var{b}},
or @code{@var{a}^=@var{b}}.
-Traditional Awk does not support the predefined @code{CONVFMT} variable.
+Traditional Awk does not support the predefined @code{CONVFMT} or
+@code{ENVIRON} variables.
Traditional Awk supports only the predefined functions @code{exp}, @code{index},
@code{int}, @code{length}, @code{log}, @code{split}, @code{sprintf},