Re: compiled open source Windows lisp
From: Pascal Costanza (pc_at_p-cos.net)
Date: 03/15/05
- Next message: Valentino Volonghi aka Dialtone: "Re: Python becoming less Lisp-like"
- Previous message: Brandon J. Van Every: "Re: why not enough lisp libraries?"
- In reply to: fraca7: "Re: compiled open source Windows lisp"
- Next in thread: Ulrich Hobelmann: "Re: compiled open source Windows lisp"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 15 Mar 2005 22:27:50 +0100
fraca7 wrote:
> Edi Weitz wrote:
>
>> On Tue, 15 Mar 2005 23:29:04 +0100, Fraca7 <fraca7@free.fr> wrote:
>
>>> I don't think so. I recently (about 2 months ago) started to want to
>>> learn Lisp (didn't go far for now) and wanted to find a Windows
>>> impl, to evaluate "cross-platformability". The only open source/free
>>> software Lisp interpreter
>
>> Compiler, not interpreter. All available Common Lisp implementations
>> are compilers - one (CLISP) compiles to bytecode while all others
>> compile to machine code.
>
> I find it increasingly difficult to discern between an interpreter and a
> compiler for a virtual machine. I guess that something that produces
> "bytecode" for an actual CPU is a compiler :)
...and a CPU is an interpreter for such "bytecode". As soon as you grasp
that concept, enlightenment will follow... ;-)
Pascal
- Next message: Valentino Volonghi aka Dialtone: "Re: Python becoming less Lisp-like"
- Previous message: Brandon J. Van Every: "Re: why not enough lisp libraries?"
- In reply to: fraca7: "Re: compiled open source Windows lisp"
- Next in thread: Ulrich Hobelmann: "Re: compiled open source Windows lisp"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|