2 ms·
I'm piling on: this is (some of) the worst possible advice for learning C++. It may take a little bit longer to learn how to use the STL container classes, bu
by timr 19y ago
I'm piling on: this is (some of) the worst possible advice for learning C++.
It may take a little bit longer to learn how to use the STL container classes, but the time is well-spent, and you can't make a legitimate claim of "knowing" C++ until you're comfortable with them. They're part of the language!
Bjarne Stroustrup wrote a good paper on learning C++ as its own language. I highly recommend it:
http://www.research.att.com/~bs/new_learning.pdf http://www.research.att.com/~bs/new_learning.pdf
- palish 19y agoMy advice is the worst possible advice, ever? The advice was based on being a professional C++ programmer for the last 3 years and a C++ tinkerer for 5 years before that. I thought there was some merit to it. If it was really that horrible, I apologize.
- timr 19y agoIt's was bad advice. Whether or not it was the "worst possible" advice...well, okay, I'm guilty of exaggeration for effect. There are probably worse ways of learning. Mea culpa. The reason that your advice was so bad, was that you were encouraging someone to lunge headlong into the worst parts of C++ programming, while simultaneously warning them off of the best parts of the language. I've been a C++ programmer since the mid-90s. I learned the language before the STL (or the 1998 standard), and I know from hard experience that C++ with STL is a very different (and far more productive) tool than C++ without STL. In other words, I learned it the way that you suggested, and I know from experience that's the wrong way to do it. (Note: I have edited the original comment to be slightly less extreme.)