Re: Grammatical fixes in gawk manual v.3.1.8

[Ralf Wildenhues]

Hello Peter,

* Peter Axon wrote on Thu, Dec 02, 2010 at 03:11:19AM CET:
> --- doc/gawk.texi       2010-04-20 18:41:01.000000000 +1000
> +++ doc/gawk-new.texi   2010-12-02 13:01:52.000000000 +1100
> @@ -12779,7 +12779,7 @@
>  The @var{regexp} argument may be either a regexp constant
>  (@samp{/@dots{}/}) or a string constant (@var{"@dots{}"}).
>  In the latter case, the string is treated as a regexp to be matched.
> address@hidden Regexps}, for a
> +See @ref{Computed Regexps}, for a

This is better changed into
   @xref{...}

because @xref already includes the "See" (or "Note") in some of the
various output formats.  See 'info texinfo "Reference Syntax"'.

>  discussion of the difference between the two forms, and the
>  implications for writing your program correctly.
>  
> @@ -12934,7 +12934,7 @@
>  string.
>  @value{DARKCORNER}
>  The POSIX standard allows this as well.
> address@hidden Regexps}, for a
> +See @xref{Computed Regexps}, for a

This hunk shouldn't be necessary, for reasons stated above.

>  discussion of the difference between using a string constant or a regexp 
> constant,
>  and the implications for writing your program correctly.
>  
> @@ -13003,7 +13003,7 @@
>  The @var{regexp} argument may be either a regexp constant
>  (@samp{/@dots{}/}) or a string constant (@var{"@dots{}"}).
>  In the latter case, the string is treated as a regexp to be matched.
> address@hidden Regexps}, for a
> +See @ref{Computed Regexps}, for a

See above.

>  discussion of the difference between the two forms, and the
>  implications for writing your program correctly.
>  
[...]

Cheers,
Ralf