1/* tag: Tom Lord Tue Dec 4 14:57:12 2001 (bugs.doc) 2 */ 3 4/************************************************************************ 5 *(h0 "Handling Bugs") 6 * 7 * 8 * |Burroughs, William S.| 9 * 10 * Captain Mission did not fear Panic, the sudden 11 * intolerable knowing that everything is alive. 12 * He was himself an emissary of Panic, of the 13 * knowledge that man fears above all else: the 14 * truth of his origin. It's so close. Just wipe 15 * away the words and look. 16 * 17 * William S. Burroughs 18 * Ghost of a Chance 19 * 20 * The Hackerlab C library defines a "bug" as a condition within a 21 * running program which is not expected to arise, and which can not 22 * be recovered from if it does arise, but which can not be ruled out 23 * with certainty. 24 * 25 * When a bug occurs, the only sane alternative is for the process 26 * to exit with a non-0 status. By convention, a process which 27 * exits due to a bug should print an error message on its standard 28 * output stream giving some indication of what bug occurred. 29 * 30 * When a fatal condition arises, call `panic'. In tricky code, 31 * play it safe and test for conditions which should always be 32 * true by using the macro `invariant'. See xref:"Panic". 33 * 34 * If your program needs to quit in some way besides `_exit(1)', you 35 * might want to replace the function `panic_exit'. See xref:"Exiting 36 * Due to Panic". 37 * 38 */ 39 40/*(menu) 41 */ 42 43/*(include-documentation "panic.c") 44 */ 45 46/*(include-documentation "panic-exit.c") 47 */ 48 49