Naming rules for struct/class/bus

I noticed there isn’t yet an explicit guideline for struct names and, in particular, for struct field names. The only related reference I found, “Defining structs”, includes an example where the struct members use UpperCamelCase. Should these be UpperCamelCase? And if so, should the same convention apply to Simulink.Bus elements?

I’m asking because this can create a mismatch with some Model Advisor naming guidelines. For example, suppose I have a Simulink Inport of type Bus, with elements Signal1 and Signal2, which has been created from a MATLAB struct or class. If I use a Bus Selector to extract Signal1 and feed it into a MATLAB Function block, where the corresponding function parameter is named signal1 (lowerCamelCase, following MATLAB function parameter conventions), Model Advisor will trigger a violation because the bus element name (UpperCamelCase) doesn’t match the block input name (lowerCamelCase).

Is there any recommendations on how to harmonize these conventions?

Beginnen Sie mit der Lektüre der vorhandenen Anleitung „Defining structs“ und der im Issue referenzierten Benennungsrichtlinien für Model Advisor. Vergleichen Sie die Konventionen für struct- und class-Felder in MATLAB mit den Elementen von Simulink.Bus und dokumentieren Sie eine konsistente Empfehlung, die die beschriebene Benennungsabweichung zwischen Bus und MATLAB Function behebt.