public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Marc Poulhiès" <poulhies@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Eric Botcazou <ebotcazou@adacore.com>
Subject: [COMMITTED] ada: Fix incorrect quoting in documentation
Date: Tue, 28 Nov 2023 10:39:31 +0100	[thread overview]
Message-ID: <20231128093931.2971051-1-poulhies@adacore.com> (raw)

From: Eric Botcazou <ebotcazou@adacore.com>

gcc/ada/

	* doc/gnat_rm/the_implementation_of_standard_i_o.rst: Fix a couple
	occurrences of incorrect quoting.
	* gnat_rm.texi: Regenerate.

Tested on x86_64-pc-linux-gnu, committed on master.

---
 gcc/ada/doc/gnat_rm/the_implementation_of_standard_i_o.rst | 5 ++---
 gcc/ada/gnat_rm.texi                                       | 7 +++----
 2 files changed, 5 insertions(+), 7 deletions(-)

diff --git a/gcc/ada/doc/gnat_rm/the_implementation_of_standard_i_o.rst b/gcc/ada/doc/gnat_rm/the_implementation_of_standard_i_o.rst
index e0b9e0c00d8..f6d884d0823 100644
--- a/gcc/ada/doc/gnat_rm/the_implementation_of_standard_i_o.rst
+++ b/gcc/ada/doc/gnat_rm/the_implementation_of_standard_i_o.rst
@@ -70,7 +70,7 @@ library streams facility; where
 *
   All files are opened using ``fopen``.
 *
-  All input/output operations use ``fread``/`fwrite`.
+  All input/output operations use ``fread``/``fwrite``.
 
 There is no internal buffering of any kind at the Ada library level. The only
 buffering is that provided at the system level in the implementation of the
@@ -127,8 +127,7 @@ The records of a Direct_IO file are simply written to the file in index
 sequence, with the first record starting at offset zero, and subsequent
 records following.  There is no control information of any kind.  For
 example, if 32-bit integers are being written, each record takes
-4-bytes, so the record at index ``K`` starts at offset
-(``K``-1)*4.
+4-bytes, so the record at index ``K`` starts at offset ``(K-1)*4``.
 
 There is no limit on the size of Direct_IO files, they are expanded as
 necessary to accommodate whatever records are written to the file.
diff --git a/gcc/ada/gnat_rm.texi b/gcc/ada/gnat_rm.texi
index 52ddb27fd01..a6a1a67b661 100644
--- a/gcc/ada/gnat_rm.texi
+++ b/gcc/ada/gnat_rm.texi
@@ -19,7 +19,7 @@
 
 @copying
 @quotation
-GNAT Reference Manual , Oct 26, 2023
+GNAT Reference Manual , Nov 24, 2023
 
 AdaCore
 
@@ -21621,7 +21621,7 @@ library streams facility; where
 All files are opened using @code{fopen}.
 
 @item 
-All input/output operations use @code{fread}/@cite{fwrite}.
+All input/output operations use @code{fread}/@code{fwrite}.
 @end itemize
 
 There is no internal buffering of any kind at the Ada library level. The only
@@ -21675,8 +21675,7 @@ The records of a Direct_IO file are simply written to the file in index
 sequence, with the first record starting at offset zero, and subsequent
 records following.  There is no control information of any kind.  For
 example, if 32-bit integers are being written, each record takes
-4-bytes, so the record at index @code{K} starts at offset
-(@code{K}-1)*4.
+4-bytes, so the record at index @code{K} starts at offset @code{(K-1)*4}.
 
 There is no limit on the size of Direct_IO files, they are expanded as
 necessary to accommodate whatever records are written to the file.
-- 
2.42.0


                 reply	other threads:[~2023-11-28  9:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231128093931.2971051-1-poulhies@adacore.com \
    --to=poulhies@adacore.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).