[COMMITTED] ada: Fix incorrect quoting in documentation
Checks
Commit Message
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(-)
@@ -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.
@@ -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.