Sections

• Page:
  Rule 01. Preprocessor (PRE)
• Page:
  Rule 02. Declarations and Initialization (DCL)
• Page:
  Rule 03. Expressions (EXP)
• Page:
  Rule 04. Integers (INT)
• Page:
  Rule 05. Floating Point (FLP)
• Page:
  Rule 06. Arrays (ARR)
• Page:
  Rule 07. Characters and Strings (STR)
• Page:
  Rule 08. Memory Management (MEM)
• Page:
  Rule 09. Input Output (FIO)
• Page:
  Rule 10. Environment (ENV)
• Page:
  Rule 11. Signals (SIG)
• Page:
  Rule 12. Error Handling (ERR)
• Page:
  Rule 13. Application Programming Interfaces (API)
• Page:
  Rule 14. Concurrency (CON)
• Page:
  Rule 48. Miscellaneous (MSC)
• Page:
  Rule 50. POSIX (POS)
• Page:
  Rule 51. Microsoft Windows (WIN)

Rule Listing

• Page:
  ARR30-C. Do not form or use out-of-bounds pointers or array subscripts
• Page:
  ARR32-C. Ensure size arguments for variable length arrays are in a valid range
• Page:
  ARR36-C. Do not subtract or compare two pointers that do not refer to the same array
• Page:
  ARR37-C. Do not add or subtract an integer to a pointer to a non-array object
• Page:
  ARR38-C. Guarantee that library functions do not form invalid pointers
• Page:
  ARR39-C. Do not add or subtract a scaled integer to a pointer
• Page:
  CON30-C. Clean up thread-specific storage
• Page:
  CON31-C. Do not destroy a mutex while it is locked
• Page:
  CON32-C. Prevent data races when accessing bit-fields from multiple threads
• Page:
  CON33-C. Avoid race conditions when using library functions
• Page:
  CON34-C. Declare objects shared between threads with appropriate storage durations
• Page:
  CON35-C. Avoid deadlock by locking in a predefined order
• Page:
  CON36-C. Wrap functions that can spuriously wake up in a loop
• Page:
  CON37-C. Do not call signal() in a multithreaded program
• Page:
  CON38-C. Preserve thread safety and liveness when using condition variables
• Page:
  CON39-C. Do not join or detach a thread that was previously joined or detached
• Page:
  CON40-C. Do not refer to an atomic variable twice in an expression
• Page:
  CON41-C. Wrap functions that can fail spuriously in a loop
• Page:
  CON43-C. Do not allow data races in multithreaded code
• Page:
  DCL30-C. Declare objects with appropriate storage durations
• Page:
  DCL31-C. Declare identifiers before using them
• Page:
  DCL36-C. Do not declare an identifier with conflicting linkage classifications
• Page:
  DCL37-C. Do not declare or define a reserved identifier
• Page:
  DCL38-C. Use the correct syntax when declaring a flexible array member
• Page:
  DCL39-C. Avoid information leakage when passing a structure across a trust boundary
• Page:
  DCL40-C. Do not create incompatible declarations of the same function or object
• Page:
  DCL41-C. Do not declare variables inside a switch statement before the first case label
• Page:
  ENV30-C. Do not modify the object referenced by the return value of certain functions
• Page:
  ENV31-C. Do not rely on an environment pointer following an operation that may invalidate it
• Page:
  ENV32-C. All exit handlers must return normally
• Page:
  ENV33-C. Do not call system()
• Page:
  ENV34-C. Do not store pointers returned by certain functions
• Page:
  ERR30-C. Take care when reading errno
• Page:
  ERR32-C. Do not rely on indeterminate values of errno
• Page:
  ERR33-C. Detect and handle standard library errors
• Page:
  ERR34-C. Detect errors when converting a string to a number
• Page:
  EXP30-C. Do not depend on the order of evaluation for side effects
• Page:
  EXP32-C. Do not access a volatile object through a nonvolatile reference
• Page:
  EXP33-C. Do not read uninitialized memory
• Page:
  EXP34-C. Do not dereference null pointers
• Page:
  EXP35-C. Do not modify objects with temporary lifetime
• Page:
  EXP36-C. Do not cast pointers into more strictly aligned pointer types
• Page:
  EXP37-C. Call functions with the correct number and type of arguments
• Page:
  EXP39-C. Do not access a variable through a pointer of an incompatible type
• Page:
  EXP40-C. Do not modify constant objects
• Page:
  EXP42-C. Do not compare padding data
• Page:
  EXP43-C. Avoid undefined behavior when using restrict-qualified pointers
• Page:
  EXP44-C. Do not rely on side effects in operands to sizeof, _Alignof, or _Generic
• Page:
  EXP45-C. Do not perform assignments in selection statements
• Page:
  EXP46-C. Do not use a bitwise operator with a Boolean-like operand
• Page:
  EXP47-C. Do not call va_arg with an argument of the incorrect type
• Page:
  FIO30-C. Exclude user input from format strings
• Page:
  FIO32-C. Do not perform operations on devices that are only appropriate for files
• Page:
  FIO34-C. Distinguish between characters read from a file and EOF or WEOF
• Page:
  FIO37-C. Do not assume that fgets() or fgetws() returns a nonempty string when successful
