|
Effective C++: 55 Specific Ways to Improve Your Programs and Designs (3rd Edition) (Addison-Wesley Professional Computing Series) (平装)
by Scott Meyers
| Category:
C++ language, Software development, IT, Technology |
| Market price: ¥ 508.00
MSL price:
¥ 468.00
[ Shop incentives ]
|
| Stock:
Pre-order item, lead time 3-7 weeks upon payment [ COD term does not apply to pre-order items ] |
MSL rating:
 Good for Gifts |
| MSL Pointer Review:
Focusing on productive and practical techniques and offering clearly well thought out advice, this classic on C++ language has always been worth your money and time. |
| If you want us to help you with the right titles you're looking for, or to make reading recommendations based on your needs, please contact our consultants. |
|
| |
AllReviews |
1 2   | Total 2 pages 15 items |
|
|
Steve Schirripa (Software Engineer, Google) (MSL quote), USA
<2007-01-11 00:00>
Every C++ professional needs a copy of Effective C++. It is an absolute must-read for anyone thinking of doing serious C++ development. If you’ve never read Effective C++ and you think you know everything about C++, think again. |
|
|
Gerhard Kreuzer (Research and Development Engineer, Siemens AG) (MSL quote), USA
<2007-01-11 00:00>
C++ and the C++ community have grown up in the last fifteen years, and the third edition of Effective C++ reflects this. The clear and precise style of the book is evidence of Scott’s deep insight and distinctive ability to impart knowledge. |
|
|
Lan Zhongdan (MSL quote), USA
<2007-01-11 00:00>
I think this is the first book a C++ programmer should read after reading a C++ syntax book. Every item is useful. This book is not as complete as C++ faq, but more concise.
Some items need to be updated, however. For example, Item 28, "Use structs to partition the global namespace", you can use namespace now (it is also mentioned at the bottom of the page).
I think the items can be better organized, for example Item 23 "Don't try to return a reference when you must return an object" and item 31 "Never return a reference to a local object or a dereferenced pointer initialized by new within the function" can be combined to one, in item 23, "object" means a local object, it is better to say it explicitely. Also similar items are better to put closer, maybe it is difficult, since many items relate to each other.
This is a book for intermediary level, it lacks some more advanced issues as exception, namespace, etc.
Exceptions are discussed in its following book More Effective C++, however, I would like to mention the discussion in More Effective C++ is not complete neither, up to now, I can find the most advanced discussions about exception in Exceptional C++ by Herb Sutter, which is the book a advanced programmer should read. Discussion about namespace can also be found in this book.
Overall, I think Effective C++ is a good book for a serious programmer to start his/her c++ career, he/she can read More Effective C++ and Exceptional C++ (maybe also Advanced C++ Styles and Idioms and C++ for Real Programmers) for more advanced topics/discussions, and C++ faq for a complete review of C++.
I regret not being able to find a book for comparison of C++ and Java, two most used programming languages. These two languages are similar in syntax, but have different features. For example, auto_ptr exists only for C++ and delegation exists only for Java, The differences of languages affect the design and implementation, Design Patterns discusses the design patterns with C++ and Smalltalk, however, Java is more popular than Smalltalk now and I hope to find a book which discusses the C++ and Java together. A more complete discussion of C++ advanced features is also needed, Herb Sutter is working on this. |
|
|
An American reader (MSL quote), USA
<2007-01-11 00:00>
This is one of the most useful and knowledgeable books on the pitfalls of developing in C++ that I have ever read. This book is not for the beginner developer since most of the items covered here refer to advanced topics such as customer memory management and C++ object oriented best practices. I'd recommend reading some basic C++ syntax based books such as "C++ How to Program" or "C++ from the Ground Up" and then reading some OOAD conceptual books such as The Object-Oriented Approach: Concepts, Systems Development, and Modeling with UML or The Rational Unified Process Made Easy: A Practitioner's Guide to Rational Unified Process to get introduced to concepts. This book goes great with its follow-up book "More Effective C++." |
|
|
Juan Alday (MSL quote), USA
<2007-01-11 00:00>
Everything has been said about this book. It's simple, well structured, and probably the best thing it has is that it doesn't teach you how to code in C++ (that's up to you); it goes through the common mistakes everyone makes (specially professionals), and tells you how to avoid them. I've been using C++ for over 15 years now, and I still go through this book once in a while. I, like others, distrust colleagues that don't know about this book/author. In fact, every time I interview candidates for jobs I ask for a must-have list of books; not knowing about this one is a definite no. As the title of my review says, if you can only buy one C++ book (apart from Stroustrup's), get this one. |
|
|
Abby Beifeld (MSL quote), USA
<2007-01-11 00:00>
After having spent several years programming in C and dabbling in C++ here and there, I felt I had a pretty good grasp of C++. However, after finishing this book, I found myself boldly corrected.
The book covers answers to questions that I hadn't even realized that I should be asking. Reading C++ reference books teach you the syntax but completely hide the level of complexity as to what's really going on behind the scenes. To use a quote from the book "Saying what you mean is only half the battle. The flip side of the coin is understanding what you're saying, and it's just as important."
What happens if you override a non-virtual function? What does private inheritance do and why would you want to use it? What code will the compiler automatically generate for you if you fail to do so yourself? When should you use references to objects versus the objects themselves? The list goes on and on. It covers the topics of Memory Management, Constructors & Destructors, Operator Overloading, Design & Decleration of Classes and Functions, Implementation, Inheritance and Object Oriented Design. But, most importantly, for every answer - there is a logical explanation of “why” things are the way that they are.
Reading this book gave me a new appreciation for the complexity behind C++. It is not a book on syntax, so this should not be the 1st C++ book that you read - but it should “definitely” be the 2nd!
Meyers has an excellent, and amusing(!) writing style which makes the book much easier to read then you'd expect from a technical book. The concepts might still make your brain hurt if you're new to C++, but keep at it - before you write any C++ code you need to understand what's going on behind the scenes and this book will show it to you. |
|
|
David Spellman (MSL quote), USA
<2007-01-11 00:00>
Memorize this book and it will take less time than all the wasted hours you spent debugging your C++ code. Read this book to prepare for a job interview, and you will look like a Guru. I have read this book three times, and it is emminently practical for making you a better programmer.
The C++ programming language can be characterized as a language that gives you enough rope to hang yourself with. Sometimes I wonder why I program in it at all. But at least this book exists to help you do it right.
The only criticism I have seen of the book is the often cited example of using the "this" pointer to have an object delete itself. Okay, lots of people don't agree with Mr. Meyers attempt to justify this, but that is a small issue. There is a ton of good advice. |
|
|
An American reader (MSL quote), USA
<2007-01-11 00:00>
The author has broken from the conventional approach by isolating his content to specific C++ items instead of presenting the entire language. Each point is well written with justifications and examples. The majority of the items (48/50) are must-know concepts for effective C++ software development. Exceptionally meaningful content includes 7 items on constructors, destructors, and assignment operators, 11 items on class design and function declaration, and 10 items on inheritance and object-oriented design. Excellent guidance for selecting the correct approach from amongst a wide-variety of advanced C++ features. Effective C++ is one of the best intermediate level C++ books. |
|
|
Jacob Marner (MSL quote, Denmark
<2007-01-11 00:00>
This book contains a list of no less that 50 pratical tips for the C++ programmer. These tips are basically just common sense, and the advanced C++ will already know the vast majority of them (he should buy the book anyway just for the ones he doesn't know). The beginning C++ programmer will feel overwhelmed by this book so for those it cannot be recommended. It is mainly targeted the intermediate C++ programmer that have learned the language but have not found experience in using it.
My favorite one is the one that tell how to reduce dependencies among files. It is common sense, but I just hadn't thought about it until I read this book. As a result the build time for our company project went down significantly. That was literally "very" valuable advice.
The book is extremely well written (even somewhat entertaining!) and both short and consise. I really liked this book, and I recommend any serious C++ programmer to buy it. |
|
|
Thomas Duff (MSL quote), USA
<2007-01-11 00:00>
This is the type of book that should be available to every programming professional in any programming language... Effective C++ Third Edition by Scott Meyers (Addison-Wesley).
Before we go too much further here, let's have some full disclosure here... I'm not a C++ programmer. This leads to a logical question... What am I doing reviewing a book on C++, then? Well, I've been in IT for over 25 years and I am a professional software developer. I also read a boatload of tech books each year, too. As a result, I can usually tell if a book is going to be worth the money and if it will deliver on the promises it makes. This one does.
If you look at all the Amazon reviews for the second edition of this book, you'll see that everyone agrees it is excellent material. I'll assume the technical information in this edition is just as good. Beyond that, there's a lot to like about the style here. Meyers doesn't attempt to "teach" the language. He assumes you know the fundamentals. His items are focused on how to better understand a particular feature or concept so that you'll be more effective as a developer (hence the title). The writing style is very readable, so it's easy to pick up the concepts between that and the code examples. Something that I found really unique and useful is pretty minor but it works so well. Relevant code and the "Things To Remember" recap at the end of each item are in red text. Doesn't sound like a big deal, but it makes a world of difference in having your eyes drawn to that which is most important. Considering most programming books are black and white, a dash of red really stands out.
If you're a C++ developer with some experience under your belt, this really is the next book you need to take your development to the next level. The people who maintain your code after you and the people who use your programs will thank you. |
|
|
|
1 2 | Total 2 pages 15 items |
|
|
|
|
|
|
