austral
cl-autowrap
Our great sponsors
austral | cl-autowrap | |
---|---|---|
18 | 8 | |
1,032 | 206 | |
3.6% | - | |
9.1 | 1.5 | |
2 months ago | 18 days ago | |
OCaml | Python | |
Apache License 2.0 | 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.
austral
- Where Are the Supply Chain Safe Programming Languages?
- Rust developers concerned about complexity, low usage
-
Modern Pascal is still in the race (2022)
> But these days folks are mostly used to the C style syntax.
Mostly, but I'm told the new Austral[1] language has syntax very similar to that of Pascal's.
1: https://austral-lang.org/
- Austral Programming Language
-
Why Use Pascal?
For the first couple of items on the list, Austral might be a language worth considering:
https://austral-lang.org
It's new so it obviously doesn't have the community of libraries to use, but it does have a very friendly and accessible Pascal-like syntax, while also having a state of the art linear type system.
-
Interested in "secure programming languages", both theory and practice but mostly practice, where do I start?
For something more new look at Austral.
- The seven programming ur-languages
-
Must move types by Niko Matsakis
https://austral-lang.org has linear types and doesn’t use RAII but it doesn’t have defer.
-
Borrow checker for Zig?
there are other languages simpler than rust which have similar functionality to the borrow checker. see e.g. https://austral-lang.org/
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?
Elm - Compiler for Elm, a functional language for reliable webapps.
c2ffi - Clang-based FFI wrapper generator
csharplang - The official repo for the design of the C# programming language
cffi - The Common Foreign Function Interface
conjure - Interactive evaluation for Neovim (Clojure, Fennel, Janet, Racket, Hy, MIT Scheme, Guile, Python and more!)
chibi-scheme - Official chibi-scheme repository
go - The Go programming language
cl-rashell - Resilient replicant Shell Programming Library for Common Lisp
deprecated-coalton-prototype - Coalton is (supposed to be) a dialect of ML embedded in Common Lisp.
mal - mal - Make a Lisp
racket - The Racket repository
claw - Common Lisp autowrapping facility for C and C++ libraries