[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: compiling interpreted functions
- To: firstname.lastname@example.org
- Subject: Re: compiling interpreted functions
- From: Espen J. Vestre <email@example.com>
- Date: 11 Oct 1993 10:01:37 GMT
- Distribution: world
- Newsgroups: comp.lang.lisp.mcl, comp.lang.lisp
- Organization: Computerlinguistik, Universitaet des Saarlandes
- References: <9310072041.AA15230@telecaster.think.com>
- Xref: news.cambridge.apple.com comp.lang.lisp.mcl:4226 comp.lang.lisp:6314
In article <9310072041.AA15230@telecaster.think.com> Barry Margolin,
> I've removed comp.lang.lisp.franz, since I don't think this discussion
> relevant to Franz Lisp (which has nothing to do with the Lisp product
> Franz, Inc.).
It's not relevant to MCL either, since (despite of what the original
posting said), MCL will by default compile _all_ functions, independent
of how and where they are defined, so the need to call compile on an
interpreted function simply doesn't exist.
> dpANS and CLtL2 it is extended to allow a lambda expression or a
> But many implementations don't implement that feature yet.
MCL are among these implementations, so in this respect, the thread is
still relevant for MCL, at least for portability reasons (but if you test
the function with compiled-function-p first, the explicit call on compile
in MCL should never occur, except for rare debugging occasions where you
have turned off automatic compiling).
Espen J. Vestre, firstname.lastname@example.org
Universitdt des Saarlandes,
Computerlinguistik, Gebdude 17.2
Postfach 1150, tel. +49 (681) 302 4501
D-66041 SAARBR\CKEN, Germany fax. +49 (681) 302 4351