CVS difference for ais/ai-00108.txt

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

--- ais/ai-00108.txt	2000/07/13 04:31:27	1.12
+++ ais/ai-00108.txt	2000/08/01 05:39:33	1.13
@@ -1,4 +1,4 @@
-!standard 13.13.02 (09)                               00-07-07  AI95-00108/07
+!standard 13.13.02 (09)                               00-07-31  AI95-00108/08
 !standard 13.13.02 (27)
 !standard 13.13.02 (36)
 !class binding interpretation 96-04-04
@@ -119,6 +119,8 @@
 when we can't do the right thing automatically, which minimizes the places
 where existing code becomes illegal).
 
+To see how this works in practice, consider the following example:
+
    package P is
       type T is limited tagged ...;
       for T'Read use ...;
@@ -129,9 +131,9 @@
       type Der_Int is new T with -- OK (non-limited extension components,
                                  --  T'Read is inherited with the additional
                                  --  components added)
-      record
-         Int : Integer;
-      end record;
+         record
+            Int : Integer;
+         end record;
 
       protected type Protect_Type is ... -- Note: no 'Read specified.
 
@@ -139,9 +141,9 @@
                                     -- Der_Protect_Type'Read is specified;
                                     -- we can't compose T'Read, as
                                     -- Protect_Type'Read can't be called.
-      record
-          PT : Protect_Type;
-      end record;
+         record
+            PT : Protect_Type;
+         end record;
    end P;
 
 Simply making the operation uncallable doesn't work, as the operations can be
@@ -196,7 +198,7 @@
 of the type or subtype.
 
 In contrast, whether operational aspects are inherited for a derived type
-depends on the specific aspect. When operational aspects are inherited for a
+depends on each specific aspect. When operational aspects are inherited for a
 derived type, aspects that were directly specified before the declaration of the
 derived type, or (in the case where the parent is derived) that were inherited
 by the parent type from the grandparent type are inherited. An inherited
@@ -206,8 +208,8 @@
 !corrigendum 13.1(18)
 
 @dinsa
-@xbullet<If an aspect of representation is not specified, it is chosen by
-default in an unspecified manner.>
+@xbullet<If an aspect of representation of an entity is not specified, it is
+chosen by default in an unspecified manner.>
 @dinst
 If an operational aspect is @i<specified> for an entity (meaning that it is
 either directly specified or inherited), then that aspect of the entity is as
@@ -245,11 +247,11 @@
 For untagged derived types, the Write and Read attributes of the parent type
 are inherited as specified in 13.1; otherwise, the default implementations of
 these attributes are used.
-The default implementation of Write and Read attributes is defined as follows:
+The default implementations of Write and Read attributes execute as follows:
 
 For elementary types, the representation in terms of stream elements is
 implementation defined. For composite types, the Write or Read attribute for
-each component is called in a canonical order, which is
+each component is called in canonical order, which is
 last dimension varying fastest for an array, and positional
 aggregate order for a record. Bounds are not included in the stream if @i<T> is
 an array type. If @i<T> is a discriminated type, discriminants are included only
@@ -270,8 +272,8 @@
 @dby
 For untagged derived types, the Output and Input attributes of the parent type
 are inherited as specified in 13.1; otherwise, the default implementations of
-the attributes are used. The default implementation of the Output and Input
-operations execute as follows:
+these attributes are used. The default implementations of Output and Input
+attributes execute as follows:
 
 !corrigendum 13.13.02(36)
 

Questions? Ask the ACAA Technical Agent