Customize generated function argument names for reusable subsystems.
Category: Code Generation > Identifiers
Enter a macro that specifies whether, and in what order, certain text is to be included in the generated argument name. The macro can include a combination of the following format tokens.
| Token | Description |
|---|---|
$I |
Optional. |
$M
| Insert name-mangling text if required to avoid naming collisions. Required. |
$N | Insert name of object (block, signal or signal object, state, parameter or parameter object) for which identifier is being generated. Recommended to maximize readability of generated code. |
$U | Insert text that you specify for the |
Avoid name collisions in general. One way is to avoid using default block names (for
example, Gain1, Gain2...) when your model has many
blocks of the same type.
Where possible, increase the Maximum identifier length to accommodate the length of the identifiers you expect to generate. Reserve at least three characters for name-mangling text.
To control the case (upper or lower case) of the text that each token represents,
include decorators such as [U_] in your macro. See Control Case with Token Decorators.
This parameter:
Appears only for ERT-based targets.
Requires Embedded Coder® when generating code.
Parameter:
CustomSymbolStrFcnArg |
| Type: character vector |
| Value: valid combination of tokens |
Default:
rt$I$N$M |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | Use default |
| Efficiency | No impact |
| Safety precaution | No recommendation |