cling
femtolisp
Our great sponsors
cling | femtolisp | |
---|---|---|
19 | 10 | |
3,329 | 1,550 | |
1.7% | - | |
8.6 | 0.0 | |
12 days ago | about 4 years ago | |
C++ | Scheme | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" 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.
cling
- Cling 1.0 Released
- Cling: Interactive C++ Interpreter
-
Interactive GCC (igcc) is a read-eval-print loop (REPL) for C/C++
More recent activity, but based on clang: https://github.com/jupyter-xeus/xeus-cling https://github.com/root-project/cling
-
It's 2023, so of course I'm learning Common Lisp
> The repl driven workflow is amazing and the lisp images are rock solid and highly performant.
do people not realize that basically everything vm/interpreted language has a repl these days?
https://www.digitalocean.com/community/tutorials/java-repl-j...
https://github.com/waf/CSharpRepl
https://pub.dev/packages/interactive
not to mention ruby, python, php, lua
hell even c++ has a janky repl https://github.com/root-project/cling
-
Compiled and Interpreted Languages: Two Ways of Saying Tomato
Interactive C++ with Cling, https://blog.llvm.org/posts/2020-11-30-interactive-cpp-with-cling/, https://github.com/root-project/cling/, Relaxing the One Definition Rule in Interpreted C++, https://dl.acm.org/doi/10.1145/3377555.3377901 (PDF: https://www.researchgate.net/publication/339463915_Relaxing_the_one_definition_rule_in_interpreted_C)
-
dont want online ones
Want to see your mind blown? Check out cling, a (sort of) C and C++ interpreter (it's a REPL). Or the work in progress, live-developed clauf, a real C interpreter.
-
How to cling for execute code plugin?
Cling: https://github.com/root-project/cling
-
Do you use Wokwi to test/simulate/debug your ESP32/Arduino code, or are there other dev tools a better fit for the ESP32?
Wanting to just test pure c or c++ functions that are hardware independent -> (solution that I'm using): cling just in time compiler, gives a shell that you can just experiment with C++ expressions
-
gcc is pre installed but g++ not?
C++ source cannot contain a shebang, but you can make them executable with binfmt-misc, and have the kernel pass them to a C++ interpreter such as Cling upon execution. Pretty much the same as running Python or Bash scripts.
- Fête à bord d’un avion de Sunwing | L’organisateur s’explique sur l’origine de sa fortune
femtolisp
- Petalisp: Elegant High Performance Computing
- fe: A tiny, embeddable language implemented in ANSI C
-
From Common Lisp to Julia
> In short, Julia is very similar to Common Lisp, but brings a lot of extra niceties to the table
This probably because Jeff Bezanson, the creator of Julia, created a Lisp prior to Julia, which I think still exists inside Julia in some fashion
https://github.com/JeffBezanson/femtolisp
-
Modern Python Performance Considerations
Well let's flip this around: do you think you could write a performant minimal Python in a weekend? Scheme is a very simple and elegant idea. Its power derives from the fact that smart people went to considerable pains to distill computation to limited set of things. "Complete" (i.e. rXrs) schemes build quite a lot of themselves... in scheme, from a pretty tiny core. I suspect Jeff Bezanson spent more than a weekend writing femtolisp, but that isn't really important. He's one guy who wrote a pretty darned performant lisp that does useful computation as a passion project. Check out his readme; it's fascinating: https://github.com/JeffBezanson/femtolisp
You simply can't say these things about Python (and I generally like Python!). It's truer for PyPy, but PyPy is pretty big and complex itself. Take a look at the source for the scheme or scheme-derived language of your choice sometime. I can't claim to be an expert in any of what's going on in there, but I think you'll be surprised how far down those parens go.
The claim I was responding to asserted that lisps and smalltalks can only be fast because of complex JIT compiling. That is trueish in practice for Smalltalk and certainly modern Javascript... but it simply isn't true for every lisp. Certainly JIT-ed lisps can be extremely fast, but it's not the only path to a performant lisp. In these benchmarks you'll see a diversity of approaches even among the top performers: https://ecraven.github.io/r7rs-benchmarks/
Given how many performant implementations of Scheme there are, I just don't think you can claim it's because of complex implementations by well-resourced groups. To me, I think the logical conclusion is that Scheme (and other lisps for the most part) are intrinsically pretty optimizable compared to Python. If we look at Common Lisp, there are also multiple performant implementations, some approximately competitive with Java which has had enormous resources poured into making it performant.
-
CppCast: Julia
While it uses an Algol inspired syntax, it has the same approach to OOP programing as CLOS(Common Lisp Object System), with multi-methods and protocols, it has a quite powerfull macro system like Lisp, similar REPL experience, and underneath it is powerered by femtolisp.
- Julia and the Incarceration of Lisp
-
What is the smallest x86 lisp?
For a real answer, other replies have already mentioned KiloLisp, but there's also femtolisp. Also, not exactly what you're asking for, but Maru is a very compact and elegant self-hosting lisp (compiles to x86).
-
lisp but small and low level?Does it make sense?
Take a look at femtolisp It has some low level features and is quite small. There is also a maintenance fork at lambdaconservatory
-
Lispsyntax.jl: A Clojure-like Lisp syntax for julia
A fun Julia easter egg I recently discovered.
Running 'julia --lisp' launches a femtolisp (https://github.com/JeffBezanson/femtolisp) interpreter.
-
Wisp: A light Lisp written in C++
Reminds me of the femtolisp README :)
Almost everybody has their own lisp implementation. Some programmers' dogs and cats probably have their own lisp implementations as well. This is great, but too often I see people omit some of the obscure but critical features that make lisp uniquely wonderful. These include read macros like #. and backreferences, gensyms, and properly escaped symbol names. If you're going to waste everybody's time with yet another lisp, at least do it right damnit.
https://github.com/JeffBezanson/femtolisp
What are some alternatives?
termux-ndk - android-ndk for termux
small-lisp - A very small lisp interpreter, that I may one day get working on my 8-bit AVR microcontroller.
xeus-cling - Jupyter kernel for the C++ programming language
julia - The Julia Programming Language
cppreference-doc - C++ standard library reference
Carp - A statically typed lisp, without a GC, for real-time applications.
sectorlisp - Bootstrapping LISP in a Boot Sector
Fennel - Lua Lisp Language
foth - Tutorial-style FORTH implementation written in golang
magic_get - std::tuple like methods for user defined types without any macro or boilerplate code
hissp - It's Python with a Lissp.