Re: [Sbcl-help] How to force compile to succeed in the face of warnings?

[Christophe R. <cs...@ca...>]

Robert Uhl <ead...@gm...> writes:

> Stelian Ionescu <sio...@cd...> writes:
>> [Robert Uhl:]
>>> Anyone have any ideas how to force this to be successful?
>>
>> Fix cells-gtk to name foreign types with symbols interned in its own
>> package, instead of :KEYWORD
>
> That's not really a solution, though, as it breaks compatibility with
> all other cells-gtk implementations.  Surely there's some way to let
> SBCL know that I don't care about this _warning_?

Well, there's the ANSI-standard function MUFFLE-WARNING, which can be
used from a condition handler roughly like so:

(eval-when (:compile-toplevel ...)
  (handler-bind ((warning #'muffle-warning))
    (cffi:defctype ...)))

Otherwise, I presume you're using asdf to manage the system
definition?  You can tell asdf-on-sbcl to behave in its treatment of
failed compiles like it does elsewhere

(asdf:oos 'asdf:load-op system :on-failure :warn)

(or bind or set asdf:*compile-file-failure-behaviour*).  You can
automate this by making the files in question have a custom component
class, and writing an :around method on perform which binds the
variable.

Best,

Christophe