CVS difference for arm/source/04a.mss

Differences between 1.3 and version 1.4
Log of other versions for file arm/source/04a.mss

--- arm/source/04a.mss	2000/04/15 21:58:26	1.3
+++ arm/source/04a.mss	2000/04/19 00:07:02	1.4
@@ -1,17 +1,17 @@
 @Part(04, Root="ada.mss")
-@SetPageHeadings{$Date: 2000/04/15 21:58:26 $}
-@LabeledChapter{Names and Expressions}
+@SetPageHeadings{$Date: 2000/04/19 00:07:02 $}
+@LabeledSection{Names and Expressions}
 @Comment{$Source: e:\\cvsroot/ARM/Source/04a.mss,v $}
-@Comment{$Revision: 1.3 $}
+@Comment{$Revision: 1.4 $}
 @Redundant[The rules applicable to the different forms of @nt<name> and
 expression, and to their evaluation, are given in this section.]
@@ -237,7 +237,7 @@
 of implicit dereference.
-@LabeledSubSection{Indexed Components}
+@LabeledSubClause{Indexed Components}
 @Redundant[An @nt<indexed_component> denotes either
@@ -326,7 +326,7 @@
@@ -414,7 +414,7 @@
-@LabeledSubSection{Selected Components}
+@LabeledSubClause{Selected Components}
@@ -604,7 +604,7 @@
 new terminology, to accommodate class-wide types, etc.
@@ -726,7 +726,7 @@
-Attributes are defined throughout this @SelfRef,
+Attributes are defined throughout this International Standard,
 and are summarized in
 @RefSecNum{Language-Defined Attributes}.
@@ -814,7 +814,7 @@
   prefix (@lSeeSecNum(Operations of Access Types)).
@@ -976,7 +976,7 @@
@@ -1089,7 +1089,7 @@
 will work (@lSeeSecNum{User-Defined Assignment and Finalization}).
-@LabeledSubSection{Record Aggregates}
+@LabeledSubClause{Record Aggregates}
 @Redundant[In a @nt<record_aggregate>, a value is specified for
@@ -1385,7 +1385,7 @@
 a record aggregate.  Now we do.
-@LabeledSubSection{Extension Aggregates}
+@LabeledSubClause{Extension Aggregates}
 @Redundant[An @nt<extension_aggregate> specifies a value
@@ -1522,7 +1522,7 @@
 The extension aggregate syntax is new.
-@LabeledSubSection{Array Aggregates}
+@LabeledSubClause{Array Aggregates}
@@ -1921,13 +1921,13 @@
 and to incorporate the rulings of AI-19, AI-309, etc.
 An @i(expression) is a formula that defines the computation or retrieval
 of a value.
-In this @SelfRef, the term ``expression'' refers to a construct
+In this International Standard, the term ``expression'' refers to a construct
 of the syntactic category @nt<expression> or
 of any of the other five syntactic categories defined below.
 @Defn{and operator}@Defn2{Term=[operator],Sec=(and)}
@@ -2116,7 +2116,7 @@
 still have to be parenthesized when used in a bound of a range.
-@LabeledSection{Operators and Expression Evaluation}
+@LabeledClause{Operators and Expression Evaluation}
 @Redundant[@Defn{precedence of operators}
@@ -2272,7 +2272,7 @@
 it is closer to the rules defining operator association.
-@LabeledSubSection{Logical Operators and Short-circuit Control Forms}
+@LabeledSubClause{Logical Operators and Short-circuit Control Forms}
 @Defn{short-circuit control form}
@@ -2392,7 +2392,7 @@
-@LabeledSubSection{Relational Operators and Membership Tests}
+@LabeledSubClause{Relational Operators and Membership Tests}
@@ -2772,7 +2772,7 @@
 We have changed the term ``catenate'' to ``concatenate''.
-@LabeledSubSection{Binary Adding Operators}
+@LabeledSubClause{Binary Adding Operators}
 @Defn{binary adding operator}@Defn2{Term=[operator],Sec=(binary adding)}
@@ -2922,7 +2922,7 @@
 its lower bound is that of the index subtype.
-@LabeledSubSection{Unary Adding Operators}
+@LabeledSubClause{Unary Adding Operators}
 @Defn{unary adding operator}@Defn2{Term=[operator],Sec=(unary adding)}
@@ -2947,7 +2947,7 @@
 for a zero operand, the result is zero.
-@LabeledSubSection{Multiplying Operators}
+@LabeledSubClause{Multiplying Operators}
@@ -3198,7 +3198,7 @@
 rather than a tabular format.
-@LabeledSubSection{Highest Precedence Operators}
+@LabeledSubClause{Highest Precedence Operators}
 @Defn{highest precedence operator}@Defn2{Term=[operator],Sec=(highest precedence)}
@@ -3312,7 +3312,7 @@
 a negative value is provided for the exponent.
-@LabeledSection{Type Conversions}
+@LabeledClause{Type Conversions}
 @Redundant[Explicit type conversions, both
@@ -4005,7 +4005,7 @@
 as a @nt<name>.
-@LabeledSection{Qualified Expressions}
+@LabeledClause{Qualified Expressions}
 @Redundant[A @nt<qualified_expression> is used to state explicitly the type,
@@ -4079,7 +4079,7 @@
 @Redundant[The evaluation of an @nt<allocator> creates an object and yields
@@ -4291,7 +4291,7 @@
 has been moved to @RefSec{Storage Management}.
-@LabeledSection{Static Expressions and Static Subtypes}
+@LabeledClause{Static Expressions and Static Subtypes}
 Certain expressions of a scalar or string type are defined to be static.
@@ -4878,7 +4878,7 @@
-@LabeledSubSection{Statically Matching Constraints and Subtypes}
+@LabeledSubClause{Statically Matching Constraints and Subtypes}
 @Defn2{Term=[statically matching], Sec=(for constraints)}

Questions? Ask the ACAA Technical Agent