clauf VS picoc

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.

I'm currently writing an interpreter for C, I plan on adding a JIT at some point as well: https://github.com/foonathan/clauf

I've continued working on developing my C interpreter: https://github.com/foonathan/clauf

I've been working on a generic bytecode interpreter the last couple of months. It reached a point where I needed to test it in a real compiler, so I've started writing a C interpreter.

Source code is available here: https://github.com/foonathan/clauf

and picoc, but it also features interactive shell

I would like to try this C REPL: https://github.com/jpoirier/picoc

You can. People have written an interpreter for C, and you could write a compiler for Python.

Yeah, I would not choose to learn the C-shell simply because it shares a letter with the compiled language. You might be better served learning Pike or PicoC.

But don't get caught up in the VM definition, the whole act of compiling to VM bytecode and then to native is just another step in the chain. For example here is a C interpreter that lets you do the same thing, without intermediate bytecode.

Can we please cut the bullshit. By that logic no language is compiled. Because behold, a C interpreter: https://github.com/jpoirier/picoc

Languages can have a compiler, an interpreter, or both. Just because a language is commonly thought of as 'compiled' doesn't mean you can't write an interpreter for it, or vice versa. There's even C interpreters for crying out loud https://github.com/jpoirier/picoc .