<< 1 >>
Rating: 
Summary: Good For experienced Programmer
Review: If you are an experienced C++ programmer, its the book for you.
Rating:
Summary: Useful implementation (and design) tips.
Review: This book contains a number of very useful columns from the recently deceased C++ report. I found particularly useful the articles on implementation of assignment operators, exception safety, and the inner workings of the standard library containers (Gillan, Austern, Sutter). Actually, they are all really about exception safety - clues on how to write robust code that I needed to learn. The introduction to Lakos' Large Scale Programming tome was also a useful tipoff about physical architecture: I've been using Rational Rose for about 18 months, and now have a better overall picture about what the component diagrams are trying to do apart from represent the receptables my classes get put in. A rule one might apply is: if the cost of the book is less than your time spent to remove the errors you'd make if you didn't read it, then buy it. This one passes the test with ease.
Rating:
Summary: Useful implementation (and design) tips.
Review: This book contains a number of very useful columns from the recently deceased C++ report. I found particularly useful the articles on implementation of assignment operators, exception safety, and the inner workings of the standard library containers (Gillan, Austern, Sutter). Actually, they are all really about exception safety - clues on how to write robust code that I needed to learn. The introduction to Lakos' Large Scale Programming tome was also a useful tipoff about physical architecture: I've been using Rational Rose for about 18 months, and now have a better overall picture about what the component diagrams are trying to do apart from represent the receptables my classes get put in. A rule one might apply is: if the cost of the book is less than your time spent to remove the errors you'd make if you didn't read it, then buy it. This one passes the test with ease.
Rating: 
Summary: Useful book.
Review: You can read the State Pattern in the famous "Design Patterns" book, but the article in this book, "Finite State Machines: A Model of Behavior in C++" by Immo Huneke, explains why the State Pattern is the way it is. That explanation was missing from the "Patterns" book. Also, Robert Martin's intro to this article was helpful. Mr. Martin mentioned he has a freeware "State Machine Compiler". I downloaded it, and it works! Really cool. This one article alone was worth the price of the book.
Rating:
Summary: Useful book.
Review: You can read the State Pattern in the famous "Design Patterns" book, but the article in this book, "Finite State Machines: A Model of Behavior in C++" by Immo Huneke, explains why the State Pattern is the way it is. That explanation was missing from the "Patterns" book. Also, Robert Martin's intro to this article was helpful. Mr. Martin mentioned he has a freeware "State Machine Compiler". I downloaded it, and it works! Really cool. This one article alone was worth the price of the book.
<< 1 >>
| 
