The CERT® C Secure Coding Standard > Declarations and Initialization (DCL) > References - Pg. : Safari Books Online

Table of Contents

Download Safari Books Online apps: Apple iOS | Android

Entire Site

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

This Book

The CERT® C Secure Coding Standard

The CERT® C Secure Coding Standard

Search

Contents

The SEI Series in Software Engineering

Acknowledgments

About the Author

Ch. 1. Using This Standard

Ch. 2. Preprocessor (PRE)

Ch. 3. Declarations and Initialization (DCL)

DCL00-C. const-qualify immutable objects

DCL01-C. Do not reuse variable names in subscopes

DCL02-C. Use visually distinct identifiers

DCL03-C. Use a static assertion to test the value of a constant expression

DCL04-C. Do not declare more than one variable per declaration

DCL05-C. Use type definitions to improve code readability

DCL06-C. Use meaningful symbolic constants to represent literal values in program logic

DCL07-C. Include the appropriate type information in function declarators

DCL08-C. Properly encode relationships in constant definitions

DCL09-C. Declare functions that return an errno error code with a return type of errno_t

DCL10-C. Maintain the contract between the writer and caller of variadic functions

DCL11-C. Understand the type issues associated with variadic functions

DCL12-C. Implement abstract data types using opaque types

DCL13-C. Declare function parameters that are pointers to values not changed by the function as const

DCL14-C. Do not make assumptions about the order of global variable initialization across translation units

DCL15-C. Declare objects that do not need external linkage with the storage-class specifier static

DCL30-C. Declare objects with appropriate storage durations

DCL31-C. Declare identifiers before using them

DCL32-C. Guarantee that mutually visible identifiers are unique

DCL33-C. Ensure that restrict-qualified source and destination pointers in function arguments do not reference overlapping objects

DCL34-C. Use volatile for data that cannot be cached

DCL35-C. Do not convert a function using a type that does not match the function definition

DCL36-C. Do not declare an identifier with conflicting linkage classifications

Noncompliant Code Example

Compliant Solution

Risk Assessment

Ch. 4. Expressions (EXP)

Ch. 5. Integers (INT)

Ch. 6. Floating Point (FLP)

Ch. 7. Arrays (ARR)

Ch. 8. Characters and Strings (STR)

Ch. 9. Memory Management (MEM)

Ch. 10. Input/Output (FIO)

Ch. 11. Environment (ENV)

Ch. 12. Signals (SIG)

Ch. 13. Error Handling (ERR)

Ch. 14. Miscellaneous (MSC)

URL

Help

References

[Banahan 03] Section 8.2, “Declarations, Definitions and Accessibility”
[ISO/IEC 9899:1999] Section 6.2.2, “Linkages of Identifiers”
[Kirch-Prinz 02]
[MISRA 04] Rule 8.1