Is it possible to tangle the Readme into pretty.h? In other words, are the codeblocks in the orgfile exhaustive.

I love the literate way you have explained your thought process in the readme.

I have not decided how I feel in general, but:

> Everyone defines these, so why not provide them?

Honestly, that's fair.

> turn any codebase into a beginner friendly one

Okay then.

I was hoping to see a “this is just for fun” disclaimer but didn’t see one. Please never actually use this in a project that other people will have to read or contribute to.

Wow, neat! The wildest part to me is

> And it’s backwards-compatible with C and all of its libraries!

I can't wait to give it a shot! This looks like a riot.

This project looks really cool! Unfortunately, there’s just way too much magic involved. In my humble opinion, C is simply not the language for this level of magic—extreme use of macros (and hidden behavior in general) is how you end up with hard-to-detect (and hard-to-debug) bugs and security vulnerabilities. As cool as this project looks, I’d never feel comfortable using it in anything serious. A+ for the effort though!

All that is missing is a garbage collector. Should be possible to implement one by overriding malloc & friends?

Being able to control indents for a particular case { right-aligning variable names - while keeping "=" in line can be useful for instance }... Is the perfect example of why indenting should be left for the eye of the reader not the computer.

It's exactly why I find python code difficult - nay impossible - to read at times.

So you are really doing absolutely the opposite of what you are claiming...

Obviously beauty is in the eye of the beholder - but the one thing that C got right was using "{" & "}" to specify code flow.

> if (argc above 1)

I give up.

This is terrifying

This should have been invented 50 years ago!