1 
 2 09/23/87  any_to_any_
 3 Known errors in the current release of any_to_any_.
 4 #         Associated TR's
 5 Description
 6 
 7 2  phx20125
 8 any_to_any_ invalidly permits certain characters to escape detection in
 9 conversion of characters to a numeric form through the char_to_numeric_
10 entry point (through assign_, any_to_any_ and some other paths).
11 
12 This occurs because the valid character detection occurs after the
13 incoming string has been rtrimmed.  The table used by the tctr, which
14 does the rtrim, is short and suitable for use only if characters exist
15 within the valid span of characters for numeric entry.  The problem
16 reported occurs when a character falls outside this range and hits a 0
17 byte within a following table, thus looking like a blank and getting
18 trimmed, rather than detected.
19 
20 When this occurs the incoming string appears to be null and is then
21 co-erced to appear to be 0.  This error does not occur in the
22 char-to-bit conversion, since this is done in a separate portion of
23 any_to_any_.
24 
25 1  phx19826
26 Any_to_any_, called either through assign_ or as an operator call
27 direct from pl1_operators_ causes an IPR fault in conversion of a
28 +000..000 fixed decimal value to a scaled fixed binary or scaled fixed
29 binary unsigned value.  This occurs since the special case of 0, with a
30 large precision, skips around code to correctly set the length of the
31 string (into x4).