What do you think?
Rate this book
C++ Primer for C Programmers
Discover all the power of C++ in object-oriented design with the new edition of this best-selling guide! The book offers you a complete, step-by-step introduction to C++ programming and object-oriented analysis and design techniques. You'll learn about the similarities and differences between C and C++, including source code naming conventions, fundamental data types, classes and derived classes, and operators and expressions. Complex C++ topics are explained in simple terms and illustrated by multiple examples, with all sample code followed by its output. The Second Edition of this essential reference now features proven strategies for identifying and solving common design problems, rapid advances in object-oriented design techniques, sample object-oriented program designs, and handy appendices with C++ syntax and OOP programming terminology. Written in a clear, engaging style, the Second Edition of C++ Primer for C Programmers shows you how to use C++ and object-oriented analysis and design techniques to develop efficient systems that are easy to modify and maintain.
392 pages, Hardcover
Published January 1, 1992
1 person is currently reading
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 of 1 review
September 27, 2020
Useful intro to C++ for C programmers with some minor faults.
I've never been a fan of object oriented programming techniques (or object obsfucation techniques as I like to say). But I have to do a little C++ stuff for a project I'm working on and thought a refresher might be helpful. This book works really well for that aspect. If you know C and want a good summary of what's different in C++, and some examples of how it works, this is a great book. The last few chapters however, I didn't like at all. They describe how to think in OO and use OO to design projects. I found that part highly non-intuitive.
When I've read elsewhere about how OO is supposed to work, it's usually the noun/verb analogy - you have things (nouns/objects) and those things do stuff (verbs/methods). But this book takes the opposite approach that the verbs should be the objects. They use an example of a program that needs to operate on customer records and do things like read them, search them, print them, etc. They choose those verbs as the objects! So there's a read object, a search object, and a print object. I found it even more non-intuitive than most other OO descriptions I've run across. If I was forced to implement the example project in OO, I'd create a records object and give read/search/print methods. But, whatever, I don't find OO useful most of the time anyway, so I'm not the one to ask about how it should work!
Anyway, the book gets a thumbs up for its intended purpose which is bringing C programmers up to speed on C++. Recommended (just skip those last few chapters).
I've never been a fan of object oriented programming techniques (or object obsfucation techniques as I like to say). But I have to do a little C++ stuff for a project I'm working on and thought a refresher might be helpful. This book works really well for that aspect. If you know C and want a good summary of what's different in C++, and some examples of how it works, this is a great book. The last few chapters however, I didn't like at all. They describe how to think in OO and use OO to design projects. I found that part highly non-intuitive.
When I've read elsewhere about how OO is supposed to work, it's usually the noun/verb analogy - you have things (nouns/objects) and those things do stuff (verbs/methods). But this book takes the opposite approach that the verbs should be the objects. They use an example of a program that needs to operate on customer records and do things like read them, search them, print them, etc. They choose those verbs as the objects! So there's a read object, a search object, and a print object. I found it even more non-intuitive than most other OO descriptions I've run across. If I was forced to implement the example project in OO, I'd create a records object and give read/search/print methods. But, whatever, I don't find OO useful most of the time anyway, so I'm not the one to ask about how it should work!
Anyway, the book gets a thumbs up for its intended purpose which is bringing C programmers up to speed on C++. Recommended (just skip those last few chapters).
Displaying 1 of 1 review