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.
Is it really that confusing though? He's just using a python script that runs the program instead of linking it. Sure the details may be interesting but the high-level concept is obvious
As far as I can tell, it looks like a wrapper for cc1plus (internal GCC tool) and ld that do a custom #define of some input data, compile, extract some data from the binary, and do... something with it. Makes it look like C++ is an interpreted language.
Implementations are orthogonal to languages, there have been C and C++ interpreters since the languages exist, as you can see by looking at BYTE and Dr Dobbs archives looking for compiler developer tools ads.
But some are more suited then others. For example, I believe the C standard to not describe what is supposed to happen when the definition of a function changes.
It doesn't have to, that is an implementation detail or OS specific feature.
Two scenarios where the definition of a function in C changes, are dynamic libraries on OSes that allow reloading the same library multiple times, or self-rewriting code.
Here you stay within the realms of a compiled language implementation, where what happens, is only expecified by compiler specific features, or OS capabilities handling executables and dynamic libraries.
Yes, but it suddenly matters if you execute code in an interpreter, where the user can change any symbol/function definition at anytime. What do you do with a a struct definition, that changes? Do all the functions return something different now? Or does the return type of all the functions change to an anon struct and the name now refers to something different. Stuff like that is what the distinction is between a compiled and an interpreted language.
The same way you deal with them as they come from a dynamic library, and the code gets reloaded on the fly, like on game engines that use compiled C and C++ instead of whatever scripting language.
Compiled code with dynamic replacement during execution,
That's really cool, but I think you still run in situation where its impossible to keep the program running, and/or you need to make decisions which are not described by the language standard.
>
Warning message
If you see the following dialog box, Hot Reload is unable to apply the current edits without restarting. You can choose either to rebuild the app and apply changes (restart) or to continue editing. If you rebuild, all application state is lost. If you continue editing, it's possible that additional changes or corrections might cause Hot Reload to work again.
[Screenshot of the apply changes dialog box]
If you select the Always rebuild when changes can't be applied option in the dialog box, you won't see the dialog box again in the current Visual Studio session, and Visual Studio will automatically rebuild and reload instead of showing the dialog box.
C++ is considered to be a typically compiled language by the majority of people. But you’re right, I should have said that it makes GCC look like a C++ interpreter.
This video doesn't explain what the project does and how it does it. Also it's deliberately misleading the viewer, for example it purposefully incorrectly states that C++ is an interpreted language.
The video is a compliment to the Github repository, the presenter even shows code and brings up the repo in the video. I guess you didn't watch that part and unfortunately you didn't get the joke either.
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.
The whole thing is a joke but presented in a serious manner. The idea is that if you know your program input at compile time you can turn everything into a constexpr which gets evaluated at compile time so your program is "ran" by the compiler instead of at run time. So he built a "runtime" that is actually ran by the compiler around this idea for fun.
> So he built a "runtime" that is actually ran by the compiler around this idea for fun.
Funnily enough, sufficiently enough of C++ is constexpr-able that it was the driving force for compile-time reflection in C++[1], which is not unlike what the author has done.
Although the new syntax is much more readable than what the author chose to do with expression templates, it's still annoying, as is much of C++. But I still like it, so I am decidedly Stockholmed.
it is "simply" a DSL implementing a full custom language that is run at compile time. As far as I can tell the DSL is implemented with the tried-and-true technique of expression templates[1] combined with constant evaluation and unrestricted template value parameters (although these days there are multiple options to implement compile time DSLs, up to compile time parsing of strings).
As to why, I can't pretend to know the author mind, but I suspect they did it because they could, the project itself is the objective.
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.
Open the cc1plus or ld "internal binaries" to be even more confused ;)
Is it really that confusing though? He's just using a python script that runs the program instead of linking it. Sure the details may be interesting but the high-level concept is obvious
Yeah, I was referring to the details. It looks like it calls internally into both tools, but not after doing some messing with the binary sections.
Got roped into watching the whole video. He obviously loves C++. And since I actually enjoyed it, I suppose that also tells something about me.
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.
Seconding AngelScript, but there’s also Squirrel, and a myriad of other C/Lua-like languages. AngelScript’s interop story is really cool, though.
Cling from root
Man, that went way over my head.
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++.
I had good experience with Xeus cling for a notebook interface.
Can't wait for this to be consumed by LLMs.
So confused what this is...
As far as I can tell, it looks like a wrapper for cc1plus (internal GCC tool) and ld that do a custom #define of some input data, compile, extract some data from the binary, and do... something with it. Makes it look like C++ is an interpreted language.
Implementations are orthogonal to languages, there have been C and C++ interpreters since the languages exist, as you can see by looking at BYTE and Dr Dobbs archives looking for compiler developer tools ads.
But some are more suited then others. For example, I believe the C standard to not describe what is supposed to happen when the definition of a function changes.
It doesn't have to, that is an implementation detail or OS specific feature.
Two scenarios where the definition of a function in C changes, are dynamic libraries on OSes that allow reloading the same library multiple times, or self-rewriting code.
Here you stay within the realms of a compiled language implementation, where what happens, is only expecified by compiler specific features, or OS capabilities handling executables and dynamic libraries.
Yes, but it suddenly matters if you execute code in an interpreter, where the user can change any symbol/function definition at anytime. What do you do with a a struct definition, that changes? Do all the functions return something different now? Or does the return type of all the functions change to an anon struct and the name now refers to something different. Stuff like that is what the distinction is between a compiled and an interpreted language.
The same way you deal with them as they come from a dynamic library, and the code gets reloaded on the fly, like on game engines that use compiled C and C++ instead of whatever scripting language.
Compiled code with dynamic replacement during execution,
https://liveplusplus.tech/
https://learn.microsoft.com/en-us/visualstudio/debugger/hot-...
https://dev.epicgames.com/documentation/en-us/unreal-engine/...
Plain interpreters,
https://iel.ucdavis.edu/publication/2006/CUJ_proof.pdf
https://root.cern/
Just some examples.
That's really cool, but I think you still run in situation where its impossible to keep the program running, and/or you need to make decisions which are not described by the language standard.
>
C++ is considered to be a typically compiled language by the majority of people. But you’re right, I should have said that it makes GCC look like a C++ interpreter.
You'll need this https://www.youtube.com/watch?v=cFtymODJEjs
This video doesn't explain what the project does and how it does it. Also it's deliberately misleading the viewer, for example it purposefully incorrectly states that C++ is an interpreted language.
Also the music is way is too loud and sudden.
The video is a compliment to the Github repository, the presenter even shows code and brings up the repo in the video. I guess you didn't watch that part and unfortunately you didn't get the joke either.
Well the video is almost entirely a joke and almost every sentence in it is ironically false; that's the point.
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.
The whole thing is a joke but presented in a serious manner. The idea is that if you know your program input at compile time you can turn everything into a constexpr which gets evaluated at compile time so your program is "ran" by the compiler instead of at run time. So he built a "runtime" that is actually ran by the compiler around this idea for fun.
> So he built a "runtime" that is actually ran by the compiler around this idea for fun.
Funnily enough, sufficiently enough of C++ is constexpr-able that it was the driving force for compile-time reflection in C++[1], which is not unlike what the author has done.
Although the new syntax is much more readable than what the author chose to do with expression templates, it's still annoying, as is much of C++. But I still like it, so I am decidedly Stockholmed.
[1]: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p29...
it is "simply" a DSL implementing a full custom language that is run at compile time. As far as I can tell the DSL is implemented with the tried-and-true technique of expression templates[1] combined with constant evaluation and unrestricted template value parameters (although these days there are multiple options to implement compile time DSLs, up to compile time parsing of strings).
As to why, I can't pretend to know the author mind, but I suspect they did it because they could, the project itself is the objective.
[1] https://en.wikipedia.org/wiki/Expression_templates
Based? Based on what?
Usually means "based on facts".[1]
Here, probably used ironically.
[1] https://www.urbandictionary.com/define.php?term=based
I don't think I've ever seen it used outside of a heavily irony-poisoned context.
So it fits perfectly.
Based.
I love sheaf’s work
Me too. He is so creative. I came across this repo and realized he also made a video about it.
A bit silly, but ok.
great video and source but needs a try-catch block
10/10 no notes.