[parenscript-devel] PS warning being treated as error by ASDF+SBCL

[Daniel Gackle]

It see that this issue is taking up a lot of valuable time - more than it
probably deserves. I vote for just removing the warnings. If that's a bad
idea, then maybe just leave them as they are for now? We do have a
workaround.

A far more important fix is the one to restore lambda lists for local
functions. We've got 30 or so temporary patches scattered around our code
because of this bug, and I'm anxious to get them out of there. (I know a fix
was committed for this, but we can't use it because of an additional bug it
seemed to introduce, which I reported a couple of days ago).

Thanks,
Daniel

On Wed, Jan 26, 2011 at 3:42 AM, Alessio Stalla <alessiostalla at gmail.com>wrote:

> On Wed, Jan 26, 2011 at 5:04 AM, Vladimir Sedach <vsedach at gmail.com>
> wrote:
> > I give up. This is happening because compile-file returns "failure-p,
> > is false if no conditions of type error or warning (other than
> > style-warning) were detected by the compiler."
> >
> > According to Clozure, this means style-warning exactly, and not any
> > subclasses. Which is completely useless, because style-warning doesn't
> > have any format arguments, so you have to subclass it for it to say
> > anything meaningful.
> >
> > Anyone have any ideas on what to do? Should I just give up on trying
> > to use warnings and write to *debug-io* myself?
>
> Just my €.02, but... to me "no conditions of type... other than
> style-warning" does exclude both style-warning and its subclasses,
> since an instance of a subclass of style-warning is of type
> style-warning. So I'd say you encountered a CCL bug, and using a
> subclass of style-warning should be fine.
>
> Alessio
>
> _______________________________________________
> parenscript-devel mailing list
> parenscript-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/parenscript-devel/attachments/20110126/4efa1dc7/attachment.html>