User's Manual

U3585-J-Z125-8-76 419
Appendix Suffixes for data types
with-wild-
constr
(continued)
The following rules must be observed when specifying a constructor:
– The constructor must include at least one wildcard of the selector.
– If the number of identical wildcards exceeds those in the selector, the
index notation must be used.
– If the string selected by the wildcard <...> or [...] is to be used in the
constructor, the index notation must be selected.
– The index notation must be selected if the string identified by the
wildcard “*” is to be duplicated. For example:
“<n><n>” must be specified instead of “**”.
– The wildcard * can also be an empty string. Note that if multiple asterisks
appear in sequence (even with further wildcards), only the last asterisk
can be a non-empty string, e.g. for “****” or “*//*”.
– Valid names must be produced by the constructor. This must be taken
into account when specifying both the constructor and the selector.
– Depending on the constructor, identical names may be constructed from
different names selected by the selector. For example:
“A/*” selects the names “A1” and “A2”; the constructor “B*” generates
the same new name “B” in both cases.
To prevent this from occurring, all wildcards of the selector should be
used at least once in the constructor.
– If the selector ends with a period, the constructor must also end with a
period (and vice versa).
Suffix Meaning
Table 11: Data type suffixes (part 5 of 7)