Juan Jose Garcia-Ripoll <juanjose.garciarip...@gmail.com> writes: > On Mon, Jul 16, 2012 at 1:02 PM, Pascal J. Bourguignon > <p...@informatimago.com> wrote: > > clisp has a true interpreter, and it will macroexpand several times the > same macro. > > I think it was either Bruno Haible or Sam Steingold who explained to > me once that the trick in CLISP is not to interpret, but to recompile > the function when the macro changes. This way it is more efficient > than GCL (which uses a list traversal interpreter) but behaves like an > interpreter in that sense. In any case I never studied CLISP's source > code, so I cannot be sure whether I misunderstood the email.
Yes, actually it's the minimum compilation that is done once with the result cached for interpretation, IIRC. But it's definitely an interpreter of the lisp forms which is used to run and debug. The clisp debugger cannot debug inside byte-compiled functions. -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
