Home > Articles > Programming > Windows Programming

Creating a Set of Guidelines

Coding guidelines should not be written in isolation (that is, by considering only their individual technical merits). The factors involved in how a set of guidelines might be used in various software development environments also need to be considered. For example, these factors might include the following:

  • How adherence to each recommendation might be checked
  • Management acceptance of the recommendations made; for example, the cost of enforcement shouldn’t be excessive
  • How a set of guidelines fit together as a package; for instance, the set shouldn’t be so restrictive that it’s impossible to write any software without violating one of the guidelines

There are an infinite number of possible coding guidelines. To guarantee that all possible program faults are covered, an infinite set of guidelines would be required. In practice, however, most coding guideline documents contain around 100 recommendations. In some sense, the recommendations that survive to become part of a coding guideline document might be considered to be the most important recommendations, with importance possibly being measured in one of several ways:

  • Maximizing the number of faults prevented
  • Having the most support from the authors of the document (which isn’t always based on any evidence that the guideline will prevent a significant number of faults occurring)
  • Marketing potential (by meeting user expectations in terms of what developers believe should be included in such a document)

While the underlying reasons for the mistakes made by developers—such as the use of uninitialized variables—might apply to all computer languages, most coding guideline documents are written to deal with specific languages.

Traditionally, the main source of guideline recommendations has been practical experience; that is, those language constructs that keep appearing as the root causes of faults (sometimes known as common mode failures). While past experience of faults is still a major source of guideline recommendations, the underlying reasons for why developers make the mistakes that lead to these faults are slowly being discovered. In one form or another, these mistakes are all the result of human fallibility.

While cognitive psychology (the study of mental processes) is still in its infancy, the models researchers have created of the various components used during reading and comprehension—for example, visual processing of text, short-term memory, and so on—do provide some insight into the processes involved in reading and writing code.

Two cognitive-based root causes of mistakes are developer knowledge failures (for example, where developers don’t realize they have insufficient knowledge) and developer performance failures (such as calculating an incorrect answer to a problem). An example of a physical root cause of mistakes is mistyping. This can become a fault if it goes undetected, as when the mistyped characters didn’t prevent the source being successfully compiled.

Possible solutions to knowledge-based mistakes include reducing the amount of information that developers need to know, or organizing the information contained in source code in such a way that there are fewer demands on developers to correctly recall or recognize information. This information might relate to the details of programming language semantics, the behavior of compilers, or knowledge about the source code used to implement an application.

Some coding guidelines recommend against the use of constructs that are obvious faults (for example, "Don’t read the value of an uninitialized variable"). To understand the reason for this kind of guideline, it’s necessary to understand the approach that many managers take toward checking for faults in their developers’ code: If it isn’t in the guidelines document, there’s no need to check for it. While high-quality static analysis tools can perform many more checks than are required by the various coding guideline documents, this minimalist checking mentality—in other words, lowest cost to that manager—means that developers may only be allocated the time needed to run analysis tools with certain specific guideline checks enabled. Yes, it’s obvious to all developers that some guidelines are simply recommending against obvious faults. Including them in the document means that managers are more likely to allocate resources for developers to check for and correct any violations.

The approach taken by the authors of MISRA-C was to base most of their guidelines on constructs whose behavior, in one form or another, was not uniquely specified by the language standard—a different compiler, or even the same compiler in different contexts, could generate machine code that behaved differently for the same language construct—on the basis that developers might write code that depends on a specific behavior. Other MISRA-C guidelines were based on avoiding known bugs in compilers and constructs that experience had shown to be a common cause of developer error.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020