Ebook C++ Gotchas: Avoiding Common Problems in Coding and Design, by Stephen C. Dewhurst
By downloading the on the internet C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst publication here, you will get some advantages not to choose the book establishment. Simply link to the internet as well as begin to download the web page link we share. Now, your C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst prepares to enjoy reading. This is your time and your peacefulness to get all that you desire from this publication C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst
C++ Gotchas: Avoiding Common Problems in Coding and Design, by Stephen C. Dewhurst
Ebook C++ Gotchas: Avoiding Common Problems in Coding and Design, by Stephen C. Dewhurst
This is it guide C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst to be best seller just recently. We give you the most effective offer by getting the stunning book C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst in this web site. This C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst will not just be the sort of book that is hard to discover. In this site, all kinds of publications are given. You could browse title by title, writer by author, and publisher by publisher to find out the most effective book C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst that you can read now.
As one of guide collections to suggest, this C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst has some strong factors for you to read. This publication is quite appropriate with what you require now. Besides, you will likewise love this publication C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst to review because this is one of your referred books to check out. When getting something brand-new based upon experience, amusement, and other lesson, you can use this publication C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst as the bridge. Starting to have reading routine can be undergone from different means and from alternative types of books
In checking out C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst, currently you might not likewise do traditionally. In this contemporary era, device and also computer will assist you a lot. This is the moment for you to open up the device as well as stay in this website. It is the appropriate doing. You could see the connect to download this C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst here, cannot you? Simply click the web link as well as make a deal to download it. You can get to buy guide C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst by online as well as ready to download and install. It is very different with the conventional way by gong to guide establishment around your city.
However, reviewing the book C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst in this website will certainly lead you not to bring the published book almost everywhere you go. Merely keep the book in MMC or computer system disk and also they are readily available to check out whenever. The flourishing air conditioner by reading this soft data of the C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst can be leaded into something new behavior. So now, this is time to prove if reading could boost your life or not. Make C++ Gotchas: Avoiding Common Problems In Coding And Design, By Stephen C. Dewhurst it undoubtedly function as well as get all advantages.
-- Provides intermediate programmers with the practical know-how needed to gain expert status.
-- In the prestigious Addison-Wesley Professional Computing Series!
C++ Gotchas is the latest addition to the distinguished roster of Addison-Wesley's bestselling programming titles, such as Effective C++ and Exceptional C++. While appealing to the same broad audience of intermediate C++ programmers, this book has a completely different approach. The author presents 99 "gotchas" - common and preventable problems in C++ programming and design. The gotchas run the gamut from minor syntactic annoyances to basic design flaws to psychological behavior. The material has been selected based on the author's extensive experience presenting gotchas in his training classes, speaking engagements, and magazine articles. By learning the lessons in this book C++ programmers will save themselves much time and wasted effort. C++ Gotchas is destined to become an invaluable reference to many programmers.
- Sales Rank: #1403425 in Books
- Published on: 2002-12-06
- Released on: 2002-11-26
- Original language: English
- Number of items: 1
- Dimensions: 9.00" h x .70" w x 7.30" l, 1.17 pounds
- Binding: Paperback
- 352 pages
From the Inside Flap
This book is the result of nearly two decades of minor frustrations, serious bugs, late nights, and weekends spent involuntarily at the keyboard. This collection consists of 99 of some of the more common, severe, or interesting C++ gotchas, most of which I have (I'm sorry to say) experienced personally.The term "gotcha" has a rather cloudy history, and a variety of definitions. For the purposes of this book, we'll define C++ gotchas as common and preventable problems in C++ programming and design. The gotchas described here run the gamut from minor syntactic annoyances to basic design flaws to full-blown sociopathic behavior. Almost ten years ago, I started including notes about individual gotchas in my C++ course material. My feeling was that pointing out these common misconceptions and misapplications in apposition to correct use would have the effect of inoculating the student against them, and help to prevent new generations of C++ programmers from repeating the gotchas of the past. By and large, the approach worked, and I was induced to collect sets of related gotchas together for presentation at conferences. These presentations proved to be popular (misery loves company?) and I was encouraged to write a "gotcha" book.Any discussion of avoiding or recovering from C++ gotchas involves other subjects, most commonly design patterns, idioms, and technical details of C++ language features.This is not a book about design patterns, but we often find ourselves referring to patterns as a means of avoiding or recovering from a particular gotcha. Conventionally, the pattern name is capitalized, as in "Template Method" pattern or "Bridge" pattern. When we mention a pattern, we describe its mechanics briefly if they are simple, but delegate detailed discussion of patterns to works devoted to them. Unless otherwise noted, a fuller description of a pattern, as well as a richer discussion of patterns in general, may be found in Design Patterns. Descriptions of the Acyclic Visitor, Monostate, and Null Object patterns may be found in Agile Software Development (see the bibliography).From the perspective of gotchas, design patterns have two important properties. First, they describe proven, successful design techniques that can be customized in a context-dependent way to new design situations. Second, and perhaps more importantly, mentioning the application of a particular pattern serves to document not only the technique that is applied, but also the reasons for its application and the effect of having applied it. For example, when we see that the Bridge pattern has been applied to a design, we know at a simple mechanical level that an abstract data type implementation has been separated into an interface class and an implementation class. Additionally, we know that the reason this was done was to separate strongly the interface from the implementation, so that changes to the implementation will not affect users of the interface. We also know that there is a runtime cost for this separation, how the source code for the abstract data type should be arranged, and many other details. A pattern name is an efficient, unambiguous handle to a wealth of information and experience about a technique, and careful, accurate use of patterns and pattern terminology in design and documentation clarify code and help to prevent gotchas from occurring.C++ is a complex programming language, and the more complex a language is, the more important is the use of idiom in programming. For a programming language, an idiom is a commonly used and generally understood combination of lower-level language features that produces a higher-level construct, in much the same way that patterns do at higher levels of design. Therefore, in C++ we can discuss copy operations, function objects, smart pointers, and throwing an exception without having to specify these concepts at their lowest level of implementation. It is important to note that an idiom is not only a common combination of language features, but also a common set of expectations about how these combined features should behave. What do copy operations mean? What can we expect to happen when an exception is thrown? Much of the advice found in this book involves being aware of and employing idioms in C++ coding and design. Many of the gotchas listed here could be described simply as departing from a particular C++ idiom, and the accompanying solution to the problem could often be described simply as following the appropriate idiom (see Gotcha #10).A significant portion of this book is spent in describing the nuances of certain areas of the C++ language that are commonly misunderstood and frequently lead to gotchas. While some of this material may have an esoteric feel to it, unfamiliarity with these areas of the language is a source of problems and a barrier to expert use of C++. These "dark corners" of the language also make an interesting and profitable study in themselves. They are in the C++ language for a reason, and expert C++ programmers often find use for them in advanced programming and design.Another area of connection between gotchas and design patterns is the similar importance of describing relatively simple instances. Simple patterns are important. In some respects, they may be more important than technically difficult patterns because they are likely to be more commonly employed. The benefits obtained from the pattern description will, therefore, be leveraged over a larger body of code and design. In much the same way, the gotchas described in this book range over a wide range of difficulty, from a simple exhortation to act like a responsible professional (Gotcha #12) to warnings to avoid misunderstanding the dominance rule under virtual inheritance (Gotcha #79). But, as in the analogous case with patterns, acting responsibly is probably more commonly applicable on a day-to-day basis than is the dominance rule.Two common themes run through the presentation. The first is the overriding importance of convention. This is especially important in a complex language like C++. Adherence to established convention allows us to communicate efficiently and accurately with others. The second theme is the recognition that others will maintain the code we write. The maintenance may be direct, so that our code must be readily and generally understood by competent maintainers; or it may be indirect, in which case we must ensure that our code remains correct even as its behavior is modified by remote changes.The gotchas in this book are presented as a collection of short essays, each of which describes a gotcha, or a set of related gotchas, along with suggestions for avoiding or correcting them. I'm not sure that any book about gotchas can be entirely cohesive, due to the anarchistic nature of the subject. However, the gotchas are grouped into chapters according to their general nature or area of (mis)applicability. Additionally, discussion of one gotcha inevitably touches on others. Where it makes sense to do so--and it generally does--I've made these links explicit. Cohesion within each item is sometimes at risk as well. Often it is necessary, before getting to the description of a particular gotcha, to describe the context in which it appears. That description, in turn, may require discussion of a technique, idiom, pattern, or language nuance that may lead us even further afield before we return to the advertised gotcha. I've tried to keep this meandering to a minimum, but it would have been dishonest, I think, to attempt to avoid it entirely. Effective programming in C++ involves intelligent coordination of so many disparate areas, that it's impractical to imagine that one can examine its etiology effectively without involving a similar eclectic collection of topics.It is certainly not necessary--and possibly inadvisable--to read this book straight through from Gotcha #1 to Gotcha #99. Such a concentrated dose of mayhem may put you off programming in C++ altogether. A better approach may be to start with a gotcha that you have experienced or with one that sounds interesting, and follow links to related gotchas. Alternatively, you may sample the gotchas at random.The text employs a number of devices that are intended to clarify the presentation. First, incorrect or inadvisable code is indicated by a grey background, whereas correct and proper code is presented with no background. Second, code that appears in the text has been edited for brevity and clarity. As a result, it is often the case that the examples, as presented, will not compile without additional, supporting code. The source code for non-trivial examples is available from the author's web site: semantics. All such code is indicated in the text by an abbreviated pathname appearing near the code example, as in gotcha00/somecode.cpp.Finally, a warning: The one thing you should not do with gotchas is elevate them to the same status as idioms or patterns. One of the signs that you're using patterns and idiom properly is that the pattern or idiom appropriate to the design or coding context will arise "spontaneously" from your subconscious just when you need it. However, you do not want to encourage a similar spontaneous recall of gotchas, since you're interested in how to produce an effective design or correct code, not how to produce a failed design and buggy code. Rather, learning to recognize a gotcha is analogous to a conditioned response to danger: once burned, twice shy. The recollection of the appropriate gotcha is triggered by its presence; it is not considered and rejected a priori. However, as with matches and firearms, it is not necessary to suffer a burn or a gunshot wound to the head personally to learn how to recognize and avoid a dangerous situation; generally all that's necessary is advance warning. Consider this collection as a means to keep your head in the face of C++ gotchas.Stephen C. DewhurstCarver, MassachusettsJuly 2002 0321125185P07192002
From the Back Cover
"This may well be the best C++ book I have ever read. I was surprised by the amount I learned."
--Matthew Wilson, Development Consultant, Synesis Software
C++ Gotchas is the professional programmer's guide to avoiding and correcting ninety-nine of the most common, destructive, and interesting C++ design and programming errors. It also serves as an inside look at the more subtle C++ features and programming techniques.
This book discusses basic errors present in almost all C++ code, as well as complex mistakes in syntax, preprocessing, conversions, initialization, memory and resource management, polymorphism, class design, and hierarchy design. Each error and its repercussions are explained in context, and the resolution of each problem is detailed and demonstrated.
Author Stephen Dewhurst supplies readers with idioms and design patterns that can be used to generate customized solutions for common problems. Readers will also learn more about commonly misunderstood features of C++ used in advanced programming and design. A companion Web site, located at http://www.semantics.org, includes detailed code samples from the book.
Readers will discover:
- How to escape both common and complex traps associated with C++
- How to produce more reusable, maintainable code
- Advanced C++ programming techniques
- Nuances of the C++ language
C++ Gotchas shows how to navigate through the greatest dangers in C++ programming, and gives programmers the practical know-how they need to gain expert status.
0321125185B10212002
About the Author
Stephen C. Dewhurst was among the first users of C++ at Bell Labs. He has more than twenty years of experience in applying C++ to problem areas such as compiler design, securities trading, e-commerce, and embedded telecommunications. He is the author and coauthor of several books on C++ and is a member of the advisory board for The C++ Source, a contributing editor for C/C++ Users Journal, and a former columnist for C++ Report. He is also the author of two C++ compilers and numerous articles on compiler design and C++ programming techniques.
0321125185AB02022005
Most helpful customer reviews
38 of 43 people found the following review helpful.
Ignore the reviewer from Sweden
By A Customer
Having been in software development for many years, the last twelve using C++, I can say from experience that the author has assembled an accurate collection of problems I encounter over and over again. I have worked with legacy source code from Microsoft, Adobe Systems and other lesser known software companies that have some of the problems described in this book. These instances are not an indication of incompetence on the part of the original programmers, but rather a reflection of the realities of the business: deadlines need to be met and rarely do we have the time fiddle with code to make it into picture perfect C++. And if it works properly as it is, then don't fix something that is not broken.
Beginning C++ programmers will get a lot out of this book. This is especially true if you are migrating from C and need to break a few bad habits. Experienced C++ developers will not get that much out of it, but the author has many interesting points that are worth checking out.
The reviewer from Sweden is either an academic pinhead who has never participated in a large commercial software development effort that someone would actually want to pay money for, or he / she / it stopped reading the book after the first three or four sections.
To sum this book up: If you DON'T need to ask yourself the questions the author addresses in this book, then you are not doing any serious C++ software development!
24 of 27 people found the following review helpful.
A must read
By uniq
This is a wonderful book. Not a usual list of trivial advices and recipes, but a collection of serious considerations on how to write code that will survive years of maintenance.
I haven't come to this conclusion right away. At first, I was a bit irritated by what I had thought were the author's biases and self-confidence, but as I kept reading, I began appreciating and even enjoying his candid and confident style that communicated strong experience of dealing with the issues. Not since the time when the ARM ("The Annotated C++ Reference Manual" by Margaret A. Ellis and Bjarne Stroustrup) and Stroustrup's "The C++ Programming Language" were published years ago have I read a C++ book that impressed me as much! If Stroustrup's books focus on the description of C++ facilities, this book concentrates on its programming practice.The author's knowledge of the C++ standard and the compiler mechanics makes his arguments very compelling.
Although anybody familiar with C++ will benefit from this book since it covers a wide range of C++ features, as well as programming and support issues, the book should appeal most of all to the mature audience: one has to be mature to understand the value in developing a program that will sustain years of maintenance by others rather than the one that will only run most of the time without crashing.
10 of 10 people found the following review helpful.
Save yourself some C++ pain
By Jack D. Herrington
If you can learn from other peoples mistakes then this book will save you a lot of pain. C++ is one of those languages that can dish out the pain if you don't understand what it's doing (and not doing) for you. The book presents 99 gotchas, starting with procedural issues (e.g. useless comments, etc.), but quickly gets into C++ technical issues.
An example is gotcha #70, where you didn't define a virtual destructor in the base class. It's something that the old dogs know to do, but if you didn't know it then you can get stung badly and it will take you a lot of frustration to figure out.
If you liked Effective C++ and More Effective C++ you will probably like this book. Either way, if you are a professional C++ programmer this book can save you a lot of pain.
C++ Gotchas: Avoiding Common Problems in Coding and Design, by Stephen C. Dewhurst PDF
C++ Gotchas: Avoiding Common Problems in Coding and Design, by Stephen C. Dewhurst EPub
C++ Gotchas: Avoiding Common Problems in Coding and Design, by Stephen C. Dewhurst Doc
C++ Gotchas: Avoiding Common Problems in Coding and Design, by Stephen C. Dewhurst iBooks
C++ Gotchas: Avoiding Common Problems in Coding and Design, by Stephen C. Dewhurst rtf
C++ Gotchas: Avoiding Common Problems in Coding and Design, by Stephen C. Dewhurst Mobipocket
C++ Gotchas: Avoiding Common Problems in Coding and Design, by Stephen C. Dewhurst Kindle
Tidak ada komentar:
Posting Komentar