Post

Why do you say that? I mean... I for one can see the results of your efforts pushing C to the goal of becoming a better, more ergonomic and safer language. And the more I learn about the history of the language, I feel like you've made the impossible happen multiple times, in a very positive way.

I don't disagree, and it's not that I don't like being on the Committee to help. It just feels like a "The Bill Is Coming Due" moment, and it feels a bit awkward to be here for the Bill Paying moment and not the Free Fun Party moments.

I think I see what you mean. Hmm. Yeah, no, there are going to be people who're only going to see a person to blame (as opposed to someone who's worked more than most, to fix things older than themselves). Take care. I hope you don't meet one of those in person. Btw is your ko-fi still up? :)

Either way, even if every diehard C person will take ~no responsibility and just blame the software and blame the PHP people (as per usual), as a Reasonable Adult who is tangentially related to this I think I need to get Defer and a bunch of other things over the finish line.

The PHP thing feels like I can almost read a 20 year old mailing list message from some hardcore C programmer about how "i don't need no c++! an exception is just a longjmp and i can emulate that perfectly with a couple macros"

Unforutnately it's less about just cleanup issues, and more about behavioral semantics for whole-program, whole-process, and whole-thread things. Some of the larger architectural issues are using longjmp on request-local OOM, but not full-process OOM. How that is handled changes program properties!