CVS difference for ais/ai-00166.txt

Differences between 1.8 and version 1.9
Log of other versions for file ais/ai-00166.txt

--- ais/ai-00166.txt	2000/04/14 01:45:08	1.8
+++ ais/ai-00166.txt	2000/06/20 04:22:43	1.9
@@ -66,39 +66,40 @@
 treatment that is initially in place when a program starts up is
 unlikely to be calling an Ada protected procedure.
 
-The intent of RM95 to allow treatments other than parameterless
-protected procedures as defaults is expressed clearly in C.2 (5):
+The intent of the International Standard is to allow treatments other
+than parameterless protected procedures as defaults is expressed
+clearly in C.3 (5):
+
+  5 Each interrupt has a default treatment which determines the
+  system's response to an occurrence of that interrupt when no
+  user-defined handler is attached.  The set of possible default
+  treatments is implementation defined, as is the method (if one
+  exists) for configuring the default treatments for interrupts.
 
-| 5 Each interrupt has a default treatment which determines the
-| system's response to an occurrence of that interrupt when no
-| user-defined handler is attached.  The set of possible default
-| treatments is implementation defined, as is the method (if one
-| exists) for configuring the default treatments for interrupts.
-
 Note that the default treatment of an interrupt is not even
 required to be static.  It is possible that an implementation or
 underlying operating system may have a mechanism that modifies the
 default treatment of an interrupt (or signal) while a program is
 running.
 
-C.2 (29) gives implementation advice as to examples of possible
+C.3 (29) gives implementation advice as to examples of possible
 default treatments, but does not limit them:
 
-| 29 (1) The default treatment for an interrupt can be to keep the
-| interrupt pending or to deliver it to an implementation-defined
-| handler.  Examples of actions that an implementation-defined
-| handler is allowed to perform include aborting the partition,
-| ignoring (i.e., discarding occurrences of) the interrupt, or
-| queuing one or more occurrences of the interrupt for possible
-| later delivery when a user-defined handler is attached to that
-| interrupt.
+  29 (1) The default treatment for an interrupt can be to keep the
+  interrupt pending or to deliver it to an implementation-defined
+  handler.  Examples of actions that an implementation-defined
+  handler is allowed to perform include aborting the partition,
+  ignoring (i.e., discarding occurrences of) the interrupt, or
+  queuing one or more occurrences of the interrupt for possible
+  later delivery when a user-defined handler is attached to that
+  interrupt.
 
 Moreover, the intent of the ARM is to allow user-specified
 handlers that are not parameterless protected procedures, as
 specified in C.3 (26)
 
-| 26 Other forms of handlers are allowed to be supported, in which
-| case, the rules of this subclause should be adhered to.
+  26 Other forms of handlers are allowed to be supported, in which
+  case, the rules of this subclause should be adhered to.
 
 For example, it would be legal for an implementation to define a
 way to attach an ordinary procedure to an interrupt, or in the
@@ -109,19 +110,19 @@
 
 This is emphasized in C.3.1 (19):
 
-| 19 Notwithstanding what this subclause says elsewhere, the
-| Attach_Handler and Interrupt_Handler pragmas are allowed to be
-| used for other, implementation defined, forms of interrupt
-| handlers.
+  19 Notwithstanding what this subclause says elsewhere, the
+  Attach_Handler and Interrupt_Handler pragmas are allowed to be
+  used for other, implementation defined, forms of interrupt
+  handlers.
 
 and again in C.3.2 (25):
 
-| 25 If implementation-defined forms of interrupt handler
-| procedures are supported, such as protected procedures with
-| parameters, then for each such form of a handler, a type
-| analogous to Parameterless_Handler should be specified in a
-| child package of Interrupts, with the same operations as in the
-| predefined package Interrupts.
+  25 If implementation-defined forms of interrupt handler
+  procedures are supported, such as protected procedures with
+  parameters, then for each such form of a handler, a type
+  analogous to Parameterless_Handler should be specified in a
+  child package of Interrupts, with the same operations as in the
+  predefined package Interrupts.
 
 This means that if an implementation supports handlers or other
 interrupt treatments (whether default or user-specified)
@@ -157,7 +158,7 @@
 previous treatment, without needing to worry about whether the
 previous treatment is a parameterless protected procedure.
 
-This intent is reflected in the first sentence of C.3.1 (16),
+This intent is reflected in the first sentence of C.3.2 (16),
 which says Current_Handler returns a value that "represents" the
 attached handler, rather than "designates".  It is unfortunate
 that the word "designates" was inadvertently substituted in the
@@ -181,13 +182,13 @@
 model.  The ARM itself does not explicitly specify how this can be
 determined, but it can be interpreted in a way that may suffice.
 
-ARM95 C.3.1 (17) does require that the null access value can be
+C.3.2 (17) does require that the null access value can be
 used to specify the default treatment for an interrupt:
 
-| 17 The Attach_Handler procedure attaches the specified handler
-| to the interrupt, overriding any existing treatment (including a
-| user handler) in effect for that interrupt.  If New_Handler is
-| null, the default treatment is restored. ...
+  17 The Attach_Handler procedure attaches the specified handler
+  to the interrupt, overriding any existing treatment (including a
+  user handler) in effect for that interrupt.  If New_Handler is
+  null, the default treatment is restored. ...
 
 This binding interpretation extrapolates from the above to
 conclude that the value returned by Current_Handler, and the value

Questions? Ask the ACAA Technical Agent