CVS difference for ais/ai-00105.txt

Differences between 1.2 and version 1.3
Log of other versions for file ais/ai-00105.txt

--- ais/ai-00105.txt	1998/09/30 23:25:09	1.2
+++ ais/ai-00105.txt	1999/07/21 03:10:57	1.3
@@ -1,4 +1,4 @@
-!standard 03.05.04 (09)                               98-06-12  AI95-00105/03
+!standard 03.05.04 (09)                               99-05-27  AI95-00105/04
 !class confirmation 96-04-04
 !status WG9 approved 98-06-12
 !status ARG Approved  9-0-0  98-04-01
@@ -8,14 +8,14 @@
 !difficulty Medium
 !subject extra negative value
 
-!summary 98-03-27
+!summary
 
 The RM does not specify whether implementations must support integer and
 fixed point types that allow the "extra negative value" of 3.5.4(9) and
 3.5.9(12).  There is no Implementation Advice as to whether or not such
 extra negative values should be supported on a two's complement machine.
 
-!question 96-04-04
+!question
 
 The following questions apply to implementations on two's complement
 machines.
@@ -36,12 +36,17 @@
 available size?  The Note in 3.5.9(22) explaining this permission
 implies that this wasn't the intent.
 
-!response 98-04-01
+!response
 
 (See summary.)
 
-!appendix 96-09-04
+!ACATS test
 
+No ACATS test is possible. Since this AI says that the RM does not specify the
+behavior, it is not testable.
+
+!appendix
+
 !section 3.5.4(09)
 !subject extra negative value
 !reference RM95-3.5.4(9)
@@ -99,7 +104,7 @@
 
 > The following questions apply to implementations on two's complement
 > machines.
-> 
+>
 > Should implementations support integer and fixed point types that allow
 > the "extra negative value" of 3.5.4(9) and 3.5.9(12)?
 
@@ -264,7 +269,7 @@
 !reference AARM95-13.3(55b)
 !reference 95-5370.a Dan Eilers  95-10-29
 !reference 96-5455.a Robert A Duff 96-4-8
-!reference 96-5514.a Dan Eilers 96-4-24 
+!reference 96-5514.a Dan Eilers 96-4-24
 !from Robert I. Eachus 96-4-26
 !reference 96-5515.a Robert I. Eachus 96-4-25>>
 !discussion
@@ -412,14 +417,14 @@
 !discussion
 
 > Bob's response seems to be inconsistent:
-> 
+>
 >      while he admits "I can imagine an implementation that used it for
 >      detecting uninitialized variables,"
-> 
+>
 >      he nevertheless insists that the implementation has to support
-> 
+>
 >         type T is range -4..3; for  T'Size use 3;
-> 
+>
 >      --so where does that leave an implementation model intended
 >      to detect unitialized variables, including components?
 

Questions? Ask the ACAA Technical Agent