Hi,
Attached is a patch that fixes a few grammar errors in the ref.tex file.
PS Michael:
I must apologise. :-) Whenever I need to reference language or syntax
documentation, it is second nature to fire up the Kylix 3 help. I was
trying to understand packed records a bit better, but the Delphi and
Kylix help was not very clear. I then viewed the FPC help - which
answered all my questions. Great work! :-)
PS #2:
It's amazing how accessing relational databases to store and retrieve
information makes a developer lazy. I had to access a binary data file
via complex record structures and couldn't remember how to do it
exactly, without first reading some documentation. Yet, when I started
with Turbo Pascal years ago, it was all I did. :-)
Regards,
- Graeme -
_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/
Index: ref.tex
===================================================================
--- ref.tex (revision 559)
+++ ref.tex (working copy)
@@ -1392,7 +1392,7 @@
the internal position of the elements in the type. The compiler will lay
out the elements of the structure in memory as it thinks will be most
suitable. That is, the order of the elements will be kept, but the location
-of the elements is not guaranteed, and is partially governed by the \var{\$PACKRECORDS}
+of the elements are not guaranteed, and is partially governed by the \var{\$PACKRECORDS}
directive (this directive is explained in the \progref).
\keywordlink{packed} \keywordlink{bitpacked}
@@ -1415,7 +1415,7 @@
\end{description}
The byte packing mechanism is simple: the compiler aligns each element of
-the structure on the first available byte boundary, even if size of the
+the structure on the first available byte boundary, even if the size of the
previous element (small enumerated types, subrange types) is less than a
byte.
@@ -1429,7 +1429,7 @@
Note that the internals of the bitpacking are opaque: they can change
at any time in the future. What is more: the internal packing depends
on the endianness of the platform for which the compilation is done,
-and no conversion between platforms is possible. This makes bitpacked
+and no conversion between platforms are possible. This makes bitpacked
structures unsuitable for storing on disk or transport over networks.
The format is however the same as the one used by the GNU Pascal
Compiler, and the \fpc team aims to retain this compatibility in the future.
@@ -1686,7 +1686,7 @@
\fpc supports fixed records and records with variant parts.
The syntax diagram for a record type is
\input{syntax/typerec.syn}
-\index{Packed} So the following are valid record types declarations:
+\index{Packed} So the following are valid record type declarations:
\begin{verbatim}
Type
Point = Record
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
