Practical C++

← Back to Stories (view on slashdot.org)

Posted by timothy on Wednesday February 18, 2004 @05:23AM from the practice dept.

jsight writes with his review of Rob McGregor's Practical C++, published by QUE. He writes "Some books attempt to do one thing really well, and others attempt a little of everything. This book is clearly an example of the latter, in full force. Weighing in at a hefty 900 pages, you would expect this book to be crammed with chapters and details on every aspect of the STL and basic C++. In the following review, I am going to cover where it succeeds in doing this, and where it fails." (This book has been out for a few years; what books would make more sense today for a C++ learner's library?) Practical C++ author Rob McGregor pages 900 publisher QUE rating 7/10 reviewer Jess Sightler ISBN 0789721449 summary Provides a practical guidebook to learning C++ Section I -- Programming 101 At first glance, the book appears to be written for people with experience programming, however reading through this section clearly dispels that myth. Here we have a section which goes over everything from for loops to if conditionals while simultaneously using verbose, duplicitous language at every step. Perhaps this was intended as a means of reinforcement, however, it seems most of the effort here would be wasted.

The technical depth is what you would expect for a novice, but without enough hand-holding and examples to make a novice feel comfortable. Making matters worse, there are numerous typos in this section, including quite a few in the examples (making them uncompilable without corrections). Some of these appear to be type-setting errors, however, there are enough to potentially confuse novice developers.

I believe that the combination of weak examples, and significant typographical errors are strong enough to give a novice much difficulty in learning the C++ language.

Having said that, the section should be provide no difficulty for any programmer with a good knowledge of any vaguely similar language (eg, Perl, Java, PHP, etc).

Section II -- Beyond the Basics

Ah, now we're getting down to Brass Tacks... this section goes over everything from Function overloading to Structure and Unions. The section on function members within structures also does an excellent job of preparing the reader for the upcoming introduction of Object Oriented concepts.

The sections on Memory management, both from an allocation standpoint, and from a bit manipulation standpoint are first-rate. Details are perhaps not as strong as they could have been, however the material is very accessible, and clearly described.

Probably my only complaint with this chapter is the overly general section on compiling and debugging programs. However, as this book does attempt to be somewhat compiler/debugger agnostic, this is forgivable. From here, we dive into the real power of C++, Object Orientation.

Section III

From the beginning, this book treats Objects as an extension of the structure syntax taught previously (with the default of Public switched to Private). This, along with the classic Plans vs. Product description of the difference between a Class and an Object are quite clear and robust.

Again, this is a solid chapter, describing the details of getting a system of classes up and running, as well as some sample data structure implementations.

And then finally, the last section is a slightly less than 200 page description of the STL. This section is probably the book's weakest part, as it is just strong enough to give you a taste of what is available, but often not strong enough to grasp the details. It's a good start, but much more attention should have been made to this subject (potentially even at the cost of some of the wasted words on how a 'for' loop works). It makes a decent introduction for someone with very limited STL background, however, there is not enough depth to reach a strong level of understanding here.

Summary Overall, this is a solid book for an existing programmer to pick up C++ concepts. A programmer with a strong knowledge of an existing procedural language (such as C) would have no trouble digesting the concepts of this book. Having said that, the poor typographical issues, and verbose wording often muddle an otherwise good book.

You can purchase Practical C++ from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

9 of 307 comments (clear)

Book spoiler by jmv · 2004-02-18 05:26 · Score: 5, Funny

It ends with }

--
Opus: the Swiss army knife of audio codec
Re:"Practical C++" by Anonymous Coward · 2004-02-18 05:27 · Score: 5, Funny

And your mother too

My mother is in fact a software developer and has no problems getting a "Hello World" to compile.
old!=obsolete by RLiegh · 2004-02-18 05:28 · Score: 5, Insightful

If you're talking about the specifics of a language to the point where the book you're reading is going to be obsolete after the next standards commitee meets--maybe you're reading the wrong book?

However, if the book you're reading concentrates on the principlas, instead of the individual bits and pieces, age shouldn't matter.

