C Traps and Pitfalls [Paperback]

Andrew Koenig (Author)

Book Description

ISBN-10: 0201179288 | ISBN-13: 978-0201179286 | Publication Date: January 11, 1989 | Edition: 1

Even C experts come across problems that require days ofdebugging to fix. This book helps to prevent such problems byshowing how C programmers get themselves into trouble. Each ofthe book's many examples has trapped a professional programmer. In addition to its examples, C Traps and Pitfalls offers adviceon: *avoiding off-by-one errors *understanding and constructing function declarations *understanding the subtle relationship between pointers andarrays Distilled from the author's experience over a decade ofprogramming in C, this book is an ideal resource for anyone,novice or expert, who has ever written a C program. 0201179288B04062001

Editorial Reviews

Amazon.com Review

C Traps and Pitfalls teaches how the peculiarities of the C language make it easy for the intended behavior of a program and the actual behavior of a program to differ. The book's experienced author, Koenig, follows up with examples and helpful advice on many of these "pitfalls." Each chapter includes exercises for contemplation with accompanying discussions at the end of the book.

From the Inside Flap

Tools that are comfortable after experience are often more difficult to learn at first than those that feel right immediately. Student pilots start out overcontrolling, turning first flights into roller-coaster rides, until they learn how light a touch flying really requires. Training wheels on a bicycle make it easier for a novice to ride, but get in the way after that.

So it is also with programming languages. Every programming language has aspects that are most likely to cause trouble for people not yet thoroughly familiar with them. These aspects vary from one language to another, but are surprisingly constant from one programmer to another. Thus the idea of collecting them.

