nullpwr

You said it perfectly, thank you!

I've always noticed that the generation that grew up with smartphones has little understanding of websites, forums, legendary authors, and so on. And this transformation happened very quickly. Frighteningly quickly.

As a member of the older generation, I don't know if I'll be able to fully adapt to these new trends.

Thanks for the clarification. Yes, that's right – that's the job of the compiler/parser/etc.

I like the C programming language. To be honest, I regret not having the knowledge (low skills) to write my own compiler, or at least a standard library. I have some rough sketches on paper of what it should look like, but I can't implement it.

It's difficult to write a law that's "correct" and satisfies all parties. And also lobbying from large companies is quite strong.

> The language should not let you create an an invalid pointer, or at least warn you when you are doing so

completely agree!

Excellent post. But it's addressed to the wrong people.

The problem lies with compilers, not with the language and its specification, or with the creators of the C programming language.

Anyone can write a compiler that transforms all undefined behaviors (UB) into defined behaviors (DB). And your compiler will be used by people, including me.

Ok. Copy that. tnx

I'm not sure if this is related or not. But a few days ago, I saw commits from the "future tense" in some repositories. When you read "committed tomorrow" after a commit, it's not funny at all. I posted a screenshot in the announcement on GitHub.