While compiling .lsp files I ran into a well known problem:
references to macros appear prior to their definition.
Because of organizational reasons I can neither reorder
the source files, nor load them into the lisp system before
compilation.
Therefore I thought of introducing a new declaration specifier
eg. (proclaim '(macro foo))
The lisp I work with (a XLISP derivative) already has lots of
nonstandard features, so one more wouldn't matter....but is
there a simpler or more elegant way to achieve this?
(Note: I have no EVAL-WHEN)
Any hint will be appeciated
- G.-
--
============================================================================
Gottfried Ira Inst. for Microelectronics, Technical University of Vienna
Gusshausstrasse 27-29 / 1040 Vienna / AUSTRIA
E-Mail: ···@iue.tuwien.ac.at | "Konsequenz ist ein Kobold der
Phone: +43/1/58801-3689 | nur in engen K"opfen spukt."
fax: +43/1/5059224 | -- Ralph Waldo Emerson
============================================================================
···@iue.tuwien.ac.at (Gottfried Ira) writes:
>While compiling .lsp files I ran into a well known problem:
>references to macros appear prior to their definition.
We have had the same problem. Our solution is as follows: We have
generated a new Lisp image (in Lucid) containing the Lisp
functions and the functions we should like to have. Each compilation
is done in this image. So all macros are present at compile time.
Inline declarations do not solve the problem appropriately. The
Lucid compiler looks for the interpreted version of the function but
our Lisp image contains compiled functions only.
Thomas Kaeufl (······@ira.uka.de)
Institut fuer Logik, Komplexitaet und Deduktionssysteme
University of Karlsruhe, Germany