C and C++ Code Capsules: A Guide for Practitioners (Prentice...

Features

• Cover Type: Paperback with 570 pages
• Published by: Prentice Hall PTR December 21, 1997
• Written in: English
• ISBN 10 Number: 0135917859
• ISBN 13 Number: 978-0135917855
• Book Dimensions: 9.1 x 7 x 1 inches
• Weighs: 1.8 pounds

Book Description
This book shares the hard-won wisdom of a highly-successful C++/C programmer - along with a large collection of ANSI-compliant programs that illustrate the true power of C++.This book includes a wide variety of ideas, tips and techniques for programmers of all skill levels. It presents little-known facts about pointers and the preprocessor that are a must for the professional developer. It offers tips and techniques for more effective use of abstraction, templates, bit manipulation, visibility, control structures and exceptions. The book also shows how to make the most of the Standard C and Standard C++ libraries, covering containers and iterators; algorithms; text and file processing; time and date processing; and memory management.For C++ and C professional developers, consultants, faculty and students of all skill levels.

Book Info
With an extensive collection of ISO-compliant programs, the author illustrates the true power of C++. Presents valuable techniques for making the most of pointers, the preprocessor, abstraction, templates, bit manipulation, visibility, control structures and exceptions. Paper.

Reader Reviews
I had high hopes for this book. Great author, great recommendations. Unfortunately I was dissapointed in his treatment of the subject matter. I think this book should have gotten rid of all pretense of discussing C, which I believe it does a bad job at. Getting rid of the C code would have made many of the examples irrelevant and/or clearer. For example, Mr Allison tells C++ programmers that to include old Standard C headers you now have to prefix a c to the filename and remove the .h (<stdio.h> would become <cstdio>). This is great information, but confusing because in the next example he uses <stdio.h> again. Something that was very annoying was the page layout. The examples and tables were all over the place. The text would often get cut up by several pages of code, which looks much like the text (similar font and size). The tables were also too far away from the discussion to be useful. I found I would just take his word on what he claimed and would skip the tables when I eventually found them. That is a great shame because that has nothing to do with his writing. I waded through the bad page layout and what I consider to be inconsistent usage of C and C++ because on the whole the book provides up-to-date information (real Std C++), but I would not say that this is a book for practitioning programmers, more like for people who want to start using their C++ compilers for more than simply a C compiler. Comment | | (Report this)