Best C++ books
looking for a good book that will break C++ down in detail. I've read websites and learned a good amount but the more I learn the more questions I start asking myself and no one to give answers.
one question I have is. How are projects made? Can someone with experience break this down for me? What I think the correct way to do this is like this.
project hamburger // building a burger
-main file // adding class 1-5 together for creating a burger
- class // these files are individual programs that do simple tasks
1st class - making and cooking the patty
2nd class - cutting tomato
3rd class - cutting lettuce
4th class - making bread
5th class - cutting Swiss cheese
is this somewhat correct?
one question I have is. How are projects made? Can someone with experience break this down for me? What I think the correct way to do this is like this.
project hamburger // building a burger
-main file // adding class 1-5 together for creating a burger
- class // these files are individual programs that do simple tasks
1st class - making and cooking the patty
2nd class - cutting tomato
3rd class - cutting lettuce
4th class - making bread
5th class - cutting Swiss cheese
is this somewhat correct?
I'm not certain what you're asking for in the projects, but good books would probably be Stroustrup's "Programming Principles and Practice." It's said to be directed towards beginners. I question that. It's a bit more advanced in parts than I think is reasonable for a beginner to understand without great trouble.
Savitch has a good book for beginners, "Problem Solving with C++" as well. I quite like it. I think it's probably more beginner friendly and detailed than Stroustrup's book, to be honest, but Stroustrup does a VERY good job on emphasizing good design and error checking. If nothing else, you should read Stroustrup's book just for that, and his no-nonsense examples. Though I can't speak for "real-world" programs, I'd be willing to bet his book has examples in it that you'd be far more likely to see in the field. Other books have "cutesy" program examples that don't do much outside of attempt to illustrate the point. If I were still betting, I'd be willing to bet a few veterans would look at a few of the examples and spend a fair bit of time on them.
People love C++ Primer (NOT Primer Plus). It asks more than is reasonable of a beginner, by far, but it also says clearly in the preface it's NOT a beginner book. People still INSIST on mentioning it for beginners, which is why I mention it now, but if you're a beginner looking for a great intro text, I wouldn't recommend it (yet).
Savitch has a good book for beginners, "Problem Solving with C++" as well. I quite like it. I think it's probably more beginner friendly and detailed than Stroustrup's book, to be honest, but Stroustrup does a VERY good job on emphasizing good design and error checking. If nothing else, you should read Stroustrup's book just for that, and his no-nonsense examples. Though I can't speak for "real-world" programs, I'd be willing to bet his book has examples in it that you'd be far more likely to see in the field. Other books have "cutesy" program examples that don't do much outside of attempt to illustrate the point. If I were still betting, I'd be willing to bet a few veterans would look at a few of the examples and spend a fair bit of time on them.
People love C++ Primer (NOT Primer Plus). It asks more than is reasonable of a beginner, by far, but it also says clearly in the preface it's NOT a beginner book. People still INSIST on mentioning it for beginners, which is why I mention it now, but if you're a beginner looking for a great intro text, I wouldn't recommend it (yet).
Thank u, ill check the first 2 books out then later look into the third book.
The project thing was an example on either I was on the right direction or not. I keep reading that it's better to split a project into many small programs then rather having one really big one. But I'm sure how this is possible. I've also read that u use a header file to link to sub file to a main file for compiler. Is that correct?
The project thing was an example on either I was on the right direction or not. I keep reading that it's better to split a project into many small programs then rather having one really big one. But I'm sure how this is possible. I've also read that u use a header file to link to sub file to a main file for compiler. Is that correct?
Topic archived. No new replies allowed.