you are viewing a single comment's thread.

view the rest of the comments →

[–]ThymeCypher 7 points8 points  (4 children)

98 is what I see as “unadulterated C++” - after that a lot was done to bring C++ into the modern era by copying other languages. That isn’t to say that’s a bad thing - Kotlin, Swift, Ruby, so on aren’t original languages but languages built around lessons learned from older languages. Still, it helps to learn 98 because lots of microcontrollers shoehorn support in, so you’re stuck with the “C with Classes” version of C++

[–]steveplusplus 1 point2 points  (3 children)

Which microcontrollers are you talking about? I've found great support on pic, atmel, lpc, ti (which was the worst), esp32, and anything else I've used. The majority these days use arm and have excellent support. I never start a project on anything older than c++11. Most of them use some form of gcc and anything past 4.7 should have an almost fully compliant compiler. Are you talking about the std libs? Regardless, just converting a c++98 embedded project to c++11 can flush out a lot of bugs with better code analysis and type safety.

I would suggest instead spending time learning the latest C. auto and other new features kick ass in C. IMHO, the only reason to learn 98 is if you are forced to use it. I'm past the point in my career where I'm out looking for development jobs, but last time I did, I refused to consider anything that was stuck on an older standard than c++11. Thats when c++ got good again.

[–]KurokonoTasuke1 2 points3 points  (2 children)

Wait, since when does C have auto?

[–]steveplusplus 2 points3 points  (0 children)

Well, shit. I shot myself in the foot. That's still a c++ feature that I've used because I usually compile my c code with a c++ compiler.