Re: compiling (Qi to) Lisp to Python: some observations
- From: Mark Tarver <dr.mtarver@xxxxxxxxxxxxxx>
- Date: Thu, 16 Apr 2009 05:21:14 -0700 (PDT)
On 16 Apr, 13:00, Slobodan Blazeski <slobodan.blaze...@xxxxxxxxx>
wrote:
How do you mean you've compiled to Python? Python is a compiler.
bobi
I mean that Qi can now produce (type secure) Python code as well as
type secure CL. The command is
(quip "<filename here>.qi")
and the resultant Python file is "<filename here>.py. This allows me
to plug in my Qi code into the well-provided Python libraries. My
provider soes not support CL but does support Python.
Eventually we will run the system under Qi/tk and you'll just click on
'File ...' and 'Output to ...' and choose what language you want your
Qi program outputted to - CL, Python, NewLisp, Clojure - even perhaps
C if we bolt on CLiCC.
Mark
.
- Follow-Ups:
- Re: compiling (Qi to) Lisp to Python: some observations
- From: Slobodan Blazeski
- Re: compiling (Qi to) Lisp to Python: some observations
- From: Raffael Cavallaro
- Re: compiling (Qi to) Lisp to Python: some observations
- References:
- compiling (Qi to) Lisp to Python: some observations
- From: Mark Tarver
- Re: compiling (Qi to) Lisp to Python: some observations
- From: Slobodan Blazeski
- compiling (Qi to) Lisp to Python: some observations
- Prev by Date: Re: compiling (Qi to) Lisp to Python: some observations
- Next by Date: Re: compiling (Qi to) Lisp to Python: some observations
- Previous by thread: Re: compiling (Qi to) Lisp to Python: some observations
- Next by thread: Re: compiling (Qi to) Lisp to Python: some observations
- Index(es):
Relevant Pages
|