Common Lisp the Language, 2nd Edition


next up previous contents index
Next: Compiled Functions Up: The Compiler Previous: The Compiler

25.1.1. Compiler Diagnostics

change_begin
X3J13 voted in June 1987 (COMPILER-WARNING-STREAM)   to specify that compile and compile-file may output warning messages; any such messages should go to the stream that is the value of *error-output*.

X3J13 voted in June 1989 (COMPILER-DIAGNOSTICS)   to specify the use of conditions to signal various erroneous situations during compilation. First, note that error and warning conditions may be signaled either by the compiler itself or by code being processed by the compiler (for example, arbitrary errors may occur during compile-time macro expansion or processing of eval-when forms). Considering only those conditions signaled by the compiler (as opposed to during compilation):

Both compile and compile-file are permitted (but not required) to establish a handler for conditions of type error. Such a handler might, for example, issue a warning and restart compilation from some implementation-dependent point in order to let the compilation proceed without manual intervention.

The functions compile and compile-file each return three values. See the definitions of these functions for descriptions of the first value. The second value is nil if no compiler diagnostics were issued, and true otherwise. The third value is nil if no compiler diagnostics other than style warnings were issued; a non-nil value indicates that there were ``serious'' compiler diagnostics issued or that other conditions of type error or warning (but not style-warning) were signaled during compilation.
change_end



next up previous contents index
Next: Compiled Functions Up: The Compiler Previous: The Compiler


AI.Repository@cs.cmu.edu