AutosarC++18_03-A3.1.1¶
It shall be possible to include any header file in multiple translation units without violating the One Definition Rule
Required inputs: IR
Possible Messages
Key |
Text |
Severity |
Disabled |
|---|---|---|---|
external_function_definition_in_header |
External function definition in header file. |
None |
False |
external_static_field_def_in_header |
External definition in header file. |
None |
False |
external_variable_definition_in_header |
External variable definition in header file. |
None |
False |
internal_function_declaration_in_header |
Internal function declaration in header file. |
None |
False |
internal_function_definition_in_header |
Function definition in header file (with internal linkage). |
None |
False |
internal_static_field_def_in_header |
Definition in header file (with internal linkage). |
None |
False |
internal_variable_definition_in_header |
Variable definition in header file (with internal linkage). |
None |
False |
tentative_variable_definition_in_header |
Tentative variable definition in header file. |
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
accept_const_fields¶
accept_const_fields : bool = False
accept_const_variables¶
accept_const_variables : bool = True
find_non_external_function_declaration¶
find_non_external_function_declaration : bool = True
report_tentative_definitions¶
report_tentative_definitions : bool = False