On Wed, Nov 04, 2009 at 01:23:47PM +0000, Sebastian Tennant wrote:
>
> Quoth "Leslie P. Polzer" <[email protected]>:
> >> I will fix it, push the change and then notify you here.
> >
> > Update: the warning emitted by c2mop seems to be in disagreement
> > with the spec. I'm arguing for the case on closer-devel.
>
> It may be some time before a global switch to control the emission of warnings
> is implemented in closer-mop, and then utilised in weblocks.
I think it will be implemented by the end of next week, and Weblocks
wouldn't need to be modified at all since the switch would default to
the previous behavior.
> Can you suggest a workaround in the meantime? Perhaps a magic darcs
> incantation in clbuild/source/closer-mop/ that will 'un-apply' the offending
> patch?
Sorry, my Darcs-fu is bad and I haven't identified the changeset. But
you could just apply this patch to closer-mop in the meantime:
--- old-closer-mop/pcl/closer-mop.lisp 2009-11-04 14:52:22.431451931
+0100
+++ new-closer-mop/pcl/closer-mop.lisp 2009-11-04 14:52:22.431451931
+0100
@@ -402,6 +402,7 @@
(defmacro defmethod (&whole form name &body body)
(declare (ignore body))
(let ((generic-function (when (fboundp name) (fdefinition name))))
+ #+(or)
(unless generic-function
(warn "No generic function ~S present when encountering
macroexpansion of defmethod. Assuming it will be an instance of
standard-generic-function." name))
`(cl:defmethod ,@(cdr form)))))
Hitting the ACCEPT restart after ASDF breaks on the warning might also
work.
Leslie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---
