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

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

--- ai05s/ai05-0078-1.txt	2008/03/07 06:15:19	1.2
+++ ai05s/ai05-0078-1.txt	2008/05/10 05:14:33	1.3
@@ -1,4 +1,4 @@
-!standard 13.9(7)                                          08-02-22    AI05-0078-1/02
+!standard 13.9(7)                                          08-04-18    AI05-0078-1/03
 !class binding interpretation 07-12-06
 !status ARG Approved  7-0-1  08-02-09
 !status work item 07-12-06
@@ -12,13 +12,15 @@
 The alignment of the source object of an unchecked conversion need only
 be a multiple of that of the target type for unchecked conversion to have
-a defined result.
+a defined result. If the target alignment is zero, the alignment of the
+source object is not relevant to whether unchecked conversion has a
+defined effect.
 13.9(7) specifies that it is required that the source object and target
 type have identical alignment for an unchecked type conversion to have
-an language-defined effect.
+a language-defined effect.
 The intent of this rule appears to be to restrict the cases
 where an unchecked conversion has a language-defined effect to
@@ -49,6 +51,10 @@
 mismatched alignments even without this language change
 (implementation-defined surely includes working as expected).
 So this language change only provides a bit of additional portability.
+If the Target'Alignment is zero, multiples of that alignment are not
+well-defined; since alignment being zero imposes no restrictions, there
+is no reason for a requirement on S'Alignment.
 !corrigendum 13.9(7)

Questions? Ask the ACAA Technical Agent