You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My background is in software engineering, and my day-to-day job does not has anything to do with Modelica, FMI or SSP. However, on a project I am working, I have to add compatibility for SSP, so I started reading through the standards. I gave this intro to make it clear that there is a high chance that my points could be completely wrong, but if anyone could make me understand why, that would be much appreciated.
As the title says, why do we need connectors?
As per the standard, Systems, Components and Signal Dictionary References can optionally have "connectors". Connectors represent the interface of the element to the outside world. The connectors MUST match variable/ports of the underlying component implementation. Being so, connectors have only two attributes: name and kind, where both MUST match with the underlying variable/port.
Now, considering that, why do we need to explicitly define connectors, where instead the variable/port of the underlying component could be referenced directly on the Connection.
You can define connectors that are not connected to, that is essential for parameters and for using SSP as an interface specification.
You also disregard that a connector declaration can hold much more information about type, array dimensions, etc.
Activity
DagBruck commentedon Feb 27, 2025
You can define connectors that are not connected to, that is essential for parameters and for using SSP as an interface specification.
You also disregard that a connector declaration can hold much more information about type, array dimensions, etc.