CVS difference for ais/ai-00133.txt

Differences between 1.13 and version 1.14
Log of other versions for file ais/ai-00133.txt

--- ais/ai-00133.txt	2004/10/05 22:48:59	1.13
+++ ais/ai-00133.txt	2004/11/14 06:36:49	1.14
@@ -17,12 +17,15 @@
 
 !summary
 
+Bit_Order clauses are concerned with the numbering of bits and not concerned
+with data flipping interoperability.
+
 The interpretation of component_clauses in the nondefault bit order is based on
 *machine scalars*, which are chunks of storage that can be natively loaded and
 stored by the machine. All the component_clauses at a given offset are
-considered to be part of the same machine scalar, and the first_bit and last_bit
-are interpreted as bit offsets within that machine scalar. This makes it
-possible to write endian-independent record_representation_clauses.
+considered to be part of the same machine scalar, and the first_bit and
+last_bit are interpreted as bit offsets within that machine scalar. This makes
+it possible to write endian-independent record_representation_clauses.
 
 The recommended level of support for Bit_Order clauses is modified to include
 support for the nondefault bit order in all cases.
@@ -56,12 +59,10 @@
 A *machine scalar* is an amount of storage that can be conveniently and
 efficiently loaded, stored, or operated upon by the hardware. Machine scalars
 consist of an integral number of storage elements. The set of machine scalars is
-implementation-dependent, but must include at least the storage element and the
+implementation defined, but must include at least the storage element and the
 word. [Machine scalars are used to interpret component_clauses when the
 nondefault bit ordering applies.]
 
-The set of machine scalars is implementation defined.
-
 
 Add after 13.5.1(10)
 
@@ -78,7 +79,7 @@
 
 A record_representation_clause (without the mod_clause) specifies the layout.
 
-If the default bit ordering applies to the type, the position, first_bit and
+If the default bit ordering applies to the type, the position, first_bit, and
 last_bit of each component_clause directly specify the position and size of the
 corresponding component.
 
@@ -89,7 +90,7 @@
 equal to the size of the largest machine scalar directly specify the position
 and size of the corresponding component;
 
-o   for the other component_clauses, all the components having the same value of
+o   for other component_clauses, all the components having the same value of
 position are considered to be part of a single machine scalar, located at that
 position; this machine scalar has a size which is the smallest machine scalar
 size larger than the largest last_bit for all component_clauses at that
@@ -144,7 +145,7 @@
 Add after 13.5.3(8):
 
 NOTE: Bit_Order clauses make it possible to write record_representation_clauses
-that can be ported between machines having different bit ordering. They don't
+that can be ported between machines having different bit ordering. They do not
 guarantee transparent exchange of data between such machines.
 
 
@@ -271,8 +272,8 @@
 a machine scalar, or within a single byte of memory, but not between bits in
 different bytes of memory. The reason is that, on different target machines,
 bytes are loaded in different order to compose a machine scalar. If we want to
-be able to write endian-independent record representation clauses, we must
-cannot interpret large bit numbers with respect to the memory representation. We
+be able to write endian-independent record representation clauses, we cannot
+interpret large bit numbers with respect to the memory representation. We
 can only interpret them with respect to machine scalars.
 
 Therefore, we adopt the following convention: in a record-representation clause
@@ -320,10 +321,9 @@
 A @i<machine scalar> is an amount of storage that can be conveniently and
 efficiently loaded, stored, or operated upon by the hardware. Machine scalars
 consist of an integral number of storage elements. The set of machine scalars is
-implementation-dependent, but must include at least the storage element and the
-word. Machine scalars are used to interpret component_clauses when the
-nondefault bit ordering applies. The set of machine scalars is implementation
-defined.
+implementation defined, but must include at least the storage element and the
+word. Machine scalars are used to interpret @fa<component_clause>s when the
+nondefault bit ordering applies.
 
 
 !corrigendum 13.5.1(10)
@@ -352,7 +352,7 @@
 layout.
 
 If the default bit ordering applies to the type, the @fa<position>,
-@fa<first_bit> and @fa<last_bit> of each @fa<component_clause> directly specify
+@fa<first_bit>, and @fa<last_bit> of each @fa<component_clause> directly specify
 the position and size of the corresponding component.
 
 If the nondefault bit ordering applies to the type then the layout is
@@ -362,7 +362,7 @@
 greater than or equal to the size of the largest machine scalar directly
 specify the position and size of the corresponding component;>
 
-@xbullet<for the other @fa<component_clause>s, all the components having the
+@xbullet<for other @fa<component_clause>s, all the components having the
 same value of @fa<position> are considered to be part of a single machine
 scalar, located at that @fa<position>; this machine scalar has a size which is
 the smallest machine scalar size larger than the largest @fa<last_bit> for all
@@ -440,7 +440,7 @@
 @xindent<@s9<NOTES@hr
 13 Bit_Order clauses make it possible to write
 @fa<record_representation_clause>s that can be ported between machines having
-different bit ordering. They don't guarantee transparent exchange of data
+different bit ordering. They do not guarantee transparent exchange of data
 between such machines.>>
 
 !ACATS Test

Questions? Ask the ACAA Technical Agent