[asdf-devel] deferred warnings doesn't tell which file

Attila Lendvai attila.lendvai at gmail.com
Tue Oct 29 15:50:26 UTC 2013


so, i'm using deferred warnings, because warnings are useful!

the only problem is that, in this specific case, i get the following
after compilation has finished:

; compilation finished in 0:00:00.033
; caught WARNING:
;   undefined variable: HU.DWIM.PEREC::INSTANCE
; compilation unit finished
;   Undefined variable:
;   caught 1 WARNING condition
; compilation unit aborted
;   caught 4 fatal ERROR conditions

and it doesn't even tell which file it happened with. (this error comes
from the depths of sbcl internals around generic methods).

how was it meant to work originally? is it assumed that the warning
will always contain a name or something that helps identifying where
it comes from? if so, then it's not always the case, and when warnings
are not deferred at least the current toplevel form is visible in the

note: this is not a showstopper just an inconvenience. i can identify
the file by checking the *.sbcl-warnings files manually.

• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
“Here is the world. Beautiful and terrible things will happen. Don't be afraid.”
	— Frederick Buechner

More information about the asdf-devel mailing list