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

Differences between 1.3 and version 1.4
Log of other versions for file ai05s/ai05-0083-1.txt

--- ai05s/ai05-0083-1.txt	2008/07/11 04:00:05	1.3
+++ ai05s/ai05-0083-1.txt	2008/10/25 04:53:14	1.4
@@ -1,5 +1,5 @@
-!standard 13.1(11/2)                                       08-07-10    AI05-0083-1/03
-!standard 13.4(22/2)
+!standard 13.1(11/2)                                       08-10-21    AI05-0083-1/04
+!standard 13.3(22/2)
 !standard 13.3(40)
 !class ramification 08-02-10
 !status ARG Approved  7-0-1  08-06-21
@@ -18,7 +18,7 @@
-Does 13.3(22/2) and 13.3(40/1) mean "view of an object" rather than just
+Does 13.3(22/2) and 13.3(40) mean "view of an object" rather than just
 "object"? (Yes.)
 Generally, Section 13 text says "view" when it means it, and it usually does
@@ -57,7 +57,7 @@
 alignment, and it could even be larger than the object's alignment if, for
 instance, the target aligns all objects to alignment 8.
-These are very different answers, and the actual answer has impacts on
+These are very different answers, and the actual answer impacts
 code generation.
 Similar questions apply to Size and other attributes that can be specified for
@@ -77,6 +77,17 @@
 Alignment even though the formal parameter is merely a view of the
 actual object. This is necessary to maintain the language design principle
 that Alignments are always known at compile time.
+Add an AARM Ramification after 13.1(18.c):
+As noted previously, in the case of an object, the entity mentioned in
+this text is a specific view of an object. That means that only references
+to the same view of an object that has a specified value for a representation
+aspect R necessarily have that value for the aspect R. The value of the 
+aspect R for a different view of that object is unspecified. In particular,
+this means that the representation values for by-reference parameters is
+unspecified; they do not have to be the same as those of the underlying

Questions? Ask the ACAA Technical Agent