Re: How to handle these warnings?
Jean Louis <[email protected]> Thu, 19 Oct 2017 10:58:38 +0300
| Newsgroups | gmane.lisp.clisp.general |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Jul 19, 2017 at 11:12:51AM -0400, Sam Steingold wrote: > > * Jean Louis <[email protected]> [2017-07-19 10:49:18 +0300]: > > > > Is there any way to disable it temporarily? > > http://clisp.org/impnotes/mop-clisp.html#mop-clisp-warn > > >>> When CLISP encounters suspicious CLOS code, it issues a WARNING of > >>> type CLOS:CLOS-WARNING. To suppress the undesired warnings (not > >>> recommended!) use EXT:SET-GLOBAL-HANDLER with MUFFLE-WARNING on the > >>> appropriate WARNING type;. To find where the warnings come from > >>> (recommended), set *BREAK-ON-SIGNALS* to the appropriate WARNING > >>> type. I have tried my best to understand, I do not get it. Can you help me with practical example on how to use EXT:SET-GLOBAL-HANDLER with MUFFLE-WARNING on the appropriate WARNING type? Jean ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ clisp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-list