Discusses many of the problems of coding style in C. The book aims to enable the readers to create their own standards, rather than imposing what may be arbitrary decisions. This is not a book of standards, but a book about standards.
Product Details
Would you like to update product info or give feedback on images?
|
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
2 of 2 people found the following review helpful:
5.0 out of 5 stars
I use this with MISRA-C.,
By kaizen (Japan) - See all my reviews
This review is from: C Style: Standards and Guidelines : Defining Programming Standards for Professional C Programmers (Paperback)
I use this standards and guidelines with misra-C, C coding standards.
This include followings; Psychological factor general principle commenting naming code layout file layout language usage data usage programming usage implementing standards MISRA-C do not include naming and layout. But there are very important for productivity on team development.
1 of 1 people found the following review helpful:
5.0 out of 5 stars
Best book I've found on the topic.,
By
This review is from: C Style: Standards and Guidelines : Defining Programming Standards for Professional C Programmers (Paperback)
Its coverage of the topic of C style guildlines is better than anything else I've found.
1 of 1 people found the following review helpful:
4.0 out of 5 stars
Coding Standards: The Learning Experience,
This review is from: C Style: Standards and Guidelines : Defining Programming Standards for Professional C Programmers (Paperback)
Here's a readable reference on a subject many people love to avoid: coding standards. Why have them? How to choose? How do they help developers? In-depth chapters on the psychology of how people understand code (when they have to read it in order to change it), and on how to deploy a coding standard successfully.
Of course, the bulk of the book is a detailed explanation of almost any kind of item you could put in a coding standard, with reasons and considerations. While these chapters are really a reference, I can see reading through them over time in order to become a better developer. To those who (rightly) are concerned about creativity, consider Straker's response: "The creative element in programming is more in the design, than in the coding. All but the most stringent standards and the most detailed designs leave plenty of creative scope for the coder. The only creativity that is to be frowned on is that which adds unnecessary complexity to the code." By the way, the author has recently put the entire text of the book online [...], but I'm still ordering print copies because I'd rather re-read under a tree than at a PC. Update: Now I've read the print copy -- there's a big difference reading from a book. Straker is thorough, and it's worth reading every word -- there's a temptation to skim and skip online. When you get tired, put the book down and come back to it later. Well worth it!
Share your thoughts with other customers: Create your own review
|
|
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|