<< 1 >>
Rating: 
Summary: see similar title by same author
Review: see similar title by same autho
Rating:
Summary: To sum up the previous review: dubious
Review: That review is very misleading. Yes, the authors first give a pithy, concise answer to a question that is not so simple. Of course that is not the full answer. What is a downcast? Yes, the first word after that is "trouble" (which leaves an important impression on the reader's mind.) That is immediately followed by 2 paragraphs explaining it in detail, followed by a programming example that is an entire page long. Then that question is followed up by more FAQs such as "Why are downcasts dangerous." (The answer is "they're like walking a high-wire without a safety net". This is followed by another paragraph of explanation.) This is less humorous and "annoying" than it is analogous to the truth and succinct, while leaving a mental image that the reader can retain after reading the detail.Anyway, the book is very highly recommended. Every C++ programmer, even a beginner, should have at least 3 books, and this should be one of them. Different books have different styles. Others to consider are a reference such as Stroustrup's, a "tutorial" such as "Accelerated C++", a "hints and tips" book such as "Effective C++", and a basic book such as Lippman's primer. For those with some C background, "Thinking in C++" by Eckel is very good. The book is available on Amazon as well as free by Eckel on the internet.
Rating:
Summary: To sum up the previous review: dubious
Review: That review is very misleading. Yes, the authors first give a pithy, concise answer to a question that is not so simple. Of course that is not the full answer. What is a downcast? Yes, the first word after that is "trouble" (which leaves an important impression on the reader's mind.) That is immediately followed by 2 paragraphs explaining it in detail, followed by a programming example that is an entire page long. Then that question is followed up by more FAQs such as "Why are downcasts dangerous." (The answer is "they're like walking a high-wire without a safety net". This is followed by another paragraph of explanation.) This is less humorous and "annoying" than it is analogous to the truth and succinct, while leaving a mental image that the reader can retain after reading the detail. Anyway, the book is very highly recommended. Every C++ programmer, even a beginner, should have at least 3 books, and this should be one of them. Different books have different styles. Others to consider are a reference such as Stroustrup's, a "tutorial" such as "Accelerated C++", a "hints and tips" book such as "Effective C++", and a basic book such as Lippman's primer. For those with some C background, "Thinking in C++" by Eckel is very good. The book is available on Amazon as well as free by Eckel on the internet.
Rating:
Summary: Excellent Book - for those whoe wanna know about C++
Review: This books answers all the questions one can imagine about C++. It sure eplains the things which are usually not explained by other books. I suggest this book, to all who are interested in learning C++, as a must read book. It is surely a definite guide to good programming.
Rating: 
Summary: Witty, in an annoying way
Review: While this book provides good information on many basic concepts in C++, many of the author's snappy one-line answers are downright annoying. For example: Q: What is a downcast?
A: Trouble. Or this:
Q: Why is downcast dangerous?
A: It's like walking on a highwire without a safety net. Or this:
Q: What is contravariance?
A: The glue that holds OO together. Many people will find the one-liners amusing, I am sure. Personally I think they are a waste of paper. Good practice should always be making definitive statements in the one-liner, and put the descriptive ones in the paragraph that follows, not the other way round. To sum up: good technical advice, dubious style.
<< 1 >>
| 
