Customer Reviews

Learning C++: A Hands-On Approach

5 star:		(2)
4 star:		(3)
3 star:		(1)
2 star:		(0)
1 star:		(1)

 

 

This book is great for intermediate to advanced C programmers who want to learn C++. I'm in my second year of computer science coursework and have taken 3 quarters of C programming, 1 quarter of assembly, and a data structures class and am using this book in my C++ for C programmers class. The first 5 chapters led me through the differences in using C++ to program procedurally vs. using C. The next chapter introduces objects and does an excellent job of transitioning from procedural thinking to objective thinking in addition to teaching the syntax. The book pretty much continues on this path, shedding more light on why the differences between C and C++ exist and how to use C++ to objectify problems and write solid classes.

If you already know an object oriented language and are looking for a C++ reference manual, don't buy this book. If you know procedural programming, preferably C, and want to learn Object Oriented programming, BUY THIS BOOK.

1. This book does not teach you C. You should be knowing C in order to study this. 2. Essentially, this book explains the C++ concepts and coding syntax, and this it does very well. 3. The author takes up an idea, presents it clearly, both in words and with examples (very simple example, at that). 4. It is not pedantic; the ideas are presented crisply. 5. If you know C and want to learn C++ QUICKLY, then go for this book.

I must say I strongly disagree with the other readers, this book is a waste of money. It does assume knowledge of C which is fine (I think anyone trying to learn C++ without prior knowledge and experience in C is in for a difficult journey) and the book generally does an okay job of explaining the differences between C and C++ but after chapter 4 it goes downhill quite fast. For starters it possibly has THE WORST INDEX I'VE EVER SEEN IN A TECHNICAL BOOK. For a technical book I consider the index to be the second most important feature aside from the actual content. Let's say for example I want to find information on the setf() member function. Good luck because it's not in there (it's in the book it's just impossible to find). This book has LOTS of code examples which wood be wonderful if the author could actually write an example of code without always using his favorite /* other details omitted */ comment. You can piece together the omitted details if you don't mind constantly flipping between pages. I however prefer to see a complete idea presented and executed. If you want a good C++ book that has in depth examples and teaches good coding practices get C++ How to Program from Deitel and Deitel. This book is fantastic for learning and for reference. In addition it covers BOTH C and C++.

My college uses this book to teach object oriented programming, so I've been elbow deep in it quite a few times. It's not bad, but it's very concise.

It's not a bad book, but Nagler only tells you something once, and if you don't understand it, you're out of luck. And usually, what you miss is something you need to understand the rest of the chapter. Also, it seems like a lot of important subjects aren't covered in depth, and some subjects are covered more than they really need to be.

I wouldn't recommend this book to anyone who wants to learn c++ unless they're already familiar with the language. If they weren't familiar, I'd suggest adding another book as a reference, since the index in this one isn't that great, and some of the most important parts of the book are only a paragraph or two long.

I had this book on a shelf for about one year. When I started reading it I finished it in a week. This is an excellent introduction to C++ for the person who already knows C. It doesn't teach you how to program but it covers many of the differences between C and C++. In general the book references the Borland Compiler which is more of an annoyance, because this book is not necessarily compiler specific. This book doesn't cover much about designing programs in an object oriented way so that the reader will be forced to learn how to do that from a different source. I felt confident writting C++ code after reading this book.

Every book on a scientific or engineering topic such as C++ is written for a specific audience, and it is generally the responsibility of the Esteemed Reader to assess the fit between the book and his or her familiarity with the topic the book covers. Is the book too advanced, of appropriate difficulty, or not advanced enough? If the book is used as a textbook in course, then it is the responsibility of the instructor to assess this fit. In the case of Eric Nagler's "Learning C++: A Hands-on Approach" the book presupposes a thorough knowledge of the C programming language and experience writing C programs using all features C programming offers. It does not review C, focuses instead on important differences between C and C++, then presents a thorough treatment of C++.

There are books-a-plenty out there on C++. Why choose Nagler's text? First, Nagler's text is up-to-date. As C++ has evolved and been standardized by the ANSI/ISO C++ committee X3J16, Nagler has updated his text and put out new editions. The first edition appeared in 1993, the second in 1997, and the current third edition in 2003. Second, "Learning C++" is thorough. It covers each topic from the generalities and major issues down to the details that may become pitfalls for C++ programmers. The pitfall examples are particularly interesting. Third, this textbook is a well-balanced presentation. It provides clear and succinct explanations of C++ language features and then balances those explanations with concrete C++ programming examples which illustrate the general concepts. Fourth, Nagler's book is a very efficient read. One C++ book after another takes over 1000 pages to explain what Nagler covers thoroughly and clearly in just over 500 pages. Why would anyone want to read over 1000 pages when they could acquire the same insights faster reading just 500? Finally, if the reader has a background in C appropriate for "Learning C++", the book reads and learns like butter. Page for page the text is just packed with valuable information and insights.

Every text book implies specific methods of assimilating its content. In the case of "Learning C++" the method is "active engagement with the material". I found it useful to read the general explanations, study the concrete programming example (sometimes typing it in and running it), and then, if it's a difficult topic, possibly iterating through the explanation and example again to make sure I understand it. Nagler offers a number of study aids throughout. Important points are emphasized with "Caution" and "Summary" boxes in the margin so that it is easy to go back and review a chapter or a topic. If the "Caution" or "Summary" is not clear, it is easy to reread the explanation and example(s) which precede it and get back up to speed. In my experience it would be a mistake to read the explanations and then skip over the concrete programming examples because they complement each other very nicely and hasten the learning process.

All in all, Nagler's "Learning C++: A Hands-on Approach" is a well-written, classic presentation of C++. It is far easier to work with and learn from than many books on the same subject. Just be sure you have a solid background in C.

This is really a very good treatise on C++. You would find no extravagance in text. The author uses concise but focussed examples to clarify the concepts being discussed. If you already know C++, but could be out of touch for some time, this book does a superb job in bringing you at par with your earlier skills. It, aptly, doesnot harp on stuff that are usual, and waste your time and pages. Even if you are new to C++, but have a background in C, this book can teach you C++ in a week, that can earn you a place amongst C++ literates. You learn the fine points of C++ here. I am waiting for its next edition, where the author would discuss about the new features added to the language. Is the author listening?