Practical C++
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 BasicsAh, 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 IIIFrom 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.
Now THATS an oxymoron...
Its the only language that ive had trouble getting
cout "Hello World!";
(or equivalent)
to compile.
NO SIG
It ends with }
Opus: the Swiss army knife of audio codec
He should've used a little of that practical C++ for compression.
Open Letter From Darl McBride:
The code examples in this book are part of the intellectual property owned by SCO. You must pay $650.00 per code example to receive a license that allows you to use our IP. Send check or money order, no cash please.
Thank You,
Darl (Big D)
One bad monkey spoils the whole barrel.
Overall, this is a solid book for an existing programmer to pick up C++ concepts.
I'm not sure what books would be good for non-existing programmers.
Steve
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..
'Practical' and 'C++'...something's not right there. :)
C invented the dangling pointer. And it put the buffer overflow on the map.
Kids these days. You have everything we worked hard for handed to you on a silver platter. You have no idea where these concepts even originated. PHAH!
the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff
Except for all other languages...
Never Politically Correct ~ I prefer the facts If you don't like what I say, get a life, or comment yourself.
Pah!
C and C++ combine all the raw speed and power of assembly with all the grace and smooth design of assembly.
(I heard that somewhere - don't know the original source).
Where's Visual Basic in that list? Forth? Lisp?
And by those numbers, if C is faster than C++, then B must be smoking fast! A comparison of B and A++ would then determine if it's the letter or the added "++" slowing down the run time.
The author obviously has something to hide.
Actually, I think it would go a lot faster without all those gratuitous commas. They really slow down the pre-parser.
John