* Nikodemus Siivola [2010-09-02 11:59] writes:
On 21 August 2010 11:03, Tobias C Rittweiler tcr@freebits.de wrote:
Should C-c C-k try to load a resulting fasls file ALWAYS?
Should it only do so if COMPILE-FILE did not return T as failurep?
From glancing, SBCL's and CMUCL's swank backends do the latter.
...which I've been bitten a couple of times by. :)
How about: pop up the debugger with a restart to load the file if failurep is true?
The problem is that compiler warnings often contain the most interesting information and popping up a debugger either explicitly or by load-time code hides the compiler messages (actually, aborting the debugger also aborts the part that sends the warnings to Emacs so the user doesn't see the warnings).
I think it would be better to display the compiler warnings first and then ask the user (with some y-or-n style query) whether the fasl file should be loaded. Essentially move the decision to the Emacs side; that way customization would also be easier.
Helmut