AutosarC++18_10-A0.1.1

A project shall not contain instances of non-volatile variables being given values that are not subsequently used

Required inputs: IR, StaticSemanticAnalysis

This check detects assignments to variables which are not used (for example, due to def-def data-flow anomalies).

Possible Messages

Key	Text	Severity	Disabled
conditional_unused_def	Result of assignment is not used along some path(s)	None	False
init_used_in_other_isr	Initialization is not used except within code reached from an entry point that might be triggered by an interrupt	None	False
unused_catch_parameter	Unused implicit initialization of catch clause parameter (you can use an unnamed one instead)	None	False
unused_def	Result of assignment is not used	None	False
unused_init	Unused initialization	None	False
used_in_other_isr	Result of assignment is not used except within code reached from an entry point that might be triggered by an interrupt	None	False

Options

• This rule shares the following common options: exclude_in_macros, exclude_messages_in_system_headers, excludes, extend_exclude_to_macro_invocations, includes, justification_checker, languages, post_processing, provider, report_at, severity

• The following places define options that affect this rule: Stylechecks, Analysis-GlobalOptions

report_dead_initializations

report_dead_initializations : bool = True

Whether initializations may be reported as dead.