[SCM] gawk branch, gawk-5.3-stable, updated. gawk-4.1.0-5490-g8d55806d

[Arnold Robbins]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gawk".

The branch, gawk-5.3-stable has been updated
       via  8d55806d3b7853a93c2aa76b94bc8640758bd8b5 (commit)
      from  29b29fe835e982d11a49e3f531179b155bc0ce59 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://git.sv.gnu.org/cgit/gawk.git/commit/?id=8d55806d3b7853a93c2aa76b94bc8640758bd8b5

commit 8d55806d3b7853a93c2aa76b94bc8640758bd8b5
Author: Arnold D. Robbins <arnold@skeeve.com>
Date:   Sun Jul 14 16:01:02 2024 +0300

    Yet another small doc fix.

diff --git a/doc/ChangeLog b/doc/ChangeLog
index 1b5514c0..bc011eb5 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,8 @@
+2024-07-14         Arnold D. Robbins     <arnold@skeeve.com>
+
+       * gawk.texi: Use @code for getline, not @command. Thanks to
+       Thanks to Antonio Colombo.
+
 2024-07-13         Arnold D. Robbins     <arnold@skeeve.com>
 
        * gawk.texi: Small fixups around use of getline and spelling fixes.
diff --git a/doc/gawk.texi b/doc/gawk.texi
index 09020d71..616cc82f 100644
--- a/doc/gawk.texi
+++ b/doc/gawk.texi
@@ -8759,7 +8759,7 @@ Parts I and II
 and have a good knowledge of how @command{awk} works.
 
 @cindex @command{gawk} @subentry @code{ERRNO} variable in
-@cindex @code{ERRNO} variable @subentry with @command{getline} function
+@cindex @code{ERRNO} variable @subentry with @code{getline} function
 @cindex differences in @command{awk} and @command{gawk} @subentry 
@code{getline} function
 @cindex @code{getline} function @subentry return values
 @cindex @option{--sandbox} option @subentry input redirection with 
@code{getline}
@@ -9309,7 +9309,7 @@ if ((getline VAR) < 0)
     print "Read error";
 @end example
 
-It is, in fact, best to parenthesize calls to @command{getline}
+It is, in fact, best to parenthesize calls to @code{getline}
 in all control expressions, as some versions of @command{awk}
 require this. Thus, the previous examples are best written
 this way:
@@ -9345,7 +9345,7 @@ BEGIN @{
 Here, the side effect is the @samp{++c}.  Is @code{c} incremented if
 end-of-file is encountered before the element in @code{a} is assigned?
 
-Despite the lack of parentheses when calling @command{getline},
+Despite the lack of parentheses when calling @code{getline},
 @command{gawk} evaluates
 the expression @samp{a[++c]} before attempting to read from @file{f}.
 However, some versions of @command{awk} only evaluate the expression once they

-----------------------------------------------------------------------

Summary of changes:
 doc/ChangeLog | 5 +++++
 doc/gawk.texi | 6 +++---
 2 files changed, 8 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
gawk