>>71You could just as well make these arguments against the hardware design and manufacture which are also "to blame" for unsafe execution. I think i can write safe code in C, and I'm also certain that safe C-code isn't all that rare. Unsafe C-code isn't rare either. What's your point? This is the reality of programling, something you should stay away from if you don't enjoy the challenge. No one language is going to solve the issues you mention. No one language had and no one language will. Undefined behavior, unsafe execution et cetera is what makes C practical in it's application. And it is typical that people like you don't understand this.
And then a lot of your points are just plain wrong.
Now it happens to be like this, I have some exciting projects coming up with a friend and I'll spend my time programming with C rather than waste my time in this incredibly stupid topic. I'm actually going to have fun. Spend your time with your equally confused C-fanatics in this forum. You and them are a match.
Tone it down a little and take care.