My first effort to collect such problems was in 1977, when I gave a talk called PL/I Traps and Pitfalls at the SHARE (IBM mainframe users' group) meeting in Washington, DC. That was shortly after I moved from Columbia University, where people used PL/I heavily, to AT&T Bell Laboratories, where people use C heavily. The decade that followed gave me ample experience in how C programmers (including me) can get themselves into trouble if they're not certain of what they're doing.

I started collecting C problems in 1985 and published the collection as an internal paper at the end of that year. The response astonished me: more than 2,000 people requested copies of the paper from the Bell Labs library. That convinced me to expand the paper into this book.

What This Book Is

C Traps And Pitfalls aims to encourage defensive programming by showing how other people, even experienced professionals, have gotten themselves into trouble. These mistakes are generally easy to avoid once seen and understood, so the emphasis is on specific examples rather than generalities.

This book belongs on your shelf if you are using C at all seriously, even if you are an expert: many of the professional C programmers who saw early drafts said things like "that bug bit me just last week!" If you are teaching a course that uses C, it belongs at the top of your supplementary reading list. What This Book Is Not

This book is not a criticism of C. Programmers can get themselves into trouble in any language. I have tried here to distill a decade of C experience into a compact form in the hope that you, the reader, will be able to avoid some of the stupid mistakes I've made and seen others make.

This book is not a cookbook. Errors cannot be avoided by recipe. If they could, we could eliminate automobile accidents by plastering the countryside with "Drive Carefully" signs! People learn most effectively through experience--their own or someone else's. Merely understanding how a particular kind of mistake is possible is a big step on the way to avoiding it in the future.

This book is not intended to teach you how to program in C (see Kernighan and Ritchie: The C Programming Language, Second Edition, Prentice-Hall 1988), nor is it a reference manual (see Harbison and Steele: C: A Reference Manual, Second Edition, Prentice-Hall, 1987). It does not mention algorithms or data structures (see Van Wyk: Data Structures And C Programs, Addison-Wesley 1988), and only briefly discusses portability (see Horton: How To Write Portable Programs In C., Prentice-Hall 1989) and operating system interfaces (see Kernighan and Pike: The Unix Programming Environment, Prentice-Hall 1984). The problems mentioned are real, although often shortened (for a collection of composed C problems see Feuer: The C Puzzle Book, Prentice-Hall 1982). It is neither a dictionary nor an encyclopedia; I have kept it short to encourage you to read it all. Your Name in Lights

I'm sure I've missed some pitfalls. If you find one I've missed, please contact me via Addison-Wesley. I may well include your discovery, with an acknowledgement, in a future edition. A Word about ANSI C

As I write this, the ANSI C standard is not yet final. It is technically incorrect to refer to "ANSI C" until the ANSI committee finishes its work. In practice, though, the ANSI standard is far enough along that nothing I say about ANSI C is likely to change. C compilers are already available that implement many of the significant improvements contemplated by the ANSI committee.

Don't worry if your C implementation does not support the ANSI function syntax mentioned here: it is easy enough to understand the parts of the examples where it matters, and you can fall into the traps described there regardless of what version of C you use. Acknowledgements

A collection like this could not possibly have been made in isolation. People who have pointed out particular pitfalls include Steve Bellovin, Mark Brader, Luca Cardelli, Larry Cipriani, Guy Harris and Steve Johnson, Phil Karn, Dave Kristol, George W. Leach, Doug McIlroy, Barbara Moo, Rob Pike, Jim Reeds, Dennis Ritchie, Janet Sirkis, Richard Stevens, Bjarne Stroustrup, Ephraim Vishnaic, and one contributor who wishes to remain anonymous. For brevity, I've mentioned only the first person to report any particular problem to me. Of course, I doubt any of the people I've mentioned actually invented the programming errors they pointed out to me, and if they did I doubt they'd admit it! I know I've made many of them myself too, some several times.

Useful editorial suggestions came from Steve Bellovin, Jim Coplien, Marc Donner, Jon Forrest, Brian Kernighan, Doug McIlroy, Barbara Moo, Rob Murray, Bob Richton, Dennis Ritchie, Jonathan Shapiro, and several anonymous reviewers. Lee McMahon and Ed Sitar pointed out what would otherwise have ben embarrassing typographical errors in early drafts of the manuscript. Dave Prosser clarified many fine points of ANSI C for me. Brian Kernighan supplied invaluable typesetting tools and assistance.

It has been a delight to work with the people at Addison-Wesley, including Jim DeWolf, Mary Dyer, Lorraine Ferrier, Katherine Harutunian, Marshall Henrichs, Debbie Lafferty, Keith Wollman, and Helen Wythe. I'm sure they've gained from the aid of others whom I haven't met.

I am particularly grateful to the enlightened managers at AT&T Bell Laboratories who made it possible for me to write this book at all, including Steve Chappell, Bob Factor, Wayne Hunt, Rob Murray, Will Smith, Dan Stanzione, and Eric Sumner.

The title of this book was suggested by Robert Sheckley's science-fiction anthology The People Trap and Other Pitfalls, Snares, Devices and Delusions (as well as Two Sniggles and a Contrivance), published by Dell Books in 1968. 0201179288P04062001

See all Editorial Reviews

Product Details

• Paperback: 160 pages
• Publisher: Addison-Wesley Professional; 1 edition (January 11, 1989)
• Language: English
• ISBN-10: 0201179288
• ISBN-13: 978-0201179286
• Product Dimensions: 9.2 x 6.2 x 0.4 inches
• Shipping Weight: 8.5 ounces (View shipping rates and policies)
• Average Customer Review: 4.0 out of 5 stars  See all reviews (12 customer reviews)
• Amazon Best Sellers Rank: #148,302 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

19 of 19 people found the following review helpful:

5.0 out of 5 stars You must read this book., December 27, 1999

By 

From_Plano_TX "a_customer_from_plano" (Plano, TX USA) - See all my reviews

This review is from: C Traps and Pitfalls (Paperback)

If you program in C or C++, you must read this book if you want to consider yourself a superior programmer. If you are a college student, definitely read this book. Koenig fills in a lot of gaps left by authors of introductory books on C or C++. Why do I mention C++? Because C++ is far more than just objects and classes. The lower level implementation of functions is still basically C programming. He includes chapters on linkage, the preprocessor, and portability. It is a short book that is definitely worth reading.

18 of 19 people found the following review helpful:

5.0 out of 5 stars Enormously entertaining and exceedingly helpful!, May 13, 1997

By A Customer

This review is from: C Traps and Pitfalls (Paperback)

This is among the five "must have" books on the astute C programmer's bookshelf. Actually, it spends little time on the shelf since one refers to it time and time again. This slim volume packs a lot of information about those "gotchas" that still "getcha" (when you least expect it). The Introduction is "Chapter 0", your first hint that Koenig knows and respects the subject. His treatment of unscrambling complex declarations is especially good.

Why a 9 instead of a 10? Simple. Andy: please release a new version! The ANSI/ISO standard is almost ten years old. :)

8 of 8 people found the following review helpful:

2.0 out of 5 stars Good book for novice C programmers, November 21, 2008

By 

scott-gamer "scott-gamer" (New England) - See all my reviews

This review is from: C Traps and Pitfalls (Paperback)

I'd recommend this book for novice C programmers, people with two or less years of coding experience. However, this 1989 book focuses on pre-ANSI C, so the novice would need to be guided by someone that knows the history of C. Some of his statements are false when applied to ANSI C with prototypes (e.g., p.139, it _is_ possible to pass a char argument, if there is a function prototype). I read through and did the problems in this slim book in about three hours. It does have a few nuggets of value, and introduced me to a bug I'd not seen before, the reverse of the "= for ==" bug:
while( (x == fgetc(f)) != EOF )