Henrik Tidefelt

Maybe this is a good time to ask ourselves whether it really is a good idea that ModelicaServices is tied to the MSL rather than the MLS? If we could...

> I agree with @HansOlsson, the benefits seem marginal. We should focus our efforts on getting rid of ModelicaServices completely instead. But wouldn't removing cyclic dependencies and making the same...

The `Include`-annotations are essential for detecting mismatches between expected and actual implementation. I really prefer having them, not least in the MSL as a way of demonstrating how external functions...

By just sitting and waiting for language version 3.5 to reach MSL.

This is not for me to judge, but in general I don't believe in a black and white picture of backward compatibility. I am very positive about semantic versioning in...

> The specification does not make it illegal, and you could even explicitly create vectors with different unit elements in Modelica like: `parameter Real a[3](unit={"kg","kg/s","kg.s-2"});` although Dymola currently ignores the...

> I think this is the cleanest Modelica can offer for now. Looks like a splendid place to use `final constant` instead of `final parameter`, doesn't it?

> Right, here's a nicer proposa, inspired from Yes, this is nicer. Still, in principle, these constants should also be `final`, as they shouldn't even be modified in derived classes....

As I see it, it means that the the MSL string handling functions are actually fine as they are as long as the targeted Modelica language version doesn't exceed 3.5,...

> Note that the initial scale of the block is 0.04 to be in alignment with the default height of the BooleanExpression block, which this block is expected to be...