1 
 2 09/21/87  error_handlers
 3 Known errors in the current release of error_handlers.
 4 #         Associated TR's
 5 Description
 6 
 7 15  phx09049
 8 the message "exp(x), x > 88.028, not allowed" is not very helpful in
 9 cases where the exp function was used implicitly
10 
11 14  phx16162
12 The code in find_condition_info_ depends on the value of an
13 uninitialized flag.  This can cause a fault_tag_1 when the stack frame
14 pointer is null and there is no condition frame.
15 
16 13  phx15846
17 com_err_ should be able to print messages longer than 256 characters.
18 
19 9  phx05920
20 There are too many quotation marks around the word start in the error
21 message for square root of a negative number.  Also, sqrt should be
22 changed to square route in the message.
23 
24 8  phx11622
25 Default error handlers takes faults if the current working directory is
26 deleted.  THis is nondelux.
27 
28 7  phx03742
29 The error message involving sqrt of a negative number prints the wrong
30 line number.  This was on the old deh bug list, but do we really believe
31 that it is not a problem is stu_?  This is left here only for
32 completeness.
33 
34 6  phx06942
35 There are NL's missing before and after linkage_error messages.  Perhaps
36 linkage_error_ is to blame?
37 
38 4  phx05898
39 The messages for arithmetical errors often contain references to PL/I
40 builtins.  They should use generic terms, or mention fortran as well.
41 Better yet, the error handlers should be able to tell which flavor of
42 program took the error, but for that see the following suggestion,.
43 
44 3  phx05641
45 The char printed for onchar=, at least when there is no message for the
46 oncode, is incorrect.  It is one character to the left.
47 
48 2  phx05641
49 The message printed for a missing oncode message is mispelled.
50 
51 1  phx05641
52 Oncode messages for oncode 376 is missing.  oncode_messages_ has to be
53 fixed.