Shop now Shop now Shop now  Up to 50% Off Fashion  Shop all Amazon Fashion Cloud Drive Photos Shop now Learn More Shop now Shop now Shop Fire Shop Kindle Listen with Prime Shop now Shop now

Customer Reviews

4.7 out of 5 stars18
4.7 out of 5 stars
Format: Paperback|Change
Price:£46.99+ Free shipping with Amazon Prime
Your rating(Clear)Rate this item

There was a problem filtering reviews right now. Please try again later.

on 25 March 1999
Have you ever noticed that none of your introductions to C++ ever mention things like header files? This book corrects that omission with a vengeance, taking us deep into the nuts and bolts of real software. It describes things no other book is going to mention (e.g. redundant external include guards, or static nonmember functions to replace private members) and things the object-oriented community prefers to be silent about (e.g., encapsulation in files, not in classes).
Lakos's great strength is in pragmatics; this is advice on programming from someone who has been there. If your project is large enough to need source code control, it's large enough to need this book.
Sometimes the book drifts away from its roots, assuming a dragging academic tone. However, this does not change the overall rating -- a book with no substitutes.
0Comment|9 people found this helpful. Was this review helpful to you?YesNoReport abuse
on 18 January 2002
The vast majority of Programming books follow the latest technology trends - new languages, new products. However a book like this, published five years ago, will be useful for as long as C++ is used for professional software development. I've suffered the pain of worked on multi-million line software projects that don't follow the techniques outlined, and I've converted a medium sized software project to follow the guidelines outlined in the book, and I can confirm that this was one of the most practical computer books I've ever read.
In fact I'd have to say it is more useful and practical than the books of C++ tricks and tips that seem so popular, but focus mainly on intricate details of the language.
Unfortunately it is a heavy read, because Lakos provides the sorts of examples and justifications that you need to "buy in" to his suggestions.
I think the length and indepth nature would intimidate people from reading it. However it is very much worth the effort!
0Comment|8 people found this helpful. Was this review helpful to you?YesNoReport abuse
on 22 June 1999
I second much of what has already been said in the previous reviews. This isn't a book for beginners, and its a tough read, but it contains many items that just aren't dealt with in any other book on C++ I've read. The most important point made is that _anything_ appearing in the C++ header file is part of the physical interface, and changing it will affect clients. As with most issues in programming, there's a trade off to be made between efficiency and insulation (and/or simplicity vs. flexibility), which this book tackles well. I certainly feel more confident about sucessfully translating an OOD into a workable C++ framework after reading and ingesting this book. Highly recommended.
0Comment|5 people found this helpful. Was this review helpful to you?YesNoReport abuse
on 23 February 2007
This book assumes you're already proficient in C++ and basic OOP design principles, and considers design at a level one higher than individual classes. You'll learn how to arrange your classes into modules and packages, and then how to organise communication within and between these higher-level constructs. Nonetheless, the book never forgets that the important thing is working C++ code, not diagrams and acronyms, so it's always practical.

There are two core advantages to the designs discussed in this book: maintaining the correct level of abstraction, and reducing recompilation times. Performance issues always run the risk of becoming outdated fairly quickly, and to a certain extent, some of the timing material is no longer relevant. In particular, Sutter and Alexandrescu, in C++ Coding Standards, explicitly disavow the advocated method of external header guards. Additionally, although namespaces are mentioned, they are not used much, and the older method of using prefixes is recommended instead.

The last part of the book drops down to more low level concerns, such as Schwarz counters, operators, and function arguments. This leans heavily on the likes of Effective C++, C++ Strategy And Tactics and C++ Programming Style, and to be honest, you'd be better off looking in more modern books for up to date best practices. For example, in this book assignment is implemented through the copy-and-destroy idiom, which is nowadays considered to be a mistake.

But this is a big book, and you won't be buying it for the lower-level stuff, but for the large amount of higher level material that makes up the bulk. The main practices and metrics remain extremely relevant, the text is clear and well written. And there just isn't many other places where you can go and read about this sort of stuff. It's a must-read.
0Comment|3 people found this helpful. Was this review helpful to you?YesNoReport abuse
on 1 December 1998
I'm a single developer of about eight years who used to go around thinking that, being alone, the systems I write will always be small, and the interfaces between packages can be casual since I own both ends. Boy was I wrong! Lakos' book is the direct answer to the most persistent problems I've had with quality, maintainability and extensibility for the last year.
Even if you're a C++ genius, I'll bet the section on how redundancy (as in duplicated code) may be desirable will teach you something you didn't realize you needed to learn. And, the extensive coverage of physical insulation shows the path away from the dark side of development that logical design texts hardly even allude to. Read this book!
0Comment|2 people found this helpful. Was this review helpful to you?YesNoReport abuse
on 28 May 1998
This book contains a lot of good hints for things to think about and mistakes to avoid in designing and/or coding a large software projekt. John Lakos hints are very well documented and argumented, they are not just like 'make this, do that'. I really recommend this book to everyone programming something larger than 'Hello World'. Sometimes J. Lakos tends to get a bit long winded when getting to something he thinks is important, but the book is still easy to read and very good to understand.
0Comment|2 people found this helpful. Was this review helpful to you?YesNoReport abuse
on 4 October 2010
If you are serious about nontrivial C++ system design you should buy this book. I have read many books on object oriented desing, design patterns, refactoring and so on. However, none of those books mentioned placed much emphasis on physical design. This is strange, given that a solid physical design is crucial for creating maintainable, understandable components. As mentioned by other reviewers it is a tough read, but that is a small price to pay for the information that is on offer.
0Comment|One person found this helpful. Was this review helpful to you?YesNoReport abuse
on 12 June 2012
Lakos really rubs your nose into the fact that every change to a header file has (potentially far-reaching) consequences. He formally introduces some concepts that every programmer has a vague idea about but never really stops to think about. If you want to write a system with thousands of components and you want to be able to expand and maintain that system for years to come, then this book is an essential read. Every serious software company should own at least one copy.

I do have some problems with the age of the C++ code in the book. Many of his examples are outdated (they were written even before the C++98 standard) and it shows. You have to mentally do the conversion of his examples to more modern C++ (using e.g. the guidelines in C++ Coding Standards : Rules, Guidelines, and Best Practices).

So if you can read past the aging C++ code, this book comes highly recommended to experienced (or aspiring) software architects. I wouldn't recommend it to the novice since it can be daunting at times.
0Comment|Was this review helpful to you?YesNoReport abuse
on 3 August 1998
Many programmers, even if they have been in the industry for a while, still do not realize the importance of how a system physically fits together; what header files go where; where does coupling make sense; and why does the damn thing require a full re-compile just because I added one new error code?
After reading this book, you will know. If you follow the advice, your project will compile faster; changes will be easier, and you should be able to slice off any part of your project to re-use somewhere else. This book gives knowledge previously only learned "the hard way" and never taught in college. I just wish it was more concise; the wordiness lost it a star.
0Comment|Was this review helpful to you?YesNoReport abuse
on 14 December 1998
After flipping through the pages of this book for two minutes, I knew that a miracle had occured. I have avoided buying many pathetically simple C++ books that introduce nothing more complex than the famous and ever annoying ATM machine example or the famous and even more annoying Shape/Square/ Circle example. Is there a C++ project that isn't large? Those are the only kind that I have worked on!! One C++ project that I worked on filled volumes of notebooks and took 3 hours to compile. This book has taught me things that no class or book ever has. Buy it!
0Comment|Was this review helpful to you?YesNoReport abuse

Send us feedback

How can we make Amazon Customer Reviews better for you?
Let us know here.

Sponsored Links

  (What is this?)