On Mon, Apr 1, 2013 at 1:16 AM, Gabriel Dos Reis
g...@integrable-solutions.net wrote:
I just quickly glanced over the code. I noticed that some of the
constructs
https://github.com/juanjosegarciaripoll/cl-cxx/blob/master/include/cl-cxx/defun.hpp
are C++03 ways of emulating
On Tue, Mar 5, 2013 at 1:59 PM, Juan Jose Garcia-Ripoll
juanjose.garciarip...@gmail.com wrote:
I did not know about Boost::Python. On reading it, it seems that, though
horrible, it would be easy to port to any Common Lisp out there. If I were
to write that, though, I would not do it as they
05.03.2013, 01:25, "Juan Jose Garcia-Ripoll" juanjose.garciarip...@gmail.com:On Mon, Mar 4, 2013 at 5:30 PM, Christian Schafmeister chris.sc...@verizon.net wrote:I've created a new implementation of Common Lisp that has a core written in C++ completely from scratch but hosts the ECL Common Lisp
On Sat, Mar 16, 2013 at 3:29 PM, Anton Vodonosov avodono...@yandex.ruwrote:
As ECL can compiles List to C, a C compiler generating LLVM code may be
used
(llvm-gcc or clang).
What Christian is doing is more what I thought should be done:
automatically generating LLVM bytecode and loading it
Anton,
The compiler I'm writing uses the LLVM API to generate LLVM-IR directly which
is just-in-time compiled to executable code.
Using (setq XXX (COMPILE nil (lambda (x) (* 3 x returns a compiled function
that can be evaluated directly using (FUNCALL XXX 4) -- 12.
There are no intermediate
On Tue, Mar 5, 2013 at 1:33 AM, Christian Schafmeister
chris.sc...@verizon.net wrote:
I needed a CL interpreter which would host the compiler (which I wrote in
Common Lisp) which calls the LLVM-IR library to generate llvm::Module
objects which contains llvm::Function objects that are
Juanjo,
To summarize - I needed a Common Lisp implementation that interfaced well with
C++ so I wrote one rather than use an existing CL implementation.
By interface well I mean interface functions are generated automatically and
much of the horribleness that is C++ is handled by template
On Tue, Mar 5, 2013 at 7:15 PM, Christian Schafmeister
chris.sc...@verizon.net wrote:
C++ template programming is not pretty but using template programming
hands the problem of identifying C++ types and parsing C++ code to the C++
compiler where it is done properly. The other approach is to
On Mar 5, 2013, at 5:41 PM, Juan Jose Garcia-Ripoll
juanjose.garciarip...@gmail.com wrote:
On Tue, Mar 5, 2013 at 7:15 PM, Christian Schafmeister
chris.sc...@verizon.net wrote:
C++ template programming is not pretty but using template programming hands
the problem of identifying C++ types
Hi,
I've created a new implementation of Common Lisp that has a core written in C++
completely from scratch but hosts the ECL Common Lisp source code.
It hosts all of the ECL Common Lisp code in the ecl/src/lsp and ecl/src/clos
directories of the ECL source tree.
I do not use any part of the
On Mon, Mar 4, 2013 at 5:30 PM, Christian Schafmeister
chris.sc...@verizon.net wrote:
I've created a new implementation of Common Lisp that has a core written
in C++ completely from scratch but hosts the ECL Common Lisp source code.
Sounds like a lot of work.
It hosts all of the ECL
Adding my $0.02 to using ecl with c++, it is quite well possible, but very
tiresome. For every method call, you have to write static wrapper which
will cast all the
pointer(s) into respectable type and call the method with arguments. Doing
so by hand is very impossible, however, doing so with
On Mon, Mar 4, 2013 at 10:35 PM, Peter Enerccio enerc...@gmail.com wrote:
Adding my $0.02 to using ecl with c++, it is quite well possible, but very
tiresome. For every method call, you have to write static wrapper which
will cast all the
pointer(s) into respectable type and call the method
On Mar 4, 2013, at 4:23 PM, Juan Jose Garcia-Ripoll
juanjose.garciarip...@gmail.com wrote:
On Mon, Mar 4, 2013 at 5:30 PM, Christian Schafmeister
chris.sc...@verizon.net wrote:
I've created a new implementation of Common Lisp that has a core written in
C++ completely from scratch but
14 matches
Mail list logo