• Page:
  FIO38-C. Do not copy a FILE object
• Page:
  FIO39-C. Do not alternately input and output from a stream without an intervening flush or positioning call
• Page:
  FIO40-C. Reset strings on fgets() or fgetws() failure
• Page:
  FIO41-C. Do not call getc(), putc(), getwc(), or putwc() with a stream argument that has side effects
• Page:
  FIO42-C. Close files when they are no longer needed
• Page:
  FIO44-C. Only use values for fsetpos() that are returned from fgetpos()
• Page:
  FIO45-C. Avoid TOCTOU race conditions while accessing files
• Page:
  FIO46-C. Do not access a closed file
• Page:
  FIO47-C. Use valid format strings
• Page:
  FLP30-C. Do not use floating-point variables as loop counters
• Page:
  FLP32-C. Prevent or detect domain and range errors in math functions
• Page:
  FLP34-C. Ensure that floating-point conversions are within range of the new type
• Page:
  FLP36-C. Preserve precision when converting integral values to floating-point type
• Page:
  FLP37-C. Do not use object representations to compare floating-point values
• Page:
  INT30-C. Ensure that unsigned integer operations do not wrap
• Page:
  INT31-C. Ensure that integer conversions do not result in lost or misinterpreted data
• Page:
  INT32-C. Ensure that operations on signed integers do not result in overflow
• Page:
  INT33-C. Ensure that division and remainder operations do not result in divide-by-zero errors
• Page:
  INT34-C. Do not shift an expression by a negative number of bits or by greater than or equal to the number of bits that exist in the operand
• Page:
  INT35-C. Use correct integer precisions
• Page:
  INT36-C. Converting a pointer to integer or integer to pointer
• Page:
  MEM30-C. Do not access freed memory
• Page:
  MEM31-C. Free dynamically allocated memory when no longer needed
• Page:
  MEM33-C. Allocate and copy structures containing a flexible array member dynamically
• Page:
  MEM34-C. Only free memory allocated dynamically
• Page:
  MEM35-C. Allocate sufficient memory for an object
• Page:
  MEM36-C. Do not modify the alignment of objects by calling realloc()
• Page:
  MSC30-C. Do not use the rand() function for generating pseudorandom numbers
• Page:
  MSC32-C. Properly seed pseudorandom number generators
• Page:
  MSC33-C. Do not pass invalid data to the asctime() function
• Page:
  MSC37-C. Ensure that control never reaches the end of a non-void function
• Page:
  MSC38-C. Do not treat a predefined identifier as an object if it might only be implemented as a macro
• Page:
  MSC39-C. Do not call va_arg() on a va_list that has an indeterminate value
• Page:
  MSC40-C. Do not violate constraints
• Page:
  MSC41-C. Never hard code sensitive information
• Page:
  POS30-C. Use the readlink() function properly
• Page:
  POS34-C. Do not call putenv() with a pointer to an automatic variable as the argument
• Page:
  POS35-C. Avoid race conditions while checking for the existence of a symbolic link
• Page:
  POS36-C. Observe correct revocation order while relinquishing privileges
• Page:
  POS37-C. Ensure that privilege relinquishment is successful
• Page:
  POS38-C. Beware of race conditions when using fork and file descriptors
• Page:
  POS39-C. Use the correct byte ordering when transferring data between systems
• Page:
  POS44-C. Do not use signals to terminate threads
• Page:
  POS47-C. Do not use threads that can be canceled asynchronously
• Page:
  POS48-C. Do not unlock or destroy another POSIX thread's mutex
• Page:
  POS49-C. When data must be accessed by multiple threads, provide a mutex and guarantee no adjacent data is also accessed
• Page:
  POS50-C. Declare objects shared between POSIX threads with appropriate storage durations
• Page:
  POS51-C. Avoid deadlock with POSIX threads by locking in predefined order
• Page:
  POS52-C. Do not perform operations that can block while holding a POSIX lock
• Page:
  POS53-C. Do not use more than one mutex for concurrent waiting operations on a condition variable
• Page:
  POS54-C. Detect and handle POSIX library errors
• Page:
  PRE30-C. Do not create a universal character name through concatenation
• Page:
  PRE31-C. Avoid side effects in arguments to unsafe macros
• Page:
  PRE32-C. Do not use preprocessor directives in invocations of function-like macros
• Page:
  Rules versus Recommendations
• Page:
  SIG30-C. Call only asynchronous-safe functions within signal handlers
• Page:
  SIG31-C. Do not access shared objects in signal handlers
• Page:
  SIG34-C. Do not call signal() from within interruptible signal handlers
• Page:
  SIG35-C. Do not return from a computational exception signal handler
• Page:
  STR30-C. Do not attempt to modify string literals
• Page:
  STR31-C. Guarantee that storage for strings has sufficient space for character data and the null terminator
• Page:
  STR32-C. Do not pass a non-null-terminated character sequence to a library function that expects a string
• Page:
  STR34-C. Cast characters to unsigned char before converting to larger integer sizes
• Page:
  STR37-C. Arguments to character-handling functions must be representable as an unsigned char
• Page:
  STR38-C. Do not confuse narrow and wide character strings and functions
• Page:
  WIN30-C. Properly pair allocation and deallocation functions