CVS difference for arm/source/06.mss

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

--- arm/source/06.mss	2005/03/25 07:15:59	1.40
+++ arm/source/06.mss	2005/04/05 23:37:46	1.41
@@ -1,10 +1,10 @@
 @Part(06, Root="ada.mss")
 
-@Comment{$Date: 2005/03/25 07:15:59 $}
+@Comment{$Date: 2005/04/05 23:37:46 $}
 @LabeledSection{Subprograms}
 
 @Comment{$Source: e:\\cvsroot/ARM/Source/06.mss,v $}
-@Comment{$Revision: 1.40 $}
+@Comment{$Revision: 1.41 $}
 
 @begin{Intro}
 @Defn{subprogram}
@@ -1125,26 +1125,28 @@
   corresponding @nt<entry_index_specification> of the @nt<entry_body>.
 @end{Discussion}
 
-@ChgRef{Version=[2],Kind=[Added],ARef=[AI95-00345-01]}
-@Chg{Version=[2],New=[Two subprograms or entries are @i<type conformant>
-(respectively @i<mode conformant>, @i<subtype conformant>, or @i<fully
-conformant>) if their profiles are type conformant (respectively mode
-conformant, subtype conformant, or fully conformant).
-@Defn2{Term=[type conformance], Sec=(for subprograms)}
-@Defn2{Term=[type conformance], Sec=(for entries)}
-@Defn2{Term=[mode conformance], Sec=(for subprograms)}
-@Defn2{Term=[mode conformance], Sec=(for entries)}
-@Defn2{Term=[subtype conformance], Sec=(for subprograms)}
-@Defn2{Term=[subtype conformance], Sec=(for entries)}
-@Defn2{Term=[full conformance], Sec=(for subprograms)}
-@Defn2{Term=[full conformance], Sec=(for entries)}],Old=[]}
+@ChgRef{Version=[2],Kind=[Added],ARef=[AI95-00345-01],ARef=[AI95-00397-01]}
+@ChgAdded{Version=[2],Text=[@Defn{prefixed view profile}
+The @i<prefixed view profile> of a subprogram is the profile obtained by
+omitting the first parameter of that subprogram. There is no prefixed view
+profile for a parameterless subprogram. For the purposes of defining subtype
+and mode conformance, the convention of a prefixed view profile is considered
+to match that of either an entry or a protected operation.]}
+
 @begin{Discussion}
-  @ChgRef{Version=[2],Kind=[AddedNormal],ARef=[AI95-00345-01]}
-  @ChgAdded{Version=[2],Text=[This definition is used to define the conformance
-  required for interfaces used in task and protected type definitions (see
-  @RefSecNum{Task Units and Task Objects} and
+  @ChgRef{Version=[2],Kind=[AddedNormal]}
+  @ChgAdded{Version=[2],Text=[This definition is used to define how
+  primitive subprograms of interfaces match operations in task and
+  protected type definitions (see @RefSecNum{Task Units and Task Objects} and
   @RefSecNum{Protected Units and Protected Objects}).]}
 @end{Discussion}
+@begin{Reason}
+  @ChgRef{Version=[2],Kind=[AddedNormal]}
+  @ChgAdded{Version=[2],Text=[The weird rule about conventions is pretty much
+  required for synchronized interfaces to make any sense. There will be
+  wrappers all over the place for interfaces anyway. Of course, this doesn't
+  imply that entries have the same convention as protected operations.]}
+@end{Reason}
 @end{StaticSem}
 
 @begin{ImplPerm}
@@ -1182,9 +1184,9 @@
   @ChgAdded{Version=[2],Text=[Defined the conformance of access result types
   (see @RefSecNum{Subprogram Declarations}).]}
 
-  @ChgRef{Version=[2],Kind=[AddedNormal],ARef=[AI95-00345-01]}
-  @ChgAdded{Version=[2],Text=[Defined the conformance of subprograms and
-  entries.]}
+  @ChgRef{Version=[2],Kind=[AddedNormal],ARef=[AI95-00345-01],ARef=[AI95-00397-01]}
+  @ChgAdded{Version=[2],Text=[Defined the prefixed view profile of subprograms
+  for later use.]}
 
   @ChgRef{Version=[2],Kind=[AddedNormal],ARef=[AI95-00409-01]}
   @ChgAdded{Version=[2],Text=[Defined the conformance of anonymous

Questions? Ask the ACAA Technical Agent