Re: CLISP CLOS style warnings
Sam Steingold <[email protected]>
| Newsgroups | gmane.lisp.clisp.devel,gmane.lisp.asdf.devel |
|---|---|
| Message-ID | <[email protected]> |
> * Faré <[email protected]> [2017-08-01 10:07:33 -0400]: > >> To mark a generic function as user-extendable, one can now use a >> declaration: >> >> --8<---------------cut here---------------start------------->8--- >> (defgeneric perform (...) >> (declare #+clisp (dynamically-modifiable)) >> ...) >> (defgeneric operation-done-p (...) >> (declare #+clisp (dynamically-modifiable)) >> ...) >> --8<---------------cut here---------------end--------------->8--- >> >> The declaration is now in `hg tip` (but has not been released yet). >> > Will that declaration cause a warning or error on older versions of > clisp? If yes, what read-time conditional more precise than #+clisp > can I use to only enable on recent enough versions of clisp? My first reaction was --8<---------------cut here---------------start------------->8--- (declaim (declaration dynamically-modifiable)) --8<---------------cut here---------------end--------------->8--- but for some reason it does not work with defgeneric. Sorry. -- Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504 http://steingoldpsychology.com http://www.childpsy.net http://www.memritv.org https://jihadwatch.org http://camera.org http://jij.org Only a fool has no doubts. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel