4 ms·
Last I checked SBCL and CCL (both open source native compiled CL implementations) are quite a bit faster than Clasp. However, if you are primarily e.g. calling
by aidenn0 5y ago
Last I checked SBCL and CCL (both open source native compiled CL implementations) are quite a bit faster than Clasp.
However, if you are primarily e.g. calling computational chemistry libraries written in C++, Clasp is the way to go. It's the only non-C++ language implementation I know of with actually usable C++ support.
- pjmlp 5y agoC++/CLI comes to mind, as means to merge .NET and C++ worlds together.
- aidenn0 5y agoOh gosh, I forgot about that. Is that Windows only though? I remember MSVC had managed/unmanaged C++ and allowed calling between the two.
- pjmlp 5y agoSadly yes. And although they don't have much love for it, they still keep it relatively up to date. It was one of the .NET Core 3.1 main milestones. However I would say for the purpose of binding .NET and C++, probably it doesn't need to understand everything anyway.
- int_19h 5y agoThe C++/CLI compiler is definitely Windows-only. But I'm not sure whether the generated code would be, if you compile with /clr:pure (which can still handle everything except for setjmp/longjmp). /clr:pure has been deprecated for some time now, unfortunately. But older compilers are still around...