8
Bjarne Stroustrup's Plan for Bringing Safety to C++
(thenewstack.io)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 31 Oct 2023
8 points (90.0% liked)
C & C++
1 readers
3 users here now
founded 5 years ago
MODERATORS
I definitely gave up on C++ when trying to refresh on it you're me too go learn C++8 before jumping in to 14.
If learning something requires learning an old version of it before moving on to the current version, something went very wrong.
It is perfectly ok to start with C++14, in fact probably preferable to starting with anything before C++11. The idioms changed a lot in C++11. I think changes since then have been minor and incremental by comparison.
Sure, today it is. In 2014, though, that wasn't the advice.
When C++11 came out, there was an immediate feeling that the language had received a major overhaul and the best ways to do most things had completely changed. Everything from before that was legacy code, though a lot of it was around. I expect it is still mostly like that.
Or do you mean about Rust? Yes that is new. I still don't understand the attraction of Rust over Ada that well.
No, I mean in 2014 the advice was not to start with the latest. Every source I found on the topic recommended getting familiar with 8 and then increment my way up to 14.
I think the C++11 edition (whichever it was) of Stroustrup's book TC++PL suggested using C++11 immediately. That is what I would have suggested. I used C++ by necessity in a few projects before that, but I didn't start actually somewhat liking it until C++11. Everything before that was ugly legacy code.