CVS difference for ais/ai-00089.txt
--- ais/ai-00089.txt 2000/04/14 01:45:06 1.4
+++ ais/ai-00089.txt 2000/07/13 04:31:27 1.5
@@ -17,8 +17,8 @@
It is a bounded error to invoke Value with a string that is not the
image of any generator. If the error is detected, Constraint_Error or
Program_Error is raised. Otherwise, a call to Reset with the resulting
-State will produce a Generator such that calls to Random with this
-Generator will produce a sequence of values of the appropriate subtype,
+State will produce a generator such that calls to Random with this
+generator will produce a sequence of values of the appropriate subtype,
but which might not be random in character. That is, the sequence of
values might not fulfill the requirements of A.5.2(41-43).
@@ -29,11 +29,11 @@
Invoking Value with a string that is not the image of any generator
state raises Constraint_Error.
-Is it legal to allow some extra flexibility? For example, suppose the
+Is it legal to allow some extra flexibility? (Yes.) For example, suppose the
Image function returns a representation of the state as a string of
-hexadecimal digits, with 'A'..'F' in upper case. A string with 'a'..'f'
+hexadecimal digits, with 'A'..'F' in upper case. A string with 'a'..'f'
in lower case, but which is otherwise equivalent to a valid image, is
-not strictly speaking "the image of any generator state". May the Value
+not strictly speaking "the image of any generator state". May the Value
function nevertheless return a valid state for such a string, or must it
raise Constraint_Error?
@@ -48,16 +48,16 @@
!discussion
A.5.2(40) seems to imply that the implementation must detect strings
-that could not have been produced by Image. However, for some kinds of
+that could not have been produced by Image. However, for some kinds of
random number generators, such detection is prohibitively expensive.
-Therefore, we choose to make this situation a bounded error. If the
+Therefore, we choose to make this situation a bounded error. If the
given string is syntactically malformed, the implementation will
-probably raise an exception. However, some strings might "look right",
+probably raise an exception. However, some strings might "look right",
but produce a generator state that could never come from a valid seed,
and results in non-random numbers.
There is no need to make the situation erroneous -- the implementation
-shouldn't write on random memory locations, or take wild jumps. The
+shouldn't write to random memory locations, or take wild jumps. The
worst that can happen is that a non-random sequence of numbers (for
example, a sequence of zeros) will be produced.
@@ -88,7 +88,7 @@
state will produce a generator such that calls to Random with this
generator will produce a sequence of values of the appropriate subtype,
but which might not be random in character. That is, the sequence of
-values might not fulfill the implementation requirements of this clause.
+values might not fulfill the implementation requirements of this subclause.
!ACATS test
Questions? Ask the ACAA Technical Agent