[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using the compiler internally in distributed applications
- To: info-mcl@digitool.com
- Subject: Re: Using the compiler internally in distributed applications
- From: neves@neves.ils.nwu.edu (David Neves)
- Date: Wed, 15 Mar 1995 10:57:32 -0600
- Organization: The Institute for the Learning Sciences
- References: <TAR.95Mar14160504@hobbes.ISI.EDU>
- Sender: owner-info-mcl@digitool.com
In article <TAR.95Mar14160504@hobbes.ISI.EDU>, tar@isi.edu wrote:
:
: Is there any way to set things up so that the compiler is properly
: excised (so that a lisp development environment is not distributed), but
: retain our own internal access to the compiler to call on
: application-generated code?
Digitool should have some (better) policy on this as I've seen other
applications that, for one reason or another, need access to the
compiler. The easy way is to redefine EXCISE-COMPILER as a NOP. This
would probably allow you to use :excise-compiler without it doing anything
(I don't know for sure as I've never tried it). This, no doubt, counters
the reason Digitool wants you to use :excise-compiler so I suppose you
could also check the disassembly for EXCISE-COMPILER to see which
functions it nukes and save copies somewhere.
-David