[Openmcl-devel] CCL as shared library.

Ron Garret ron at flownet.com
Mon Apr 18 22:46:38 UTC 2016


On Apr 18, 2016, at 3:32 PM, Pascal J. Bourguignon <pjb at informatimago.com> wrote:

> Dmitry Igrishin <dfigrish at gmail.com> writes:
> 
>> Hello,
>> 
>> Could you tell me please, is it possible to build "lisp kernel" as a
>> shared library
>> and map the "heap image" from arbitrary C/C++ program? (Yes, I know
>> about the 
>> ECL/MKCL, but I'm curious about embedding the CCL.)
>> Thanks.
> 
> Compiling a shared library would be the least of the problems you'd
> have.
> 
> I don't know whether ccl needs to map the image at a fixed address
> (perhaps the address where it was saved from?); you would have to
> determine that, and deal with it.
> 
> But the biggest problems would come (as with any other CL
> implementation, or actually, as when trying to merge any two
> runtime-like libraries whatever they are), from the handling of signals
> and threads.

That’s a very good point.

Have you considered TinyScheme?  It is eminently embeddable.  In fact, I have it running on an STM32 chip.

rg



More information about the Openmcl-devel mailing list