More likely than not C is why Sony Pictures is being destroyed. More likely than not C is why a German steel mill has a load of scrap on it's hands where they once had expensive machinery. C is a weapon of mass destruction.
BTW, is VB even a language? :-D
It's not even portable
The idea that these issues would go away if people stopped using C is cute.
I don't hate C. I hate that C devs flatly reject advances in software development.
I also hate behavior just like what you just typed up. Dismissal of my point of solely because it does not match your own.
More likely than not C is why Sony Pictures is being destroyed. More likely than not C is why a German steel mill has a load of scrap on it's hands where they once had expensive machinery. C is a weapon of mass destruction.
Rigby, what language would you recommend for programming small MCU's instead of C/C++?
The idea that these issues would go away if people stopped using C is cute.
Oh I see, this is one of those hypothetical, Wouldn't It Be Nice If arguments.
I want a unicorn.
Rigby, what language would you recommend for programming small MCU's instead of C/C++?
Not a lot of choice, is there. Since all of you are so blindly in love with C to even admit it has issues, I don't see that ever changing.
Sounds a lot like Turbo Pascal, 31 years ago.
Only sort of kidding.
That is how it was marketed. Strong typing. No pointers except where needed. Strings with lengths at the start, bounds checking on arrays better modularity, all the speed of C, a better language for system-level work.
It was also much admired by teachers for doing things 'the right way' and used in tertiary courses (like Java was 10 years ago... what do they use now???).
I sort of liked ir.
Here's a potential replacement for C on micros.
http://dlang.org/comparison.html
...
I see what computers can do, and I see how C is very much unchanged in so many ways after over 40 years.
Computers are supposed to aid us. With C, the computer just gets in the way, lets you lay little traps that no one will notice for years, and almost aids developers in making mistakes. My primary complaint about that is that NO ONE SEEMS TO CARE. Virtually every C developer I've known, when I mention how easy common mistakes are, they respond with something like "yeah, so don't do that." You're sitting at a computer which was partially DESIGNED to detect errors that humans are prone to make and we still rarely use them to detect errors that humans are prone to make, purely because we each have so much misplaced confidence in our own abilities.
The result is that every new C developer makes these mistakes again and again, and we constantly hear about code that is vulnerable to buffer overflow or memcopy exploits or whatever the bug du jour is lately.
We could use the computer to aid us as C developers, yet we choose not to. This is my complaint. We are so full of ourselves to think if we just remember not to do a bad thing that no bad things will happen in our code.
go for visual basic 6 my friend... it has array bound check in every compile option, your problem solved!Every C compiler has a bounds check flag you can enable if you want.BTW, is VB even a language? :-D
It's not even portable
---
Daniel
C is for advanced programmers.
(already 10 pages of on while loops, intriguing)
Quote(already 10 pages of on while loops, intriguing)Yes, and more importantly, amazing.
That's the biggest crock I've heard. If you took 2 seconds to look into the issue you'd see that it's the result of spear phishing: http://arstechnica.com/security/2014/12/computer-intrusion-inflicts-massive-damage-on-german-steel-factory/
thing about dealing with engineers - everything is black and white and answers must be right or wrong.
C is for advanced programmers.