SEI CERT C Coding Standard

Space shortcuts

Page tree

Title: PC-lint Plus_V  
Author: Alex Bock Feb 23, 2021
Last Changed by: Alex Bock Feb 23, 2021
Tiny Link: (useful for email) https://wiki.sei.cmu.edu/confluence/x/BYAvE
Export As: Word · PDF  
Incoming Links
SEI CERT C Coding Standard (152)
    Page: API09-C. Compatible values should have the same type
    Page: ARR32-C. Ensure size arguments for variable length arrays are in a valid range
    Page: ARR01-C. Do not apply the sizeof operator to a pointer when taking the size of an array
    Page: FIO38-C. Do not copy a FILE object
    Page: MSC06-C. Beware of compiler optimizations
    Page: MSC20-C. Do not use a switch statement to transfer control into a complex block
    Page: FLP03-C. Detect and handle floating-point errors
    Page: POS44-C. Do not use signals to terminate threads
    Page: PRE11-C. Do not conclude macro definitions with a semicolon
    Page: DCL01-C. Do not reuse variable names in subscopes
    Page: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction
    Page: EXP42-C. Do not compare padding data
    Page: FLP30-C. Do not use floating-point variables as loop counters
    Page: EXP30-C. Do not depend on the order of evaluation for side effects
    Page: FIO39-C. Do not alternately input and output from a stream without an intervening flush or positioning call
    Page: SIG35-C. Do not return from a computational exception signal handler
    Page: CON43-C. Do not allow data races in multithreaded code
    Page: MSC21-C. Use robust loop termination conditions
    Page: PC-lint Plus
    Page: ARR37-C. Do not add or subtract an integer to a pointer to a non-array object
    Page: MSC37-C. Ensure that control never reaches the end of a non-void function
    Page: STR07-C. Use the bounds-checking interfaces for string manipulation
    Page: MEM35-C. Allocate sufficient memory for an object
    Page: INT16-C. Do not make assumptions about representation of signed integers
    Page: ERR33-C. Detect and handle standard library errors
    Page: ARR38-C. Guarantee that library functions do not form invalid pointers
    Page: MEM11-C. Do not assume infinite heap space
    Page: DCL02-C. Use visually distinct identifiers
    Page: ERR07-C. Prefer functions that support error checking over equivalent functions that don't
    Page: STR11-C. Do not specify the bound of a character array initialized with a string literal
    Page: FLP37-C. Do not use object representations to compare floating-point values
    Page: INT09-C. Ensure enumeration constants map to unique values
    Page: FLP02-C. Avoid using floating-point numbers when precise computation is needed
    Page: INT07-C. Use only explicitly signed or unsigned char type for numeric values
    Page: PRE06-C. Enclose header files in an include guard
    Page: EXP08-C. Ensure pointer arithmetic is used correctly
    Page: ENV33-C. Do not call system()
    Page: EXP47-C. Do not call va_arg with an argument of the incorrect type
    Page: MEM05-C. Avoid large stack allocations
    Page: DCL11-C. Understand the type issues associated with variadic functions
    Page: MEM31-C. Free dynamically allocated memory when no longer needed
    Page: SIG01-C. Understand implementation-specific details regarding signal handler persistence
    Page: DCL16-C. Use "L," not "l," to indicate a long value
    Page: MSC01-C. Strive for logical completeness
    Page: MSC19-C. For functions that return an array, prefer returning an empty array over a null value
    Page: INT05-C. Do not use input functions to convert character data if they cannot handle all possible inputs
    Page: ERR34-C. Detect errors when converting a string to a number
    Page: MEM34-C. Only free memory allocated dynamically
    Page: EXP33-C. Do not read uninitialized memory
    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: PRE00-C. Prefer inline or static functions to function-like macros
    Page: SIG30-C. Call only asynchronous-safe functions within signal handlers
    Page: EXP12-C. Do not ignore values returned by functions
    Page: EXP16-C. Do not compare function pointers to constant values
    Page: POS34-C. Do not call putenv() with a pointer to an automatic variable as the argument
    Page: ENV01-C. Do not make assumptions about the size of an environment variable
    Page: FIO11-C. Take care when specifying the mode parameter of fopen()
    Page: FLP00-C. Understand the limitations of floating-point numbers
    Page: DCL36-C. Do not declare an identifier with conflicting linkage classifications
    Page: CON33-C. Avoid race conditions when using library functions
    Page: WIN00-C. Be specific when dynamically loading libraries
    Page: WIN02-C. Restrict privileges when spawning child processes
    Page: DCL38-C. Use the correct syntax when declaring a flexible array member
    Page: FIO13-C. Never push back anything other than one read character
    Page: MSC24-C. Do not use deprecated or obsolescent functions
    Page: MSC13-C. Detect and remove unused values
    Page: PRE05-C. Understand macro replacement when concatenating tokens or performing stringification
    Page: STR10-C. Do not concatenate different type of string literals
    Page: PRE01-C. Use parentheses within macros around parameter names
    Page: STR05-C. Use pointers to const when referring to string literals
    Page: FIO30-C. Exclude user input from format strings
    Page: PRE07-C. Avoid using repeated question marks
    Page: STR09-C. Don't assume numeric values for expressions with type plain character
    Page: STR38-C. Do not confuse narrow and wide character strings and functions
    Page: POS54-C. Detect and handle POSIX library errors
    Page: MSC17-C. Finish every set of statements associated with a case label with a break statement
    Page: DCL23-C. Guarantee that mutually visible identifiers are unique
    Page: EXP05-C. Do not cast away a const qualification
    Page: ARR30-C. Do not form or use out-of-bounds pointers or array subscripts
    Page: POS47-C. Do not use threads that can be canceled asynchronously
    Page: INT02-C. Understand integer conversion rules
    Page: ARR02-C. Explicitly specify array bounds, even if implicitly defined by an initializer
    Page: DCL19-C. Minimize the scope of variables and functions
    Page: INT12-C. Do not make assumptions about the type of a plain int bit-field when used in an expression
    Page: STR34-C. Cast characters to unsigned char before converting to larger integer sizes
    Page: PRE31-C. Avoid side effects in arguments to unsafe macros
    Page: MEM02-C. Immediately cast the result of a memory allocation function call into a pointer to the allocated type
    Page: MSC33-C. Do not pass invalid data to the asctime() function
    Page: MSC30-C. Do not use the rand() function for generating pseudorandom numbers
    Page: FIO47-C. Use valid format strings
    Page: MEM30-C. Do not access freed memory
    Page: CON37-C. Do not call signal() in a multithreaded program
    Page: DCL04-C. Do not declare more than one variable per declaration
    Page: EXP34-C. Do not dereference null pointers
    Page: FIO46-C. Do not access a closed file
    Page: DCL15-C. Declare file-scope objects or functions that do not need external linkage as static
    Page: INT00-C. Understand the data model used by your implementation(s)
    Page: DCL00-C. Const-qualify immutable objects
    Page: EXP20-C. Perform explicit tests to determine success, true and false, and equality
    Page: DCL10-C. Maintain the contract between the writer and caller of variadic functions
    Page: EXP46-C. Do not use a bitwise operator with a Boolean-like operand
    Page: EXP00-C. Use parentheses for precedence of operation
    Page: DCL31-C. Declare identifiers before using them
    Page: DCL30-C. Declare objects with appropriate storage durations
    Page: MEM12-C. Consider using a goto chain when leaving a function on error when using and releasing resources
    Page: MSC41-C. Never hard code sensitive information
    Page: DCL41-C. Do not declare variables inside a switch statement before the first case label
    Page: EXP19-C. Use braces for the body of an if, for, or while statement
    Page: API00-C. Functions should validate their parameters
    Page: MSC12-C. Detect and remove code that has no effect or is never executed
    Page: ARR00-C. Understand how arrays work
    Page: EXP10-C. Do not depend on the order of evaluation of subexpressions or the order in which side effects take place
    Page: POS49-C. When data must be accessed by multiple threads, provide a mutex and guarantee no adjacent data is also accessed
    Page: ERR04-C. Choose an appropriate termination strategy
    Page: EXP02-C. Be aware of the short-circuit behavior of the logical AND and OR operators
    Page: INT13-C. Use bitwise operators only on unsigned operands
    Page: EXP44-C. Do not rely on side effects in operands to sizeof, _Alignof, or _Generic
    Page: PRE02-C. Macro replacement lists should be parenthesized
    Page: DCL13-C. Declare function parameters that are pointers to values not changed by the function as const
    Page: ERR06-C. Understand the termination behavior of assert() and abort()
    Page: STR30-C. Do not attempt to modify string literals
    Page: WIN01-C. Do not forcibly terminate execution
    Page: FIO42-C. Close files when they are no longer needed
    Page: MSC04-C. Use comments consistently and in a readable fashion
    Page: PRE10-C. Wrap multistatement macros in a do-while loop
    Page: DCL40-C. Do not create incompatible declarations of the same function or object
    Page: FLP36-C. Preserve precision when converting integral values to floating-point type
    Page: CON35-C. Avoid deadlock by locking in a predefined order
    Page: MSC18-C. Be careful while handling sensitive data, such as passwords, in program code
    Page: EXP15-C. Do not place a semicolon on the same line as an if, for, or while statement
    Page: EXP36-C. Do not cast pointers into more strictly aligned pointer types
    Page: MEM00-C. Allocate and free memory in the same module, at the same level of abstraction
    Page: SIG00-C. Mask signals handled by noninterruptible signal handlers
    Page: DCL37-C. Do not declare or define a reserved identifier
    Page: SIG31-C. Do not access shared objects in signal handlers
    Page: SIG34-C. Do not call signal() from within interruptible signal handlers
    Page: EXP45-C. Do not perform assignments in selection statements
    Page: CON32-C. Prevent data races when accessing bit-fields from multiple threads
    Page: SIG02-C. Avoid using signals to implement normal functionality
    Page: DCL20-C. Explicitly specify void when a function accepts no arguments
    Page: DCL18-C. Do not begin integer constants with 0 when specifying a decimal value
    Page: PRE32-C. Do not use preprocessor directives in invocations of function-like macros
    Page: INT08-C. Verify that all integer values are in range
    Page: STR31-C. Guarantee that storage for strings has sufficient space for character data and the null terminator
    Page: INT36-C. Converting a pointer to integer or integer to pointer
    Page: EXP43-C. Avoid undefined behavior when using restrict-qualified pointers
    Page: MSC32-C. Properly seed pseudorandom number generators
    Page: POS04-C. Avoid using PTHREAD_MUTEX_NORMAL type mutex locks
    Page: DCL07-C. Include the appropriate type information in function declarators
    Page: FLP06-C. Convert integers to floating point for floating-point operations
    Page: EXP13-C. Treat relational and equality operators as if they were nonassociative
Hierarchy
Parent Page
    Page: EE. Analyzers
Labels
There are no labels assigned to this page.
Recent Changes
Time Editor  
Feb 23, 2021 10:22 Alex Bock