AbstractMISRA context for error tracking and rule transformations state
Abstract ReadonlyanalysisSpecifies the scope of analysis: single unit or entire system.
Protected ReadonlyappliesStandards to which this rule applies to
ProtectedcontextProtectedinvalidIdentifiers with invalid names that require renaming.
ReadonlypriorityA positive integer starting from 1 that indicates the rule's priority, determining the order in which rules are applied.
List of dependent visits, which is empty by default
AbstractnameRule identifier according to MISRA-C:2012
An alias for 'name'
ProtectedappliesVerifies if the rule applies to the standard being used
Renames all invalid identifiers found in the program. After renaming, the program is rebuilt to ensure proper linking of functions, variables, and their external declarations.
Joinpoint to transform
Report detailing the transformation result
Initial value stored in the shared context
ProtectedlogLogs a MISRA-C rule violation error
The joinpoint where the violation occurred
Description of the violation
AbstractmatchChecks if the joinpoint violates the rule
Joinpoint to analyze
[logErrors=false] - Whether to log errors if a violation is detected
Returns true if the joinpoint violates the rule, false otherwise
ProtectedrebuildRebuilds the program based on the current AST, clears stored data in the shared context, and resets all caches
Abstract base class for MISRA-C rules that enforce constraints on identifier uniqueness where renaming may be required.
Need to implement: