Exploring the embedding and interop features of ECL.
[ Check out all posts in “lisp” series here. ]
In my previous post, I mentioned that I really like Lisp but I only used it for hobby projects so far.
Professionally, I mainly use C, C++ and Python. There have been many times that I realized the solution I settled on is heavily influenced by a Lisp mindset. Mainstream languages pulled more and more concepts from it, so now it is even easier to think in Lisp and write in another language. I don’t mind the label of the tool as long as it is a feasible option, and it empowers me to engineer good solutions.
Nowadays, I rarely think “this would benefit a lot from being implemented in a Lisp instead”. It is even less rare that I consider it feasible to do so, even when there are good technical reasons. But there are cases where the impact of easy exploration (with good enough performance) is a higher priority than even the long term feasibility concerns. And it would be good to be able to throw Lisp at the problem when that’s the case. Even if only for early prototyping.
There are many implementations of the Common Lisp standard. My primary choice has always been SBCL. It is an extremely good native implementation.
Problems I want to throw Lisp at are sometimes existing tech written in C/C++. So I have been looking into interop options.
Common Lisp generally has strong FFI support for C interop. But I also wanted to explore the implementations that are written with embedding in mind. So I am having a closer look at Embeddable Common-Lisp today. Here is the Wikipedia page for ECL.
As a starting point, I found this simple embedding example on ECL repository. It is pretty straightforward.
I don’t yet have a good understanding of the strenghts and weaknesses of this implementation. Will write more as I learn.
Thanks for reading! If you find technical errors, please report in the blog’s Issues page.