Class | Package: excl | ToC | DocOverview | CGDoc | RelNotes | FAQ | Index | PermutedIndex
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version

## compiler-undefined-functions-called-warning

This is the class of condition signaled if during the compilation of a file, the compiler notices a call to a function not defined (previously or in the file), it prints a warning that the function is called but not yet defined. (It is not an error to compile a function that calls a not-yet-defined function, of course. The warning is often useful, however, when the function name is typed incorrectly or the user believes a function is defined when it is not.)

This condition will also be signaled when an operator defined at the top-level calling undefined functions is compiled.

Here is an example:

    ;; The file foo.cl contains the following. Note the call to BAR.
    (in-package :user)
    (defun foo (x) (bar x))

    ;; Here is what happens when we compile the file:
    USER(1): (compile-file "foo.cl")
     ; --- Compiling file /net/rubix/usr/tech/dm/foo.cl ---
     ; Compiling FOO
     ; Writing fasl file "/net/rubix/usr/tech/dm/foo.fasl"
     ; Fasl write complete
     Warning: The following undefined functions were referenced in the compilation:
     (BAR)
    #p"/net/rubix/usr/tech/dm/foo.fasl"
    NIL
    NIL
    USER(2):

If multiple calls to compile-file are part of the body of a with-compilation-unit form, no undefined function warning will be signaled when a function called in one file is defined in a later file.

See compiling.htm for general information on the Allegro CL compiler.

Copyright (c) 1998-2022, Franz Inc. Lafayette, CA., USA. All rights reserved.
This page was not revised from the 10.0 page.
Created 2019.8.20.

|  | ToC | DocOverview | CGDoc | RelNotes | FAQ | Index | PermutedIndex
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version