hisl_0063: Length of user-defined object names to improve MISRA C:2012 compliance
ID: Title | hisl_0063: Length of user-defined object names to improve MISRA C:2012 compliance | |
---|---|---|
Description | To improve MISRA C:2012 compliance
of generated code, use configuration parameter Maximum
identifier length ( Note The default of Maximum identifier length is
| |
A | For Subsystem blocks with parameter Function name
options set to User specified ,
limit the length of function names to be equal to or less than the value
specified in Maximum identifier length. | |
B | Limit the length of data object names to be equal to or less than the value specified in Maximum identifier length:
| |
C | When using these storage classes, limit the length of signal and parameter names to be equal to or less than the value specified in Maximum identifier length:
Note If specified, this includes the length of the Identifier name. | |
Note | When using a Service Interface configuration, identifiers derived from expansion tokens (e.g., $R, $X, etc.) can exceed the maximum identifier length. | |
Rationale | Length in the generated code can result in a MISRAC:2012 violation. | |
Model Advisor Checks | Check for length of user-defined object names (Simulink Check) | |
References |
| |
Prerequisites | hisl_0060: Configuration parameters that improve MISRA C:2012 compliance | |
Last Changed | R2023b | |
Examples | You can limit the function name to the length equal to or less than the specified value using Code mappings. This can be used to avoid violation of MISRA rules.
|