They still use the ritchie book after all, right?
Best learner's C++? by FortKnox · 2004-02-18 05:29 · Score: 5, Informative

(This book has been out for a few years; what books would make more sense today for a C++ learner's library?)

Best learner's C++ book has to be "Thinking in C++" by Bruce Eckel. I always touted his "Thinking in Java" as the premier book for the learning java developer, but his success started with TiC++. Best of all? Its available free electronically on his website (but I always went out and spent the $30 for the paperback version to support him).

If you pick up the book, you'll understand the language just a little more. He writes the book just how you'd like to learn, not like some math book that blandly gives out information in a manner that puts you to sleep. You can thank me later after reading it ;-)

--
Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
Re:Cease and Desist by Patrik_AKA_RedX · 2004-02-18 05:41 · Score: 5, Funny

$650.00 per code example
Lets assume 350 code examples, that makes $227,500
A hit-man cost about $30,000. hmmm....
Sorry Darl McBride, it's not personaly, it's just economics.
This book has been out a few years.. by osullish · 2004-02-18 05:42 · Score: 5, Funny

Next review, punchcards in a nutshell (It being an O'Reilly book will have a T-Rex on the cover) :-)

--
It's hard enough to remember my opinions, never mind the reasons for them..
Enough with C++/C/Java books! We need wider topics by Anonymous Coward · 2004-02-18 05:57 · Score: 5, Insightful

Isn't it time we start seeing reviews of books other than C/C++/Java/Perl/C#/HTML?

I am a hard core C++ person myself, but even I am fed up with the series of similar books on these PLs.

There are many other topics in programming that deserve better attention by the /. developer community. Examples from the top of my head:

Books on

- Code optimization techniques (both for C/C++ & assembly level and optimization for web programming and DB programming)

- Algorithms and data structures - this one will never go away whatever high level garbage collecting foolproof language/framework you end up using.

- Software design topics (design patterns and its relatives, UML, alternative paradigms such as extreme programming)

- Software project management topics ...

Come on people!
Re:Cease and Desist by SW6 · 2004-02-18 05:57 · Score: 5, Funny

Lets assume 350 code examples, that makes $227,500
A hit-man cost about $30,000. hmmm....
Sorry Darl McBride, it's not personaly, it's just economics.
I clearly need to move to a nicer area. The going rate for a hit round here is less than a tenth of that. And the body would probably dissolve in the river...
Re:C++ had its day...and it is today by dmeranda · 2004-02-18 06:40 · Score: 5, Insightful

I find that those who write off C++ really don't know the language, or at least the "modern" standardized language. C++ is incredibly powerful, and if you use solid OO techniques you really shouldn't have many issues with memory management. At least in C++ (as apposed to Java) the language guarantees that all destructors will be called and with well defined ordering. That allows you to use resource allocation patterns that greatly simplify memory manangement or resource issues entirely.

Although you can compare pure Java with C++ as languages, it is meaningless to compare a Java framework/JDK such as J2EE with C++, as the former is an entire environment, not just the underlying language. There's lots of stuff that C++ does better than Java (generics/templates, destructors, high-performance containers, abstract algorithms). Not to mention that C++ is a completely standardized and *free* language, whereas Java is a fast moving pseudo non-free standard.

Oh, and the syntax problems you complain about are not really all that different from Java, or even C#. Yes, they are each somewhat different and some have cleaner syntaxes for specific issues, but in the grand scheme of computer languages they are almost the same. And there are syntax problems with Java too which C++ doesn't suffer...they are both strongly based upon a C foundation, like C#, Javascript, etc.

And yes, I've written very large C++ projects with many developers very successfully, and C++ has proven to be a very nice language indeed as long as you take the initial time to learn it correctly rather than out of a C++ for Dummy's tutorial.

Now if you want to talk high-level languages (both Java and C++ are low-level of approximately the same power), then you should be talking about something like Python, or more academically Haskell. But Java is by no means a high level language, just as C++ is not.