CVS difference for ais/ai-00256.txt
--- ais/ai-00256.txt 2001/02/16 05:08:17 1.2
+++ ais/ai-00256.txt 2001/03/15 23:54:52 1.3
@@ -1,5 +1,6 @@
-!standard 13.11.01 (01) 01-02-12 AI95-00256/01
+!standard 13.11.01 (01) 01-03-15 AI95-00256/02
!standard A.12.01 (30)
+!standard G.02.02 (03)
!class binding interpretation 01-02-12
!status work item 01-02-12
!status received 01-02-12
@@ -11,9 +12,9 @@
!summary
(Note: This AI contains various wording changes that ought to be made to the
-standard for which there is no opposition to the change. The intent is that
-this AI will only be processed when a Corrigendum or Revision is about to
-be issued.)
+standard for which there is expected to be no opposition to the change. The
+intent is that this AI will only be processed when a Corrigendum or Revision
+is about to be issued.)
1) The value of the Size_In_Storage_Elements is the maximum value that could be
requested by the implementation.
@@ -21,6 +22,9 @@
2) Ada.Streams.Read (and Write) without an index parameter read
(or write) at the current index if the file supports positioning.
+3) The rule of 3.5.8(2/1) applies in G.2.2(3) as well. (Otherwise the RM is
+inconsistent.)
+
!question
1)
@@ -45,6 +49,11 @@
intent is that stream files with positioning act like Dirct_IO files. Is
it OK for an implementation to ignore the current index of a stream file? (No.)
+3)
+The Technical Corrigendum fixes 3.5.8(2), which links 'Digits and
+'Model_Mantissa. But it does not fix G.2.2(3), which
+contains essentially the same formula. Was this intended? (No.)
+
!recommendation
(See summary.)
@@ -67,6 +76,10 @@
with that Defect Report failed to say where Read and Write without an index
parameter read or write. Compare A.12.1(30) to A.8.5(3) to see the missing text.
+3)
+Defect Report 8652/0004 clearly states that the intent of the language is as
+specified in 3.5.8(2/1). The failure to change the related paragraph G.2.2(3)
+as well is just an oversight.
!corrigendum 13.11.01(03)
@@ -99,13 +112,35 @@
and Write without a Positive_Count parameter starts writing at the current
index.
+!corrigendum G.2.2(3)
+
+@drepl
+Yields the number of digits in the mantissa of the canonical form of the model
+numbers of @i<T> (see A.5.3). The value of this attribute shall be greater
+than or equal to @i<Ceiling>(@i<d> ú log(10) / log(T'Machine_Radix)) + 1,
+where @i<d> is the requested decimal precision of @i<T>. In addition, it shall
+be less than or equal to the value of @i<T>'Machine_Mantissa. This attribute
+yields a value of the type @i<universal_integer>.
+@dby
+Yields the number of digits in the mantissa of the canonical form of the model
+numbers of @i<T> (see A.5.3). The value of this attribute shall be greater
+than or equal to
+@xindent<@i<ceiling>(@i<d> * log(10) / log(T'Machine_Radix)) + @i<g>@hr
+where @i<d> is the requested decimal precision of @i<T>, and @i<g> is 0 if
+Machine_Radix is a positive power of 10 and 1 otherwise.> In addition, it shall
+be less than or equal to the value of @i<T>'Machine_Mantissa. This attribute
+yields a value of the type @i<universal_integer>.
+
!ACATS test
1) The existing test CDB0A02 tests Size_In_Stream_Elements.
-2) A test should be created that insures that Read and Write operate properly.
-(This probably will be done as part of the objective for 8652/0055.)
+2) Test CXAC005 (which checks the objective for 8652/0055) also checks this
+rule.
+3) The ARG voted to not test the change to 3.5.8(2) (because it applies to very
+few machines), and that vote applies here as well.
+
!appendix
From: Randy Brukardt
@@ -124,5 +159,16 @@
I would assume the above is non-controversial, but since quite a few
compilers ignore it, perhaps I'm wrong.
+
+****************************************************************
+
+From: Pascal Leroy
+Sent: Thursday, January 18, 2001 8:09 AM
+
+I am noticing that DR 0004 fixes 3.5.8(2), which links 'Digits and
+'Model_Mantissa. It seems that it should also have fixed G.2.2(3), which
+contains essentially the same formula.
+
+Oh well...
****************************************************************
Questions? Ask the ACAA Technical Agent