Customize generated global type identifiers.
Category: Code Generation > Identifiers
Enter a macro that specifies whether, and in what order, certain text is to be included in the generated identifier. The macro can include a combination of the following format tokens.
Insert name-mangling text if required to avoid naming collisions.
Insert name of object (block, signal or signal object, state, parameter or parameter object) for which identifier is being generated.
Insert root model name into identifier, replacing unsupported characters with the underscore (_) character.
Required for model referencing.
Insert text that you specify for the
Insert the name of a storage class that is associated with the data item.
Avoid name collisions in general. One way is to avoid using default block names (for example,
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 by Using Token Decorators.
If you specify
$R, the value you specify for Maximum identifier length must be large enough to accommodate full expansions of the
When a name conflict occurs between an identifier within the scope of a higher-level model and an identifier within the scope of a referenced model, the code generator preserves the identifier from the referenced model. Name mangling is performed on the identifier in the higher-level model.
Name mangling conventions do not apply to type names (that is,
typedefstatements) generated for global data types. The Maximum identifier length setting does not apply to type definitions. If you specify
$R, the code generator includes the model name in the
This option does not impact objects (such as signals and parameters) that have a storage class other than
For referenced models, if the Global types parameter does not contain a
$Rtoken (which represents the name of the reference model), code generation prepends the
$Rtoken to the identifier format.
You can use the Model Advisor to identify models in a model referencing hierarchy for which code generation changes configuration parameter settings.
On the Modeling tab, select Model Advisor.
Select By Task.
Run the Check code generation identifier formats used for model reference check.
Appears only for ERT-based targets.
Requires Embedded Coder® when generating code.
|Type: character vector|
|Value: valid combination of tokens|
|Safety precaution||No recommendation|