Per Östlund
Per Östlund
> I don't know how much that has been used in practice, if used one possibility would be to standarize current tool behavior just to avoid breaking things; and don't...
@eshmoylova: Newer versions of OpenModelica rejects it because `r` isn't an array, and `sum` requires the argument to be an array. But my original MWE was just: ```Modelica record BaseR...
> @HansOlsson, @henrikt-ma, @perost, what do you think? The original issue in ClaRa was fixed, so there is no longer any use case for this. As such I can't see...
> To me this is the obvious solution, and I don't see why this would need the old version. > How could the import be shadowed without also impacting `.Modelica.SIunits.Conversions.NonSIunits.Angle_deg...
> > > To me this is the obvious solution, and I don't see why this would need the old version. > > > How could the import be shadowed...
Looks good to me, besides the small issue with context I mentioned above.
In OpenModelica we define a parameter as structural if it must be evaluated by our frontend at compile time, such as a parameter used to define an array dimension in...
Those functions are still used by the MSL, so we need to support them.
In OpenModelica we just use the default value for `significantDigits` (i.e. 6) if it's not given, and it looks like Dymola does the same. It's also used like that in...
> > By the way, what is the part about restriction to encapsulated classes actually trying to say? It sounds as if this would be legal: > > ``` >...