From: Bilbo <bi...@ho...> - 2006-01-16 16:25:08
|
I was wondering if there is an easy way to turn off the "Replacing method" warnings when recompiling a file? I used to have a way that worked in some software I recently restarted developing. When developing the software before, I had a small snippet of lisp that would turn off these warnings when I recompiled. It doesn't seem to be working any more. This is the snippet: #+CLISP (eval-when (:load-toplevel :compile-toplevel :execute) (defvar old-warning) (defvar old-gf-warning) (defvar old-gf-replace-all) (setq old-warning clos::*warn-if-gf-already-called* =09=09old-gf-warning clos::*gf-warn-on-replacing-method* =09=09old-gf-replace-all clos::*gf-warn-on-removing-all-methods*) (ext:without-package-lock () =09=09=09=09=09=09(setf clos:*warn-if-gf-already-called* nil =09=09=09=09=09=09=09 clos:*gf-warn-on-replacing-method* nil =09=09=09=09=09=09=09 clos:*gf-warn-on-removing-all-methods* nil))) This served me well before, but it seems to be generating errors now.=20 For one, even though I have the "without-package-lock", it claims that CLOS is a locked package. Continuing from that error, *gf-warn-on-replacing-method* seems to have gone (I can't find it with a grep), and *warn-if-gf-already-called* is not marked external, and *gf-warn-on-removing-all-methods* is gone as well. I read a message stating that custom:*suppress-check-redefinition* would solve another similar message, so I tried (setf custom:*suppress-check-redefinition* t) but that doesn't seem to get rid of the warnings. Thanks for any help. I appreciate CLISP quite a bit. It's nice having a quality Common Lisp implementation avaiable for Windows. |