(Limitations of Usual Tools): Also list \< and \>, and mention that

HP-UX's grep, like the one from Solaris, does not support that syntax.

diff --git a/ChangeLog b/ChangeLog
index 0db98012b50b6e6eea8830c4cfe92ca71728c172..b6d5608882e803433f2255d096a59b2fcffcfcd2 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,6 +1,8 @@
 2007-03-17  Jim Meyering  <jim@meyering.net>
 
        * doc/autoconf.texi: Adjust grammar around use of "heuristics".
+       (Limitations of Usual Tools): Also list \< and \>, and mention that
+       HP-UX's grep, like the one from Solaris, does not support that syntax.
 
 2007-03-09  Stepan Kasal  <kasal@ucw.cz>
 

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 389220f5446442b5c174f4694ccef472c3ee2ab8..c1f1abbf431fdce0cce98c2ed9a8333a7d115bd6 100644 (file)
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -13562,8 +13562,8 @@ Portable @command{grep} regular expressions should use @samp{\} only to
 escape characters in the string @samp{$()*.0123456789[\^@{@}}.  For example,
 alternation, @samp{\|}, is common but Posix does not require its
 support in basic regular expressions, so it should be avoided in
-portable scripts.  Solaris @command{grep} does not support it.
-Similarly, @samp{\+} and @samp{\?} should be avoided.
+portable scripts.  Solaris and HP-UX @command{grep} do not support it.
+Similarly, @samp{\<}, @samp{\>}, @samp{\+} and @samp{\?} should be avoided.
 
 
 @item @command{join}