cl-cblas
cl-autowrap
cl-cblas | cl-autowrap | |
---|---|---|
3 | 8 | |
2 | 208 | |
- | - | |
0.0 | 1.5 | |
over 1 year ago | 12 days ago | |
Python | Python | |
- | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cl-cblas
-
CL-AUTOWRAP generated (C)BLAS wrapper in QUICKLISP
About the convergence, I actually want to separate out the low-level backend interface from the high level user interface. That way, multiple high level libraries can employ the same common low-level backends. This has been my motivation for CL-CBLAS and CL-BMAS.
-
[Common Lisp] Best Libraries for Interfacing with UNIX-like Operating Systems?
(ii) generating the bindings for the first time can be a fair bit of work involving installation of the correct version of clang and c2ffi; community maintained repos can make this latter step super easy by not having to install clang and c2ffi; I made a repo for cblas but it's by no means stable or cross-platform (or perhaps even cross-unix-like) yet.
cl-autowrap
-
Why Is Common Lisp Not the Most Popular Programming Language?
> Lack of access to the C libraries.
???
I recently started learning Common Lisp for fun (and fun it is!) and the ease of accessing C libraries was one of the things that surprised me in a positive way.
Using https://github.com/rpav/cl-autowrap one can simply write (c-include "file.h") and the API defined in "file.h" is accessible from Lisp. I can't think of a simpler way.
Even without cl-autowrap, FFI using https://cffi.common-lisp.dev/ seems simple enough.
-
An Idea for Piggybacking Python (language) ecosystem
I think the closest is cl-autowrap. I can imagine a higher level wrapper around it by which it can translate the python header file into the CL counterpart, although I'm not sure how much work the translation might entail. Also, because python and lisp semantics can differ considerably, the generated code might be trying to do weird things - again an issue of translation.
-
Why Functional Programming Should Be the Future of Software
Common lisp has a "pretty OK" story for calling C code whenever some speed is needed [0,1]. In my opinion, they suffer from some of the documentation/quick start problems that common lisp has, but they're otherwise usable.
Some of Naughty Dog's late 90's/early 2000's games (Jak and Daxter, Jak II) were written in a lisp called GOAL, Game Oriented Assembly Lisp [2]
[0] https://github.com/rpav/cl-autowrap
-
Common Lisp language extensions wish list?
The closest thing to what you request, that I'm aware of, is cl-autowrap (to use C code from Lisp) but it is not standard in any way. CFFI is the de facto standard for using C from Lisp across different implementations.
-
I have bolted together ECL and the Irrlicht game library
:claw tracks back to 2017 as a fork of cl-autowrap with cl-autowrap/pull/83 feature.
-
Common Lisp
If you're interested in FFI, then yeah CFFI is the standard. The other comments addressed speed, I also wanted to point out https://github.com/rpav/cl-autowrap which is built on top of CFFI and can help get a wrapper up and running faster. After using autowrap's c-include you can then use CFFI basically like normal or some useful autowrap/plus-c's helper functions -- e.g. in one project, I have an SDL_Event (https://wiki.libsdl.org/SDL_Event) and to access event.key.keysym.scancode I have a helper function that's just (plus-c:c-ref event sdl2-ffi:sdl-event :key :keysym :scancode). Last year I wanted to try out using FMOD, and even though it's closed source and has a (to me) "interesting" API things worked easily: https://gist.github.com/Jach/dc2ec7b9402d0ec5836a935384cacdc... More work would be needed to make a nice wrapper, type things more fully, etc. but depending on the C library you might find someone's already done that (or made a start) and made it available from quicklisp.
-
[Common Lisp] Best Libraries for Interfacing with UNIX-like Operating Systems?
In recent years there has also been cl-autowrap; caveats -
-
Alternative to ECL?
There is the cl-autowrap that can generate lisp packages from C header filesc- I am unsure if it sticks to ANSI C or goes beyond. It inturn depends on c2ffi for the first time around.
What are some alternatives?
OpenBLAS - OpenBLAS is an optimized BLAS library based on GotoBLAS2 1.13 BSD version.
c2ffi - Clang-based FFI wrapper generator
magicl - Matrix Algebra proGrams In Common Lisp.
cffi - The Common Foreign Function Interface
awesome-cl - A curated list of awesome Common Lisp frameworks, libraries and other shiny stuff.
chibi-scheme - Official chibi-scheme repository
cl-rashell - Resilient replicant Shell Programming Library for Common Lisp
mal - mal - Make a Lisp
claw - Common Lisp autowrapping facility for C and C++ libraries
c-mera - Next-level syntax for C-like languages :)
racket - The Racket repository
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project