Is there a problem learning programming from old books?
I didn't learn anything from my OOP/C++ professor so I decided to learn from this book which I picked from a curated list on StackOverflow and seems like it is exacty what I need, but its from 2000, fucking 17 years old, will it be filled with outdated practices or something?
A C++ book from 2000 may teach you the concepts of C/C++, but it will obviously not teach you C++ 11/14/17 which bring the language up to, what some would consider, a modern language.
Unless you are looking to enter a field of: finance, electronics, high-performance computing, game development, low-level systems or working on legacy code (what I do, it sucks dick), then you should pick a different language.
>>59096360
yes
>>59096801
I'm not looking to land a job with it, I just want to learn for the sake of learning and have a foundation to higher level languages, also maybe have some hobby projects like game dev.
What book would you recommend that is relevant to current practices?
>>59096855
Programming is such a large field, that I think you should tailor your learning to your interests. If you just want to learn OOP then I suggest Python or C#, as they are much easier to learn and work with.
I can't recommend any books for 11/14/17, as I don't know them myself. My degree is in electronics and I work on legacy software, so I specialize in C99 and C++98.
There are many online tutorials for Python that you can try out. I honestly just learned it from the Python website. I don't like books for languages, as I feel the information changes too quickly.
Stroustrup's A Tour of C++ is a good short book on C++11 in general and covers the essentials of OOP.
You can learn the basics from old books just fine, but they do lack all the elegant new features like smart pointers and will instead teach you some unnecessarily complex practices (mostly related to memory management) that you no longer need in modern C++.
>>59096360
Something like C or Lisp, you're fine.
Anything vaguely OOP-like has changed waaay too much in the last decade, except MAYBE arguably Java.
C++ in particular is just now getting around to fixing some of the awful shit from its inception, and it's not even halfway done in that regard. (modules, concepts, unified calling syntax, etc. will still take years more to get done, if ever)
>>59096360
Just shut up and code.
Question, is the book in the OP a good read? I have a copy sitting on my desk.