gawk 3.0.98 documentation suggestion for POSIXLY_CORRECT and POSIX

[Paul Eggert]

A while back I noted that gawk doesn't follow the GNU coding standards
with respect to POSIXLY_CORRECT, and suggested a possible fix (without
coding it up).  I don't know whether you deferred the proposal or
rejected it, but at any rate I think the incompatibility should be
plainly documented, and here is a proposed patch to do that.

Also, while sending this email I noticed that the gawk 3.0.98 README says
"This address send mail to" where it should say
"This address sends mail to".

2001-05-15  Paul Eggert  <address@hidden>

        * gawk.texi: Warn up-front (indirectly) that plain Gawk is not
        compatible with SVR4 awk and with POSIX awk.  Describe how
        Gawk differs from the GNU standard in its interpretation of
        POSIXLY_CORRECT.

===================================================================
RCS file: gawk.texi,v
retrieving revision 3.0.98.0
retrieving revision 3.0.98.1
diff -pu -r3.0.98.0 -r3.0.98.1
--- gawk.texi   2001/05/13 15:38:13     3.0.98.0
+++ gawk.texi   2001/05/16 02:58:02     3.0.98.1
@@ -780,9 +780,11 @@ Such jobs are often easier with @command
 The @command{awk} utility interprets a special-purpose programming language
 that makes it easy to handle simple data-reformatting jobs.
 
-The GNU implementation of @command{awk} is called @command{gawk}; it is fully
+The GNU implementation of @command{awk} is called @command{gawk}; if you
+invoke it with the proper options or environment variables
+(@pxref{Options, ,Command-Line Options}), it is fully
 compatible with the System V Release 4 version of
address@hidden  @command{gawk} is also compatible with the POSIX
address@hidden and with the POSIX
 specification of the @command{awk} language.  This means that all
 properly written @command{awk} programs should work with @command{gawk}.
 Thus, we usually don't distinguish between @command{gawk} and other
@@ -15261,7 +15263,10 @@ program source code.
 If the environment variable @env{POSIXLY_CORRECT} exists,
 then @command{gawk} behaves in strict POSIX mode, exactly as if
 you had supplied the @option{--posix} command-line option.
-Many GNU programs look for this environment variable to turn on
+Many GNU programs look for this environment variable to suppress
+extensions that conflict with POSIX, but @command{gawk} behaves
+differently: it suppresses all extensions, even those that do not
+conflict with POSIX, and behaves in
 strict POSIX mode. If @option{--lint} is supplied on the command-line
 and @command{gawk} turns on POSIX mode because of @env{POSIXLY_CORRECT},
 then it issues a warning message indicating that POSIX