- Paperback: 160 pages
- Publisher: McGraw-Hill Inc.,US; 2nd Revised edition edition (1 Jun 1978)
- Language English
- ISBN-10: 0070342075
- ISBN-13: 978-0070342071
- Product Dimensions: 22.6 x 15 x 0.8 cm
- Average Customer Review: 2.5 out of 5 stars See all reviews (2 customer reviews)
- Amazon Bestsellers Rank: 1,006,846 in Books (See Top 100 in Books)
| ||||||||||||||||||||
 Trade In this Item for up to £30.15
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in Elements of Programming Style for an Amazon.co.uk gift card of up to £30.15, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Product details |
More About the Authors
Discover books, learn about writers, and more.
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
6 of 7 people found the following review helpful
Format:Paperback
Although this book was needed in its day (copyright 1978, 1974), many of the examples are so dated that they've lost their relevance. Steve Maguire's more recent "Writing Solid Code" covers the very same material, but uses examples written in C rather than Fortran and PL/C. I recommend it instead.
3 of 4 people found the following review helpful
Format:Paperback
This was the definitive work on programming style when first written, and is still a standard reference. However, it desperately needs updating, mainly in the examples, which are based on PL1 and a now-obsolescent version of Fortran.
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
16 reviews
25 of 26 people found the following review helpful
All programmers should buy this book
13 Oct 2001
Format:Paperback
I firmly believe that computer programming is a craft, perhaps an art but certainly not a science. As you learn the craft you need to learn the wisdom of those that have gone before you. This book becomes essential.
It spells out, first with a counter example found in a piece of code published elsewhere and then with the code rewritten, over 70 pearls of wisdom that should be engraved into our consciousness; for many years every morning when I logged on to start work as a commercial Unix programmer one of these rules was randomly chosen as my message of the day, if I didn't understand the short rule I dragged out the book and refreshed my memory.
Brian Kernighan has co-authored three books almost essential to learning our craft, this volume, "Software Tools" and "The Unix Programming Environment". "Elements of Programming Style" spells out the fundamental rules, "Software Tools" shows you how to apply them to a number of simple projects and extends the rules to software design and finally "The Unix Programming Environment" shows you how to use them in an operating system designed to reward you for your effort.
The examples in either PL/I or Fortran expound the simple rules clearly and expertly in a manner typical of Kernighan's writing. That the languages used are old and most of the rules long accepted lore are not a drawback to this volume. Anyone who knows C, Pascal or even Perl should easily understand the code and programmers turn out code just as bad today in any number of languages.
These things make this book highly recommended reading for anyone who wishes to call them self "programmer." A final word of warning, don't lend this book to anyone, you'll never get it back - I've bought four copies so far.
11 of 11 people found the following review helpful
A classic programming book
15 Feb 2001
Format:Paperback
Published in 1978. 168 pages. These 77 rules represent the definitive basis of good programming style and best programming practices. Included in this famous set of rules are gems such as "say what you mean", "write clearly", "use the telephone test", "make sure comments and code agree", and "make it right before you make it faster". Each rule is described in the context of a small program or code fragment. The authors expertly illuminate their rules by correcting these deficient programs. All of the example code in FORTRAN or PL/I was taken from prior publications. The rules are programming language independent (76/77); the only exception is "avoid the FORTRAN arithmetic IF." This book solidified many of the ideals expressed in the structured programming movement.
5 of 5 people found the following review helpful
Many rules still apply
18 Sep 2006
Format:Paperback
I dare say many rules Mr. Kernighan preached almost three decades ago are still NOT followed by the programming community at large. For examples, "Modularize. Use subroutines." "Each module should do one thing well." and "Don't patch bad code--rewrite it." A widespread, bad practice of 90% of the programmers today is still writing functions that are way too long! And they very often keep modifying existing functions--inserting new logic into them--to make already bad code even worse; they seldom give it a second thought about rewriting the whole damn crap!
Another set of rules from the book: "Make sure code and comments agree." and "Don't over-comment." Many programmers seldom do the first thing, resulting in widespread mismatches between the actual codes and surrounding comments. This applies to Java code as well. The comment style recommended by Java--that is, mixing code and comments that can be extracted into so-called self documentation--is an outright violation of the "don't over-comment" rule. (This is intended to be a criticism of Java-style comments.) Good code should document itself clearly; with perhaps a little help from judiciously added few comments that are not self-evident from the code itself.
The book uses FORTRAN and PL/I code examples. There are things that no longer apply today. But the fundamental rules and styles are still well applicable today and in the future.
Another set of rules from the book: "Make sure code and comments agree." and "Don't over-comment." Many programmers seldom do the first thing, resulting in widespread mismatches between the actual codes and surrounding comments. This applies to Java code as well. The comment style recommended by Java--that is, mixing code and comments that can be extracted into so-called self documentation--is an outright violation of the "don't over-comment" rule. (This is intended to be a criticism of Java-style comments.) Good code should document itself clearly; with perhaps a little help from judiciously added few comments that are not self-evident from the code itself.
The book uses FORTRAN and PL/I code examples. There are things that no longer apply today. But the fundamental rules and styles are still well applicable today and in the future.
Were these reviews helpful?
Let us know
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
