< Support Home
Suggestion: compile-time unsupported should be errors; compile-time errors should give backtraces.
by informatimago on 2015-02-27 (793 days ago)
Mac OS X
When compiling we get warnings such as: defmacro in-package /Users/pjb/src/public/lisp/common-lisp/lisp-reader/package-def.fasl Warning: Function MAKE-INSTANCE is currently unsupported at compile-time. Warning: Function MAKE-INSTANCE is currently unsupported at compile-time. Warning: Compile-time evaluation failed at RT::MAKE-RESTART. Error: Could not expand macro DEFPACKAGE because NIL failed to evaluate at compile-time. make: *** [informatimago] Error 1 1- I think those warning should be considered and signaled as errors, because if any code is generated, it will be wrong. 2- Also, those errors (and ex-warning), since they cannot be debugged in another implementation, being shortcoming of mocl, should produce more debugging information, starting with better reference to the source code in question, and full backtrace (of the macro-expansion/compiler process). (notice it's not CL:DEFPACKAGE in the example above, so nothing you should be concerned about, apart from the fact that we don't have a full compilation environment to work with).
to add a comment.