I wish all projects like these had some sort of documentation as to how they worked. All I can see is that the `-B` flag tells GCC to look in the ased directory for internal binaries (cc1plus and ld), but anything other than that would require more than the few minutes I have to look into.
It's also really interesting to see the audience this is reaching. The issues on the GitHub repository are quite telling.
Would anyone like to explain in text form how this works? I've got as far as the use of <{ meaning to run at compile time, so the whole thing is going to be one of those template metaprogramming stunts.
13 comments
[ 4.6 ms ] story [ 42.3 ms ] threadIt's also really interesting to see the audience this is reaching. The issues on the GitHub repository are quite telling.
But if you just want to run C++ in a REPL, you can use Clang-Repl <https://clang.llvm.org/docs/ClangRepl.html> which uses the LLVM JIT to "interpret" C++.
Also read up on sheafification really quick. Neither Firefox nor Chrome seem aware of it (red underline), so there.
Edit: If anyone is actually interested in interpreted C++, I think AngelScript is the most practical way for this.