CVS difference for arm/source/08.mss

Differences between 1.61 and version 1.62
Log of other versions for file arm/source/08.mss

--- arm/source/08.mss	2005/08/17 00:07:00	1.61
+++ arm/source/08.mss	2005/09/30 05:33:46	1.62
@@ -1,10 +1,10 @@
 @Part(08, Root="ada.mss")
-@Comment{$Date: 2005/08/17 00:07:00 $}
+@Comment{$Date: 2005/09/30 05:33:46 $}
 @LabeledSection{Visibility Rules}
 @Comment{$Source: e:\\cvsroot/ARM/Source/08.mss,v $}
-@Comment{$Revision: 1.61 $}
+@Comment{$Revision: 1.62 $}
 @redundant[The rules defining the scope of declarations and the rules defining
@@ -3105,11 +3105,14 @@
 in a class in scope.
-@Chg{Version=[2],New=[The part of the first sentence after the semicolon
-serves to define the "expected type" for constructs that don't have one (like
-qualified expressions and object renames). Otherwise, such constructs
-wouldn't allow @nt{aggregate}s, 'Access, and so on.],Old=[]}
+  @ChgRef{Version=[2],Kind=[Revised],ARef=[AI95-00332-01]}
+  @ChgAdded{Version=[2],Text=[The first sentence is carefully worded so that it
+  only mentions @lquotes@;expected type@rquotes as part of identifying the
+  interesting case, but doesn't require that the context actually provide such
+  an expected type. This allows such constructs to be used inside of constructs
+  that don't provide an expected type (like qualified expressions and renames).
+  Otherwise, such constructs wouldn't allow @nt{aggregate}s, 'Access, and so
+  on.]}
 A complete context shall have at least one acceptable interpretation;

Questions? Ask the ACAA Technical Agent