In complex macros, that would for instance implement some
domain-specific language, it would be benefitical when the macro could
point to subform in question. The compiler-warn function
does allow you to do that.
| compiler-warn |
|
Function |
|
Issue a warning about the form form. When possible implementation specific means are used to point the finger at the form, so that eventually SLIME or whatever IDE could highlight the context. When not available or not within the compiler, a normal warning is issued. Obviously this does not work if form is an atom.
To narrow down the context you could setup a next best
context with |
| compiler-error |
|
Function |
|
Same as |
| compiler-descend |
|
Macro |
|
The |
Gilbert Baumann, 2021-02-15