CVS difference for arm/source/safety.mss

Differences between 1.4 and version 1.5
Log of other versions for file arm/source/safety.mss

--- arm/source/safety.mss	2000/04/19 00:07:04	1.4
+++ arm/source/safety.mss	2000/04/20 02:30:30	1.5
@@ -1,9 +1,9 @@
 @Comment{ $Source: e:\\cvsroot/ARM/Source/safety.mss,v $ }
-@Comment{ $Revision: 1.4 $ $Date: 2000/04/19 00:07:04 $ $Author: Randy $ }
+@Comment{ $Revision: 1.5 $ $Date: 2000/04/20 02:30:30 $ $Author: Randy $ }
 @Part(safety, Root="ada.mss")
 @Modify(Appendix, Numbered <@A.>, Referenced <@A>)
-@SetPageHeadings{$Date: 2000/04/19 00:07:04 $}
+@SetPageHeadings{$Date: 2000/04/20 02:30:30 $}
 @LabeledNormativeAnnex{Safety and Security}
@@ -116,7 +116,7 @@
 Whenever possible, the implicit initial value for a scalar subtype
 should be an invalid representation
-(@lSeeSecNum{Data Validity}).
+(see @RefSecNum{Data Validity}).
 When an out of range value is used for the initialization,
@@ -139,11 +139,11 @@
 pragma Import has been specified,
 since initialization of an imported object is performed
 solely by the foreign language environment
- (@lSeeSecNum[Interfacing Pragmas]).
+ (see @RefSecNum[Interfacing Pragmas]).
 The use of pragma Normalize_Scalars  in conjunction with
 Pragma Restrictions(No_Exceptions) may result in erroneous execution
-(@lSeeSecNum[Safety and Security Restrictions]).
+(see @RefSecNum[Safety and Security Restrictions]).
 Since the effect of an access to an out of range value will often be to
@@ -196,7 +196,7 @@
 using the abort statement, so that the effects of a partly completed
 @nt{assignment_statement} do not have to be considered in the validation of a
-(@lSeeSecNum{Abort of a Task - Abort of a Sequence of Statements}).
+(see @RefSecNum{Abort of a Task - Abort of a Sequence of Statements}).
 For this reason documentation linked to an actual compilation may be
 most useful. Similarly, an implementation may be able to take into
 account use of the Restrictions pragma.
@@ -432,7 +432,7 @@
 The order of elaboration of library units will be documented
 even in the absence of @nt[pragma] Reviewable
-(@lSeeSecNum{Program Execution}).
+(see @RefSecNum{Program Execution}).
@@ -525,7 +525,7 @@
 Reaching an inspection point is an external interaction
 with respect to the values
 of the inspectable objects at that point
-(@lSeeSecNum{Conformity of an Implementation with the Standard}).
+(see @RefSecNum{Conformity of an Implementation with the Standard}).
 @Ramification{The compiler is inhibited from moving an assignment to
 an inspectable variable past an inspection point for that variable.
 On the other hand, the evaluation of an expression that might raise

Questions? Ask the ACAA Technical Agent