3 ms·
> Most performant CL implementations require the ability compile to executable code at run-time. Not really. Most performant CL implementations make sure that
by lispm 9y ago
> Most performant CL implementations require the ability compile to executable code at run-time.
Not really. Most performant CL implementations make sure that at runtime nothing needs an actual compiler, unless the application actually needs it.
For example the LispWorks on iOS implementation supports the whole Common Lisp, minus the runtime compiler. It's still possible to use the interpreter, though - AFAIK.
- aidenn0 9y agoLW has always been better at AOTing everything than cmucl derivatives. CCL is somewhat in the middle of the two. That being said, how did I miss LW introducing a version that supports iOS? That's huge!
- lispm 9y ago> LW introducing a version that supports iOS? That's huge! That's a delivery compiler with a relatively complete LispWorks runtime, minus the runtime compiler. It's a bit expensive. It lacks any GUI and is supposed to be used inside an Xcode iOS application. There is also one for Android... They are working on the 64bit ARM version. The 32bit ARM version is out for some time. LispWorks for Mobile: http://www.lispworks.com/products/lw4mr.html http://www.lispworks.com/products/lw4mr.html
- aidenn0 9y agoOuch! $1k per annum is more than I can justify for hobby programming. If I were actually making money in the mobile space it would be tempting though.