cling VS Vacietis

More recent activity, but based on clang: https://github.com/jupyter-xeus/xeus-cling https://github.com/root-project/cling

> 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

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)

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.

Cling: https://github.com/root-project/cling

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

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.

Yes. Not because of the developer, but because of how extremely flexible and dynamic the Lisp-family languages are. The power and joy of Lisp is in how it's almost a meta-language, so every project can become its own EDSL. The most famous (infamous?) example of this is Vacietis[2], which is a Common Lisp library that allows C code to be imported directly(!!).

[0] IIRC the Yesod framework's Warp does well on benchmarks, and when you look at code like https://github.com/yesodweb/wai/blob/master/warp/Network/Wai... you can see the lengths they had to go through to work around the choice of implementation language.

[1] Go has a garbage collector, but exposes the stack/heap distinction more directly than Haskell, so it's easier to write allocation-free code in hot paths.

[2] https://github.com/vsedach/Vacietis

racket and common lisp both offer reader interfaces which allow parsing non-s-expression languages. see https://github.com/vsedach/Vacietis , a c compiler implemented in common lisp which uses the common lisp reader.

Very funny. One might be interested in e.g. Vacietis which does manage to compile enough of C correctly to a higher level language (in this case, Common Lisp) to be interesting.

https://github.com/vsedach/Vacietis - C in CL

C

How about C?

https://news.ycombinator.com/item?id=25531871

https://github.com/vsedach/Vacietis

================

Vacietis is a C compiler for Common Lisp systems.

Vacietis works by loading C code into a Common Lisp runtime as though