C++ FAQs

Don't even _think_ of writing C++ without reading this book first.Yes it sometimes preaches ("arrays are evil") and clubs you over the head about the "one true way" of doing things but there's method behind the madness and it's just trying to save you the pain of finding certain things out the hard way. Suffice it to say that if your program has any new[] or delete[] in it then you need to read this book.Apart from the chapter on arrays it also has masses of tips to help you write reliable, working C++ programs in the real world. One of my favourites is to "imagine that your '~' key has a big alarm attached to it and red lights will flash every time you press it" (see book for reasons why) will go a long way towards helping you avoid mysterious errors and long debugging sessions.Apart from the nitty gritty details of C++ the book also has whole sections on programming philosophy and design techniques, how to organize your code to minimize recompiles and all sorts of things to help you work more effectively with this untamed beast we call C++.Above all, this tries to help you avoid repeating the mistakes and painful learning experiences being suffered by C++ programmers the world over. It's very readable and it _will_ improve your programming technique. Ignore it it at your peril.

C++ jocks like to show off, using sophisticated features of the language. How to figure out what the heck they're doing? This is the book. Not only will you figure out what they're doing, you'll learn why -- and become a better programmer. I would call it a combination reference and tutorial.This book is essential in figuring out what is actually going on, under the covers. As the title says, it's a list of Frequently Asked Questions. For each, there is a short one-line answer, and then, a (much longer) detailed answer, that tells you not only HOW, but WHY, down to the nitty-gritty. It makes no apologies for C++ shortcomings; rather, it points them out and tells you what to do about them. Nearly every question has example code, typically entire programs that can stand alone. Sometimes, there are several examples, illustrating different ways of doing something.Yes, I first printed out and pored through the online version. I learned a lot. Then I went to the bookstore and looked through this one. And felt amazed at my good fortune -- that such a book exists, and that I had actually found it. I couldn't wait to get out of there with it.

Books like this can't get much better. The 3 authors slam through every topic worth mentioning concerning C++ and do it well. There isn't any dogmatic fluff how C++ should take over the world like other books because they aren't caught in the hype of object orientation like the rest of the mindless masses are (e.g. they don't waste their time tearing procedural styles because there are more important things to discuss).The most eminent thing that the blue faqs reflect is common sense. The authors aren't caught in an endless web of technical nonsense. Of course, the nature of the subject IS technical, but you'll notice and like the fact that the authors know their stuff, and answer the questions you have before you ask them to yourself.It is absolutely perfect for folks with some C++ experience. The blue faqs put everything together, covering management perspectives, testing strategies, containers, the big three, and a heck of a lot more. In short, it will cover everything you'll need to know to exploit the C++ system of programming. It is simply a wonderful, useful, organized piece of work.I wouldn't recommend learning C++ off of this book, though. It seems to be aimed more towards individuals that have experience in C++ and design. It might be good for businessmen to gain some insight.There are pieces of helpful code peppered throughout the book. No excercises (it's not a textbook), no CD-ROM comes with it, either. It's written in a fun, understandable, down to Earth conversational style and gets (VERY) technical where needed. For those who want it, do not worry about not finding rigor in it. This is probably the only book that ever has hit a wonderful balance between the mush than those awful "buzz" books offer and good, technical precision.Go to Yahoo! and find the Internet version of the C++ faqs, maintained by the authors of the blue faqs and decide for yourself. That has a ton of good stuff in it, but the blue one has 500% more stuff in it.

While there are new things that come up from time to time, in the overwhelming number of cases, many others have tried to do what you are doing. The hurdles that you face have almost certainly been leapt by someone else. Furthermore, if the problem that you are having is difficult, then others have also tried and most likely struggled. Finally, one of the most efficient ways to learn to program for production is to study those problems that others have frequently faced. It is quite likely that the problems that many others have had will contain some that you will face at some point. Put all of this together, and lists of Frequently Asked Questions or FAQs are one of the most valuable resources that you can have. Outside of questions concerning basic syntax, this is the first reference that I consult when I am stuck on a point in C++. Even if the FAQ is not quite what I am doing, in many cases it is close enough so that I can interpolate the proper path. I use this book as a reference so often that I listed it as one of the best books of the year in my "On Books" column that appeared in the September, 1999 issue of _Journal of Object-Oriented Programming_.

This is the first book I pick up when I need an answer.The entire book is a series of FAQs, organized extremely well. Each topic has its own chapter. Within a chapter, the questions progress from general to specific, often in the same order that they pop into my mind. Each question is followed by a cut-to-the-chase 1-sentence answer, followed by a more detailed explanation. Finding your question in the book is facilitated by a table of contents that lists each FAQ, and a detailed index.I also like the editorializing. ("Arrays are evil.") One reason I find C++ baffling is that there are so many ways to do something. The authors pick a way and tell you why it is better than the alternatives. That's information I can use.As a bonus, there's a chapter on understanding management's perspective. For example, when you're trying to convince management to adopt the object-oriented paradigm, "Show why it's relevant... don't use the 'it will keep the developers happy' approach ... most managers think that they are the people who need to be kept happy ...".Incidentally, when I find the time, I plan to systematically read the book start to finish, just to fill in gaps in my knowledge. It is entertaining enough that I'm actually looking forward to it.