Re: Question about *handle-warn-on-redefinition*.
"Tim Bradshaw (as tfb at tfeb dot org)" <[email protected]>
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <[email protected]> |
I suspect you are not compiling the file. LW does not warn for assignments to unknown variables in interpreted code (or not at the top level anyway), but it does in the compiler. IN particular if I compile your file I get a warning about ;;;*** Warning in (top-level-form 3): test::*handle-warn-on-redefinition* assumed special in SETQ It is *almost always* a good idea to compile things, simply because the compiler will find things that the interpreter won't. --tim > On 24 Apr 2025, at 16:03, Uģis Lācis (as ugis dot lacis at equa dot se) <[email protected]> wrote: > > Hi LispWorks community, > We have been experimenting with LispWorks to see if it would be good to use as a LISP environment in our company. During our experiments, we have noticed following strange behaviour. If I define a package that uses common-lisp (but not lispworks), then setting *handle-warn-on-redefinition* does not seem to have an effect. It can be reproduced by loading attached file with (load "redefine_method_package.lisp"). But strangely, LispWorks does not complain that variable *handle-warn-on-redefinition* is not defined. If I use lispworks:*handle-warn-on-redefinition* instead, the behavior is as expected and I can control redefinition per our needs. > Is this the expected behaviour? Or is this potentially a bug? > Best wishes, > Ugis<redefine_method_package.lisp> _______________________________________________ Lisp Hug - the mailing list for LispWorks users [email protected] http://www.lispworks.com/support/lisp-hug.html