CVS difference for ai05s/ai05-0295-1.txt

--- ai05s/ai05-0295-1.txt	2012/02/19 04:54:06	1.3
+++ ai05s/ai05-0295-1.txt	2012/03/16 03:07:45	1.4
@@ -1,4 +1,4 @@
-!standard  13.1(0)                               12-02-18    AI05-0295-1/02
+!standard  13.1(0)                               12-03-15    AI05-0295-1/03
 !standard   3.8(11)
 !standard  9.10(1)
 !standard  13.1(0.1/1)
@@ -23,6 +23,7 @@
 !standard  13.1.1(0)
 !class Amendment 12-02-15
 !status Amendment 2012 12-02-15
+!status ARG Approved 8-0-2  12-02-25
 !status work item 12-02-15
 !status received 12-01-12
 !priority Medium
@@ -66,8 +67,8 @@
 with:
     Otherwise, two nonoverlapping objects are independently addressable
     except when they are both parts of one composite object for which a
-    nonconfirming representation value is specified for any of the
-    following aspects: Layout, Component_Size, Pack, Atomic,
+    nonconfirming value is specified for any of the
+    following representation aspects: Layout, Component_Size, Pack, Atomic,
     or Convention; in this case, it is unspecified whether the parts
     are independently addressable.
 
@@ -82,7 +83,7 @@
    Two kinds of aspects of entities can be specified: representation
    aspects and operational aspects. Representation aspects affect how
    the types and other entities of the language are to be mapped onto
-   the underlying machine. Operational aspects determine to other properties
+   the underlying machine. Operational aspects determine other properties
    of entities.
 
    Either kind of aspect of an entity may be specified by means of an
@@ -90,7 +91,7 @@
    kinds of declarations and applies to the entity or entities being declared.
    Aspects may also be specified by certain other constructs occurring
    subsequent to the declaration of the affected entity: a representation aspect
-   value may be specified by means of an representation item and an
+   value may be specified by means of a representation item and an
    operational aspect value may be specified by means of an operational item.
 
 Replace AARM 13.1(1.a) with:
@@ -148,15 +149,15 @@
 
 Modify 13.1(13/1):
 
-{Specifying a}[A] representation or operational {aspect such}[item] that {the
-aspect} is not supported by the implementation is illegal, or raises an
+{If a specification of a}[A] representation or operational {aspect}[item that]
+is not supported by the implementation{, it} is illegal[,] or raises an
 exception at run time.
 
 Modify 13.1(13.1/2):
 
 A type_declaration is illegal if it has one or more progenitors, and
-a {nonconfirming} representation {value was specified for}[item applies to]
-an ancestor, and this representation {aspect}[item] conflicts with the
+a {nonconfirming value was specified for a} representation {aspect of}[item
+applies to] an ancestor, and this representation {aspect}[item] conflicts with the
 representation of some other ancestor. The cases that cause conflicts are
 implementation defined.
 
@@ -169,7 +170,7 @@
 specified somewhere. The simpler wording would allow any combination of types to
 be rejected if the implementation felt like it (since "conflicts" is
 implementation defined). Note that I did simplify the wording a bit, and brought
