CVS difference for arm/source/10.mss

Differences between 1.101 and version 1.102
Log of other versions for file arm/source/10.mss

--- arm/source/10.mss	2012/03/20 06:13:58	1.101
+++ arm/source/10.mss	2012/11/28 23:53:04	1.102
@@ -1,15 +1,16 @@
 @Part(10, Root="ada.mss")
-@Comment{$Date: 2012/03/20 06:13:58 $}
+@Comment{$Date: 2012/11/28 23:53:04 $}
 @LabeledSection{Program Structure and Compilation Issues}
 @Comment{$Source: e:\\cvsroot/ARM/Source/10.mss,v $}
-@Comment{$Revision: 1.101 $}
+@Comment{$Revision: 1.102 $}
 @Comment{Corrigendum changes added, 2000/04/24, RLB}
 @redundant[The overall structure of programs and the facilities for separate
-compilation are described in this section.
+compilation are described in this @Chg{Version=[3],New=[clause],Old=[section]}.
 A @i(program) is a set of @i(partitions), each of which
 may execute in a separate address space, possibly on a separate
@@ -42,7 +43,9 @@
 Library units may be organized into a hierarchy of
 children, grandchildren, and so on.]
-This section has two clauses:
+This @Chg{Version=[3],New=[clause],Old=[section]} has two
 @RefSec{Separate Compilation}
 discusses compile-time issues related to separate compilation.
 @RefSec{Program Execution}
@@ -89,9 +92,9 @@
-The section organization mentioned above is different from that of
+The @Chg{Version=[3],New=[clause],Old=[section]} organization mentioned above is
+different from that of RM83. @end{DiffWord83}
 @LabeledClause{Separate Compilation}
@@ -1103,13 +1106,15 @@
 the @nt{with_clause}.],Old=[]}
- @nt{With_clause}s control the visibility of
+@nt{With_clause}s control the visibility of
 declarations or renamings of library units.
 Mentioning a root library unit in a
 @nt{with_clause} makes its declaration
 directly visible. Mentioning a nonroot library unit
 makes its declaration visible.
-See Section 8 for details.
+See @Chg{Version=[3],New=[Clause],Old=[Section]} @RefSecNum{Visibility Rules}
+for details.
 Note that this rule implies that @lquotes@;@key{with} A.B.C;@rquotes@; is
@@ -2082,8 +2087,9 @@
 @nt{compilation} and compilation unit boundaries,
 just as they are enforced within a single compilation unit.
-Note that Section 1 requires an implementation to detect illegal
-compilation units at compile time.
+Note that @Chg{Version=[3],New=[Clause],Old=[Section]} @RefSecNum{General}
+requires an implementation to detect illegal compilation units at compile time.
@@ -2962,9 +2968,10 @@
 @Defn{active partition}
-The kind of partition described in this clause is known as an
-@i{active} partition.
+The kind of partition described in this @Chg{Version=[3],New=[subclause],Old=[clause]}
+is known as an @i{active} partition.
 An implementation is allowed to support other kinds of partitions,
 with implementation-defined semantics.
 @ImplDef{The semantics of any nonactive partitions supported by the
@@ -3737,7 +3744,7 @@
 produces other side effects when called.]
 A declared-pure @nt{library_item} has no variable state.
 Hence, a call on one of its (nonnested) subprograms cannot
@@ -3750,7 +3757,7 @@
 @Chg{Version=[3],New=[ and ],Old=[]}],Old=[]}unchecked conversion to an access type declared within the
 subprogram@Chg{Version=[3],New=[; this list is not exhaustive],Old=[, and
 similar features]}.@Chg{Version=[3],New=[ Thus, the permissions described
-in this section may apply to a subprogram whose execution has
+in this subclause may apply to a subprogram whose execution has
 side effects.],Old=[]} The compiler may omit a call to such a subprogram
 even if @Chg{Version=[3],New=[],Old=[such]} side effects exist, so the
 writer of such a subprogram has to keep this in mind.

Questions? Ask the ACAA Technical Agent