From: Faré <fa...@gm...> - 2010-08-12 20:57:10
|
On 12 August 2010 09:41, Sam Steingold <sd...@gn...> wrote: > I think > (or custom:*compile-warnings* *asdf-verbose*) > is more reasonable OK. Or maybe I should leave it to custom:*compile-warnings*, which defaults to T anyway. What do you think? > I can hardly imagine a situation when a warning or error issued by the > implementation should be suppressed by asdf. ASDF certainly shouldn't suppress anything by default. >>>>>> That said, if it is a policy that CLISP should issue lots of warnings, >>>>>> we could conditionally modify the defaults for >>>>>> *compile-file-warnings-behaviour* and >>>>>> *compile-file-failure-behaviour*. >>>> Should both be :ignore on CLISP? >> They are used to determine what to do when there's a failure and when >> there are warnings, respectively, as given from secondary and tertiary >> values. > what are the valid values for these *behavior* variables? > ignore actually sounds fine as long as it means that the value is ignored > while the warnings and errors are NOT suppressed. The valid values are :ignore :warn :error. :error means ASDF will issue an (error ...) after the compilation (default failure behaviour on SBCL), :warn means ASDF will issue a (warn ...)ing , and :ignore means ASDF will proceed happily. In no case does ASDF suppress messages here. Does that change make ASDF 2.116 suitable to you? > PS. why does asdf place compiled files in ~/.cache/common-lisp instead of > the directory tree which contains the source code? > The cache is enabled by default, because that's what allows things to work out of the box with no configuration for most people in most installations, notably where multi-user shared sources or multiple implementations are involved. There's a FAQ on how to disable it. If CLISP needs some exceptions to these translations, for implementation-provided libraries, I can add an entry to the wrapping-output-translations function, according to your specifications. See also function module-provide-asdf if you want CLISP to hook into ASDF for requiring software. (Currently supported by ABCL, ClozureCL, CMUCL, ECL, SBCL.) --#f Being really good at C++ is like being really good at using rocks to sharpen sticks. — Thant Tessman |