-in "nonconfirming".]
+in "nonconfirming". - Editor.]
 
 In AARM 13.1(14.a), replace
    Note that it is illegal to specify an aspect (including a
@@ -205,7 +206,7 @@
 
 Modify AARM 13.1(18.a/1):
 
-    Note that {specifying an } representation {aspect}[items] can affect
+    Note that {specifying a } representation {aspect}[items] can affect
     the semantics of the entity.
 
 Replace 13.1(18.2/2):
@@ -213,7 +214,7 @@
    would have been chosen in the absence of the representation item is said
    to be *confirming*.
 with:
-   A aspect_specification or representation item that specifies a
+   An aspect_specification or representation item that specifies a
    representation aspect that would have been chosen in the absence of the
    aspect_specification or representation item is said to be *confirming*. The
    aspect value specified in this case is said to be a
@@ -244,7 +245,7 @@
    Implementation defined: The interpretation of each [aspect of] representation
    {aspect}.
 
-Modify AARM 13.1(20.a):
+Modify AARM 13.1(20.b):
    Implementation defined: Any restrictions placed upon
    {the specification of} representation {aspects}[items].
 
@@ -257,18 +258,18 @@
    A confirming {specification for a} representation {aspect}[item]
    should be supported.
 
-Modify AARM 13.1(21.a.1/2):
+Modify AARM 13.1(21.a.1/2): [and drop the .1 from the number, it's not needed]
 
-   ... representation {value}[item] ...
+   ... representation {aspect value}[item] ...
 
 Modify 13.1(22):
 
-An implementation need not support representation items {or
-aspect_specifications for representation aspects} containing
-nonstatic expressions, except that an implementation should support a
-representation item {R or aspect_specification for a representation
-aspect S} for a given entity if each nonstatic expression in
-{R or S}[the representation item] is a name that statically denotes a constant
+An implementation need not support {the specification for a} representation
+{aspect that contains}[items containing]
+nonstatic expressions, {unless}[except that an
+implementation should support a
+representation item for a given entity if] each nonstatic expression [in
+the representation item] is a name that statically denotes a constant
 declared before the entity.
 
 Modify 13.1(24/2), 13.1(25/2), and 13.1(26/2):
@@ -323,7 +324,7 @@
 either object is specified as independently addressable (see C.6). Otherwise,
 two nonoverlapping objects are independently addressable
 except when they are both parts of a composite object for which
-a nonconfirming representation value is specified for any of the following
+a nonconfirming value is specified for any of the following representation
 aspects: (record) Layout, Component_Size, Pack, Atomic, or Convention; in
 this case it is unspecified whether the parts are independently addressable.
 
@@ -433,9 +434,8 @@
 A representation or operational item that is not supported by the implementation
 is illegal, or raises an exception at run time.
 @dby
-Specifying a representation or operational aspect such that the
-aspect is not supported by the implementation is illegal, or raises an
-exception at run time.
+If a specification of a representation or operational aspect is not supported by
+the implementation, it is illegal or raises an exception at run time.
 
 !corrigendum  13.1(13.1/2)
 
@@ -446,10 +446,9 @@
 cause conflicts are implementation defined.
 @dby
 A @fa<type_declaration> is illegal if it has one or more progenitors, and
-a nonconfirming representation value was specified for
-an ancestor, and this representation aspect conflicts with the
-representation of some other ancestor. The cases that cause conflicts are
-implementation defined.
+a nonconfirming value was specified for a representation aspect of an ancestor,
+and this conflicts with the representation of some other ancestor. The cases
+that cause conflicts are implementation defined.
 
 !corrigendum 13.1(15/1)
 
@@ -510,7 +509,7 @@
 would have been chosen in the absence of the representation item is said
 to be @i<confirming>.
 @dby
-A @fa<aspect_specification> or representation item that specifies a
+An @fa<aspect_specification> or representation item that specifies a
 representation aspect that would have been chosen in the absence of the
 @fa<aspect_specification> or representation item is said to be @i<confirming>.
 The aspect value specified in this case is said to be a
@@ -564,12 +563,9 @@
 representation item is a name that statically denotes a constant declared before
 the entity.>
 @dby
-@xbullet<An implementation need not support representation items or
-@fa<aspect_specification>s for representation aspects containing
-nonstatic expressions, except that an implementation should support a
-representation item @i<R> or @fa<aspect_specification> for a representation
-aspect @i<S> for a given entity if each nonstatic expression in @i<R> or @i<S>
-is a name that statically denotes a constant declared before the entity.>
+@xbullet<An implementation need not support the specification for a representation
+aspect that contains nonstatic expressions, unless each nonstatic expression
+is a @fa<name> that statically denotes a constant declared before the entity.>
 
 !corrigendum 13.1(24/2)