Re: three questions about ASDF
Nikodemus Siivola <[email protected]>
| Newsgroups | gmane.lisp.cclan.general |
|---|---|
| Message-ID | <[email protected]> |
William Harold Newman <[email protected]> writes: > First, what is a good way to stop ASDF from suppressing the output > describing full WARNINGs which result when it calls SBCL's > COMPILE-FILE function? Turns out that presently SBCL signals unbound variable warnings only from SUMMARIZE-COMPILATION-UNIT -- at the end of the compilation unit. ...and ASDF puts a WITH-COMPILATION-UNIT around the entire operation on system, and so the warnings are still patiently waiting in SB-C::*UNDEFINED-WARNINGS* to be signalled once ASDF is done. So writing an :around method on COMPILE-OP to wrap it in a WITH-COMPILATION-UNIT :OVERRIDE T gets you the same behaviour as COMPILE-FILE. ...but to get the context in the top-level forms we need to change SBCL. Not an unfamiliar feat to you, I'd say. ;-) Presumably NOTE-UNDEFINED-REFERENCE should signal the appropriate warning, and the end-of-compilation-unit summary could be condenced a bit. > Second, if I wanted to experiment with the bleeding edge ASDF by using > it to override whatever happens to be bundled with my SBCL > installation, what is "the" (or at least "a") preferred way? Something > like > (load (compile-file "/usr/local/src/asdf-bleeding-edge/asdf")) > in my .sbclrc? I think that is as good as any. You may want to add :sbcl-hooks-require to *features* beforehand, though, to get the require-magic. > Third, what is the master upstream version of the ASDF documentation? > I found errours in the version of the documentation frozen in > sbcl/contrib/asdf/ when I was investigating ASDF's errour reporting, > and I'd consider submitting patches, but the documentation in > "cvs co asdf" from SourceForge looks different, and it isn't 100% > clear to me that even that is the master upstream version of the > documentation, and I don't want to try to fix something which has > already been fixed independently. As far as I am concerned the asdf.texinfo in the cclan repository is authoritative, but yes, someone (like yours truely) may have at a clueless moment done things to the version in sbcl repo -- something to investigate. Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs."