Documented m4 incompatibility with lex.

diff --git a/doc/flex.texi b/doc/flex.texi
index 64d9767ec18df709a1ae723b8c50a1af1f52d687..8b6591fff21f74108e44f4018d8d2af20d67d287 100644 (file)
--- a/doc/flex.texi
+++ b/doc/flex.texi
@@ -4585,6 +4585,12 @@ indicating which version of @code{flex} generated the scanner. For
 example, for the 2.5.22 release, these defines would be 2,  5 and 22
 respectively. If the version of @code{flex} being used is a beta
 version, then the symbol @code{FLEX_BETA} is defined.
+
+@item
+The symbols @samp{[[} and @samp{]]} in the code sections of the input
+may conflict with the m4 delimiters. @xref{M4 Dependency}.
+
+
 @end itemize
 
 @cindex POSIX comp;compliance
@@ -8228,7 +8234,6 @@ As you can see, there really is no magic here. We just use
 @node M4 Dependency, , Bison Bridge, Appendices
 @section M4 Dependency
 @cindex m4
-
 The macro processor @code{m4}@footnote{The use of m4 is subject to change in
 future revisions of flex.} must be installed wherever flex is installed.
 @code{flex} invokes @samp{m4}, found by searching the directories in the