Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
logMessage #vref# behaviour with aliases #732
Section 2.1.5 describes the expansion of
(I think this is also a question with FMI2 - the fmi-sdk seems to pick the first SV it finds with the right vref)
As you say, the importing implementation has no way of knowing which of multiple variable names to choose here, as discussed in #435, esp. my comment #435 (comment). So it will pick an arbitrary name.
It was decided that the ability for FMU exporters to not have to place knowledge of variable names into exported code was deemed more important than removing this complex mechanism with its draw backs. As such I think the rationale for this decision and the consequences should probably be pointed out in non-normative text, A pull request would probably be appreciated.