- Taschenbuch: 168 Seiten
- Verlag: McGraw-Hill Inc.,US; Auflage: 2 (Juni 1978)
- Sprache: Englisch
- ISBN-10: 0070342075
- ISBN-13: 978-0070342071
- Größe und/oder Gewicht: 22,6 x 15 x 0,8 cm
- Durchschnittliche Kundenbewertung: 3.0 von 5 Sternen Alle Rezensionen anzeigen (1 Kundenrezension)
- Amazon Bestseller-Rang: Nr. 453.156 in Englische Bücher (Siehe Top 100 in Englische Bücher)
|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
| |||||||||||||||
Produktinformation |
Mehr über die Autoren
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Tags(Was ist das?)Bei einem Tag handelt es sich um ein Schlagwort, das zum Produkt passt.
Tags erleichtern allen Kunden die Suche und die Sortierung ihrer Lieblingsprodukte. |
Eine digitale Version dieses Buchs im Kindle-Shop verkaufen
Wenn Sie ein Verleger oder Autor sind und die digitalen Rechte an einem Buch haben, können Sie die digitale Version des Buchs in unserem Kindle-Shop verkaufen.
Weitere Informationen
Kundenrezensionen
Die hilfreichsten Kundenrezensionen
1 von 1 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Zwar sind die im Buch gelieferten Beispiele schon etwas älter, doch haben sie nichts von ihrer Aktualität verloren. Auf den knapp 150 Seiten stellen die Autoren ihre Vorstellungen guten Programmierstils anhand vieler Beispiele (in Fortran) ausführlich vor und liefern damit eine solide Grundlage für jeden, der sich für die Verbesserung seines Programmierstiles interessiert.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
16 Rezensionen
25 von 26 Kunden fanden die folgende Rezension hilfreich
All programmers should buy this book
13. Oktober 2001
Format:Taschenbuch
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 von 11 Kunden fanden die folgende Rezension hilfreich
A classic programming book
15. Februar 2001
Format:Taschenbuch
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 von 5 Kunden fanden die folgende Rezension hilfreich
Many rules still apply
18. September 2006
Format:Taschenbuch
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.
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
