[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Disabling compiler in PCL
- To: jona@whale.ils.nwu.edu
- Subject: Re: Disabling compiler in PCL
- From: Gregor J. Kiczales <gregor@parc.xerox.com>
- Date: Thu, 14 Jun 90 11:42:32 PDT
- Cc: commonloops.pa@Xerox.COM
- In-reply-to: Kemi Jona's message of Thu, 14 Jun 90 10:00:45 CDT <9006141500.AA02145@whale.ils.nwu.edu>
- Line-fold: NO
- Redistributed: commonloops.pa
- Sender: gregor@parc.xerox.com
Date: Thu, 14 Jun 90 10:00:45 CDT
From: Kemi Jona <jona@whale.ils.nwu.edu>
I am using PCL with Mac Allegro Common Lisp and would like to be able
to make a standalone application. The problem is that the compiler is
not included in such an application, so any calls to the compiler do
nothing. I believe this is a problem when creating new instances in
PCL.
Can anyone confirm that PCL does in fact make calls to the compiler
when new instances are created? I am nearly certain that it does.
Second, and more importantly, is there any mechanism by which I can
instruct PCL not to call the compiler?
There are certain cases where PCL calls the compiler at runtime. This
tends to happen when it encounters a generic function or effective
method `shape' that it has never seen before. There is a way to get it
to precompile these, see the release notes for a description of the
macro precompile-random-code-segments.
There is also a way to tell PCL not to try and call the compiler, even
if it would like to. You can do this by setting the variable
*COMPILER-PRESENT-P* to nil. For more information on this, see the
definition of COMPILE-LAMBDA in the file low.lisp.