Learning with older books--dangerous?
After starting to learn what i could call my first programming language (c++) on internet I decided that moving on to restart learning on a book as it could provide me with more information/more to practice with/etc. I've found some books that are more frequently recommended by other people, such as accelerated c++ or c++ for dummies.
I started c++ for dummies 5th ed. and I actually liked it pretty much, but a bit after reading i noticed the book is from 2004, and even suggests to use dev c++..I could be simply using another compiler and follow the same book, but would learning from this be any dangerous? Being outdated is the worst thing I could think to find myself into when in these topics...and since I am not well aware of what all I'll end up knowing, I am not sure if reading something 7 years old will end up helping. I believe it should be able to teach basics like any other book, but, am I wrong?
I started c++ for dummies 5th ed. and I actually liked it pretty much, but a bit after reading i noticed the book is from 2004, and even suggests to use dev c++..I could be simply using another compiler and follow the same book, but would learning from this be any dangerous? Being outdated is the worst thing I could think to find myself into when in these topics...and since I am not well aware of what all I'll end up knowing, I am not sure if reading something 7 years old will end up helping. I believe it should be able to teach basics like any other book, but, am I wrong?
Last edited on
| c++ for dummies |
Why would anyone willingly buy a book that openly acknowledges its reader base is stupid?
As long as the book isn't from before 1998/1999, it won't be too outdated, since that's when the C++ standard was published. That doesn't mean that any newer book is good, it just means that a newer book can in principle be useful.
Just found a quick preview on googlebooks... expecting the title would not really mean what it said xP I havent bought anything yet. In that case I would start with the other one anyways, unless anyone has another recommendation?
Check if it tells you to include iostream or iostream.h. If it has the ".h", it is perhaps old, as these are the old version of the libraries.
Coincidentally, when I was new to C++, I saved money by buying the 4th edition rather than the 5th edition of that one. It told me to use djgpp. For DOS.
(Ultimately, I used "Wiley's Teach yourself C++". I've seen many bad reviews for it, but I found it quite good at the time. Mind you, it didn't discourage exception specifications. Maybe if I looked back there would be other things wrong with it...)
Coincidentally, when I was new to C++, I saved money by buying the 4th edition rather than the 5th edition of that one. It told me to use djgpp. For DOS.
(Ultimately, I used "Wiley's Teach yourself C++". I've seen many bad reviews for it, but I found it quite good at the time. Mind you, it didn't discourage exception specifications. Maybe if I looked back there would be other things wrong with it...)
Last edited on
Actually from my experience C++ for Dummies (4th edition), it was pretty decent. Definitely not the worst book I've read, though it's no C++ primer either (In my opinion, anyway). But ultimately I learned so much more just by researching on the internet.
You are aware that the name is meant to be tongue in cheek, right Helios? xD
You are aware that the name is meant to be tongue in cheek, right Helios? xD
Last edited on
It uses iostream, yet it seems sort of outdated overall. I'll end up considering to read something else. I guess this book is in some way catchier to read, but also seems to lack some seriousness in getting all the info. Someday later I'll judge that more carefully :l. I got tons of time right now anyways, not much of a hurry, so I'll try to find something as complete as possible, no matter if it is harder to read.. I'll remember the suggestion, too : D..thanks
I feel like I've made this same post at least five times, but...
FOR THE LOVE OF GOD DON'T BUY ANY FOR DUMMIES BOOKS! They say they're for dummies, and that means all of the material in it is understandable for a four year old. It may seem friendly, but all "For Dummies" means is that there's less content and subjects aren't explained in depth. If you're going to buy a C++ book make sure it's longer than the four or so hundred pages the for dummies book is. It's a waste of money and your time to buy it. Go for a larger and more in depth book from a respected author, please!
FOR THE LOVE OF GOD DON'T BUY ANY FOR DUMMIES BOOKS! They say they're for dummies, and that means all of the material in it is understandable for a four year old. It may seem friendly, but all "For Dummies" means is that there's less content and subjects aren't explained in depth. If you're going to buy a C++ book make sure it's longer than the four or so hundred pages the for dummies book is. It's a waste of money and your time to buy it. Go for a larger and more in depth book from a respected author, please!
| If you're going to buy a C++ book make sure it's longer than the four or so hundred pages the for dummies book is. |
A book with many hundreds of pages does not mean it's a good book.
| A book with many hundreds of pages does not mean it's a good book. |
The fact of the matter is, you can only cram so much into 400 pages. Assuming the Authors aren't stupid (and if they're writing a book hopefully they aren't) then the 1000 page book will always have more content than the 400 page book. People have written books that are longer than 400 pages on the STL. A good 400 page book can only teach you a fraction of what a good 1000 page book could, so why even bother with the 400 page book? Not to mention I wouldn't describe C++ For Dummies as a "good 400 page book."
I personally found the C++ Primer book by Stanley B. Lippman to be a pretty good book, even for today despite that it's the first edition from 1989 which its age definitely shows and I wouldn't recommend it over more modern books, but it only has around 450 pages.
Books that go into high detail over a thousand pages about the ins and outs of programming are great reference books, but for someone who's learning how to program it can be too in depth. Or you get books that have nearly 1000 pages which are meant to teach beginners how to program, and needlessly spread 100 pages worth of content across 250 pages. There's a difference between a great book to reference, and a great book to learn by.
Books that go into high detail over a thousand pages about the ins and outs of programming are great reference books, but for someone who's learning how to program it can be too in depth. Or you get books that have nearly 1000 pages which are meant to teach beginners how to program, and needlessly spread 100 pages worth of content across 250 pages. There's a difference between a great book to reference, and a great book to learn by.
Last edited on
400 pages is too many pages for the STL, IMO. Anyway, keep reading--you'll find that some authors are very succint and others are just the opposite. For example, Bjarne Stroustrup's writing is nothing but content. You can't afford to skip a word in his sentences. Other authors tell stories and hardly teach anything. Sutter's writing is just about right--informative without being unbearably technical.
Last edited on
Topic archived. No new replies allowed.