[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Compiler Warnings, again
- To: info-mcl
- Subject: Re: Compiler Warnings, again
- From: email@example.com (Bob Kerns)
- Date: 15 Mar 92 18:11:03 GMT
- In-reply-to: firstname.lastname@example.org's message of 14 Mar 92 18:42:39 GMT
- Newsgroups: comp.lang.lisp.mcl
- Organization: Cambridge Research Lab, Digital Equipment Corp.
- References: <29C2491E.email@example.com>
- Sender: firstname.lastname@example.org (USENET News System)
In article <29C2491E.email@example.com> firstname.lastname@example.org (Michael Pazzani) writes:
From: email@example.com (Michael Pazzani)
Date: 14 Mar 92 18:42:39 GMT
predicates that are not (yet) defined cause "Undefined functions" warnings.
I'm sure if I try hard enough, I can get around this, but I'd rather
not anticipate every possible warning and correct for it. I really
want to turn off all warnings. If I promise to use it only in
(without-compiler-warnings (compile (convert-to-lisp-function ....)))
can I get a hint on how to write without-compiler-warnings.
How will you know if convert-to-lisp-function has a bug?
What you want to do is use with-compilation-unit around
the entire set of compilations. This *should* cause your
"undefined functions" to not happen until the end, by
which time they should be defined (or you want to hear
Another approach is, instead of compiling them one at a time,
turn them all into a big progn:
`(PROGN ,@(mapcar #'convert-to-lisp-function prolog-stuff))
and compile that all at once.