Embedded C Coding Standard
| Author | : | |
| Rating | : | 4.74 (664 Votes) |
| Asin | : | 1442164824 |
| Format Type | : | paperback |
| Number of Pages | : | 90 Pages |
| Publish Date | : | 2013-05-01 |
| Language | : | English |
DESCRIPTION:
Michael Barr is the CTO of Barr Group, an embedded systems consulting firm based in Germantown, Maryland. Barr is a former adjunct professor of electrical and computer engineering. Internationally recognized as an expert in the field of embedded software process and architecture, Barr has been admitted as a testifying expert witness in U.S. For three and a half years Barr served as editor-in-chief of Embedded Systems Programming magazine.&nb
A serious waste of money This 89 page minibook, printed in the largest font of any technical book I have read, is instantly unimpressive. I cannot say I learned a single thing from this book.If you can write drivel in a font appropriate for children, and sell it for the same price a "real" technical book sells for, that is a way to make a fast buck.But there will not be any follow-on purchases of other titles from this author after you get a look at this offering.An example of one of his "rules. Waste of money Volodymyr Prykhodko Waste of money. Content is not worth the price. This is not a book just a booklet and it should be priced accordingly. Rob Wehrli said A quality coding standard for Embedded C Programmers. The first thing to note about any standard is that you ain't gonna make everyone happy by publishing a standard that says DO THIS and ONLY THIS, EVERY TIME. By their very nature, programmers of all types have to question everything they come into contact withall of the time. When the law is laid down, few programmers like it. Standards for coding are lax or non-existent because of this basic fact. When standards are lax, code quality suffers. Fact of life. Don't shoot t
Individual rules that have been demonstrated to reduce or eliminate certain types of bugs are highlighted.. Barr Group's Embedded C Coding Standard was developed from the ground up to minimize bugs in firmware, by focusing on practical rules that keep bugs out, while also improving the maintainability and portability of embedded software. The coding standard book details a set of guiding principles as well as specific naming conventions and other rules for the use of data types, functions, preprocessor macros, variables and much more
Whenever it is generally the case that one rule chosen from a set of alternatives has the ability to keep bugs out, that is the rule we recommend. From the Back Cover The primary reason to adopt this coding standard is to reduce the number of bugs present in new embedded software (a.k.a., firmware) and in code later added or modified by maintainers. . Thus this coding standard should be applied as part of the broader embedded software development and quality assurance process. A coding standard benefits a team of developers and larger organiza