Page 1
Embedded C Coding StandardEmbedded C Coding Standard by Michael Barr Keeps Bugs Out ® Edition: BARR-C: 2018 | barrgroup.com
The BARR-C:2018 edition of Michael Barr’s Embedded C Coding Standard, published by Barr Group, defines practical coding rules intended to reduce defects and improve the readability, maintainability, and portability of embedded software. Based on C99, it covers general language usage, comments, white space, modules, data types, procedures, variables, and statements, with examples, reasoning, and enforcement guidance. It also discusses compatibility with MISRA C:2012, deviations, and customization. Appendices provide accepted abbreviations, header and source file templates, and a CRC example program. The document is not a safety standard and does not guarantee defect-free software.
The first 5 pages, shown as text so search engines and readers can find this document.
Embedded C Coding StandardEmbedded C Coding Standard by Michael Barr Keeps Bugs Out ® Edition: BARR-C: 2018 | barrgroup.com
BARR-C:2018 Embedded C Coding Standard
Embedded C Coding Standard ii
Embedded C Coding Standard iii Embedded C Coding Standard by Michael Barr Edition: BARR-C:2018 | barrgroup.com
Embedded C Coding Standard iv Embedded C Coding Standard by Michael Barr Copyright © 2018 Integrated Embedded, LLC (dba Barr Group). All rights reserved. Published by: Barr Group 20251 Century Blvd, Suite 330 Germantown, MD 20874 This book may be purchased in print and electronic editions. A free online edition is also available. For more information see https://barrgroup.com/coding-standard. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. Compliance with the coding standard rules in this book neither ensures against software defects nor legal liability. Product safety and security are your responsibility. Barr Group, the Barr Group logo, The Embedded Systems Experts, and BARR-C are trademarks or registered trademarks of Integrated Embedded, LLC. Any other trademarks used in this book are property of their respective owners. ISBN-13: 978-1-72112-798-6 ISBN-10: 1-72112-798-4
Doxxly editorial guide
This guide helps you understand the scope of Embedded C Coding Standard before or alongside reading the original document. It is based on the catalogue record, credited creator, source, classification and topics shown on this page. It does not replace the original work and does not invent claims about passages that Doxxly cannot verify.
Embedded C Coding Standard is a 87-page documentcredited to Mira W. Thackery. The BARR-C:2018 edition of Michael Barr’s Embedded C Coding Standard, published by Barr Group, defines practical coding rules intended to reduce defects and improve the readability, maintainability, and portability of embedded software. Based on C99, it covers general language usage, comments, white space, modules, data types, procedures, variables, and statements, with examples, reasoning, and enforcement guidance. It also discusses compatibility with MISRA C:2012, deviations, and customization. Appendices provide accepted abbreviations, header and source file templates, and a CRC example program. The document is not a safety standard and does not guarantee defect-free software. It appears in the Technology & Security collection, which groups it with other material that readers may use for comparison and further study.
The item can be approached in several ways. A reader looking for a quick orientation can begin with the free five-page preview, inspect the page structure and use the metadata to judge relevance. Someone undertaking deeper research can work through the complete file, search its indexed text, record useful page references and compare its treatment of Embedded C, BARR-C:2018, Coding Standards, Firmware Development, C99, Software Reliability, Code Reviews, Static Analysis, MISRA C with the related resources linked below.
Rather than reducing the work to a single claim, this page treats it as a source that should be read in context. The title, creator, publication source, licence and format all help explain what kind of evidence it may offer. Readers should distinguish the original author's statements from Doxxly's catalogue description, and should cite the original edition when using the material in academic, professional or published work.
The catalogue connects this document with Embedded C, BARR-C:2018, Coding Standards, Firmware Development, C99, Software Reliability, Code Reviews, Static Analysis, MISRA C. These terms offer practical entry points rather than a substitute for close reading. Start by identifying the definitions, examples, arguments, tables or visual explanations attached to each topic. Then note where the creator draws connections, makes distinctions or moves from background material to a conclusion, recommendation, calculation or narrative development.
A useful reading method is to separate description from interpretation. First record what the item actually presents: names, headings, figures, formulas, quotations or stated propositions. Next consider why those details matter within the whole work. Finally compare them with another source from the same subject area. This process helps turn a long digital file into evidence that can be evaluated rather than merely skimmed.
The following is an editorial content guide based on the verified catalogue topics. It is not represented as the original author's formal table of contents. Use it to organise notes while moving through the 87 pages in the player.
Use this section of the reading guide to identify how Embedded C appears in Embedded C Coding Standard, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how BARR-C:2018 appears in Embedded C Coding Standard, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how Coding Standards appears in Embedded C Coding Standard, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how Firmware Development appears in Embedded C Coding Standard, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how C99 appears in Embedded C Coding Standard, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how Software Reliability appears in Embedded C Coding Standard, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how Code Reviews appears in Embedded C Coding Standard, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how Static Analysis appears in Embedded C Coding Standard, note important terms, and connect the subject to the wider purpose of the work.
When a heading in the original differs from this guide, follow the original heading in your citation. Page numbers can also vary between editions. Doxxly's direct page field is useful for navigation, but formal references should include the title, creator, source and edition details available in the file itself.
Doxxly credits Mira W. Thackery as the author or creator of Embedded C Coding Standard. This page does not add an unverified biography, job title or institutional affiliation. The attribution is preserved so readers can distinguish the creator from the hosting library and follow the original record when an external author link is available.
Author context matters because a work reflects a particular purpose, audience and point of view. Before relying on the material, consider what the creator set out to explain, when the source was produced and whether later research or revised guidance should also be consulted. For literature and philosophy, compare translations and editions; for technical material, check whether a newer version has superseded the one shown here.
The recorded source for this item is barrgroup.com. Doxxly provides access and discovery tools but does not claim to be the original publisher unless explicitly stated. Source links, creator attribution and the recorded Publicly available file collected for editorial review licence are displayed to help readers assess provenance and permitted use.
Provenance is especially important for reports, standards, presentations and working spreadsheets. Check the original source for amendments, supporting files and current policy. A trustworthy research workflow keeps the source URL with any notes or downloaded copy, verifies important figures against the original, and avoids treating an archived document as automatically current.
Visit barrgroup.comBegin with the title and opening pages, then use the guide above to decide whether to read sequentially or move to a particular topic. The Doxxly player provides previous and next navigation, a direct page field, zoom steps, fit-to-width and fit-to-page modes, rotation and fullscreen. These controls are useful when a page contains small type, a wide table, an image, a scanned layout or a dense sequence of notes.
The first five pages are open to every visitor. A plan unlocks the complete item and full-document search. Search is best used for distinctive names, technical terms or short phrases; broad words can produce too many possible contexts. When you find a useful passage, read the surrounding pages so that a sentence, chart or formula is not separated from its explanation.
If downloading is enabled, members can obtain the original PDF file. Keep the original format when formulas, slide sequencing, pagination or layout carries meaning. Respect the Publicly available file collected for editorial review terms displayed on this page, and use the rights-report link if you believe the attribution or availability needs review.
As you read Embedded C Coding Standard, ask which audience the creator addresses, what problem or idea organises the work, what evidence is presented, and which assumptions remain unstated. Note whether important terms are defined consistently and whether examples represent a broader pattern or a narrow case. For quantitative material, record units, time periods, formulas and data sources. For interpretive material, separate the creator's language from your own summary.
A second set of questions concerns relevance today. Which parts remain durable, which depend on their historical or institutional setting, and what would need confirmation from a newer source? Following the tags and the Technology & Security collection can reveal useful comparisons. Agreement between sources can strengthen confidence, while disagreement can point to changing definitions, methods, evidence or priorities.
Finally, decide what you need from the item: background knowledge, a quotation, a worked example, a model, a visual explanation or a starting bibliography. That purpose should guide the depth of reading and the notes you keep. Doxxly helps locate and navigate the source; careful interpretation remains the reader's responsibility.
Practical answers about reading, downloading and understanding this document on Doxxly.

National Institute of Standards and Technology

National Institute of Standards and Technology

National Institute of Standards and Technology

National Institute of Standards and Technology

National Institute of Standards and Technology

National Institute of Standards and Technology