CVS difference for arm/source/06.mss

Differences between 1.23 and version 1.24
Log of other versions for file arm/source/06.mss

--- arm/source/06.mss	2000/09/27 00:15:09	1.23
+++ arm/source/06.mss	2004/10/30 21:51:42	1.24
@@ -1,10 +1,10 @@
 @Part(06, Root="ada.mss")
-@Comment{$Date: 2000/09/27 00:15:09 $}
+@Comment{$Date: 2004/10/30 21:51:42 $}
 @Comment{$Source: e:\\cvsroot/ARM/Source/06.mss,v $}
-@Comment{$Revision: 1.23 $}
+@Comment{$Revision: 1.24 $}
@@ -678,7 +678,7 @@
 @Defn{calling convention}
 @Redundant[As explained in @RefSec{Interfacing Pragmas},
@@ -816,7 +816,7 @@
 @Defn2{Term=[calling convention], Sec=(entry)}
 The default calling convention is @i{entry} for an entry.
 @Chg{New=[@Redundant[If not specified above as Intrinsic, the calling convention for any
 inherited or overriding dispatching operation of a tagged type is that of the
 corresponding subprogram of the parent type.] The default calling convention
@@ -945,7 +945,7 @@
 different @nt{default_expression}s.
 @Chg{New=[each @nt{attribute_designator} in one must be the same as the
 corresponding @nt{attribute_designator} in the other; and],Old=[]}
@@ -1003,6 +1003,17 @@
 conforms fully with "(X: T; Y: T)",
 and "(X: T)" conforms fully with "(X: @key[in] T)".
+@Chg{Version=[2],New=[@b<Corrigendum:> Clarified that the default convention is
+Ada. Also clarified that the convention of a primitive operation of a tagged
+type is the same as that of the type.],Old=[]}
+@Chg{Version=[2],New=[@b<Corrigendum:> Added wording to insure that two
+attributes conform only if they have the same @nt{attribute_designator}.],Old=[]}
 @LabeledSubClause{Inline Expansion of Subprograms}

Questions? Ask the ACAA Technical Agent