dotfiles VS cppfront

If you're on MacOS an imgcat tool pairs well with an imgpbcopy tool like this:

https://github.com/williamcotton/dotfiles/blob/master/bin/im...

Then creating a shell function like:

  imgc() {

I started down this path sometime last year with Crafting Interpreters and I’ve gotten obsessed with this entire world since. I wrote a little language [0] using Python Lex Yacc a couple of months ago at work because I wanted an awk-like way to quickly make graphs/charts from the CLI. Then I wrote a parser-as-a-type in TypeScript [1] for the same grammar.

My plan was to take a look at OCaml for future tinkerings with parsers, but man, F# is already looking very familiar between TypeScript and Lex/Yacc-like things.

Thanks for this post, I think I might have a new favorite language in the oven!

[0] https://github.com/williamcotton/dotfiles/blob/master/bin/pl...

[1] https://github.com/williamcotton/dotfiles/blob/master/bin/pl...

CPP2/cppfront:

https://github.com/hsutter/cppfront

I hope we see this in C++26 as optional mode i.e. #safe and #unsafe and same for #impdef or so.

C++23 is done. But C++ is not! In this talk, the author shares his personal perspectives on an ongoing and very active evolution of C++, updates on his cppfront experimental compiler, and why compatibility is essential to the further success of the C++ development.

https://github.com/hsutter/cppfront

But his side project at Microsoft didn't gain traction with gcc, clang, etc and everybody else in the industry. So at this point, the C++ committee will be perceived as "so far behind" ... because there's nothing for them to vote on.

C++ has major flaws that cannot be rectified without serious breaking changes. With that said, Herb has been experimenting with a new cpp frontend with sane defaults [1].

In my opinion, the world is on standby until Anders Hejlsberg feels like tackling a modern, next generation systems language.

[1] https://github.com/hsutter/cppfront