Francesco Casella

@AHaumer according to [Modelica.UsersGuide.Conventions.ModelicaCode.Format](https://doc.modelica.org/Modelica%204.0.0/Resources/helpOM/Modelica.UsersGuide.Conventions.ModelicaCode.Format.html), we should have something like ```modelica Boolean useZeroSystem=true "= true if zero current is explicitly computed"; ```

@AHaumer, based on our testing there were apparently no bad consequences of those changes _in the MSL_, except the Spice3 case discussed in #13010, which can be considered as a...

Sections [4.7](https://specification.modelica.org/maint/3.6/class-predefined-types-and-declarations.html#balanced-models) and [9.3.1](https://specification.modelica.org/maint/3.6/connectors-and-connections.html#balancing-restriction-and-size-of-connectors) of the MSL define the condition for balanced models. When a composite models turns out to be unbalanced, it is possible to use those rules recursively...

As I understand, the correct strategy when checking a model is that you first start checking its local balancedness, then recursively check the local balancedness of every sub-model. This helps...

Also, we should probably be stricter in terms of the outcome of balancedness analysis. Consider this simple MWE: ```modelica model M Real x; end M; ``` According to the rules...

Keeping @CJLuiten in the loop

```modelica model MWE Modelica.Units.SI.AngularVelocity omega(displayUnit = "Hz"); equation omega = 2*Modelica.Constants.pi; annotation(uses(Modelica(version="4.0.0"))); end MWE; ```  omega in Hz should be 1, not 6.28.

Original ticket https://trac.openmodelica.org/OpenModelica/ticket/5775

This is not super-urgent, but definitely needs to be fixed. Tables are often used in FMUs, and memory leaks should not happen.

@onofriol, please try with the latest nightly build, maybe it's fixed already.