SEI CERT C Coding Standard

Space shortcuts

Page tree

Warning

This section is under construction.

Content by label

There is no content with the specified labels

Information for Editors
To have a new guideline automatically listed above be sure to label it api and rule.

Risk Assessment Summary

Rule

Severity

Likelihood

Remediation Cost

Priority

Level

 

3 Comments

  1. Martin Sebor

    The guidelines API05-C. Support compile-time checking and API06-C. Make failures obvious don't exist. Should they be deleted?

    1. Robert Seacord

      or further developed. This section was an attempt to codify some rules at interface design in C that didn't really get the attention it deserved before we became distracted by other things.

      1. Martin Sebor

        I'd be happy to contribute but I'm afraid I'm not sure I know how one would go about supporting compile time checking in C other than by following DCL03-C. Use a static assertion to test the value of a constant expression, and while making failures obvious (as opposed to hard to detect?) sounds like a good design principle I struggle coming up with a simple code example demonstrating how.