ModelicaSpecification
ModelicaSpecification copied to clipboard
modelica
Specification of the Modelica Language
Just trying to get MCP/0032 specification ready. Whether this should replace MCP/0032 or be merged directly is a latter issue. First is this ok-ish @christoff-buerger ?
This is a follow-up to a discussion about character set restrictions applying to string content where it was noted that we say that `Q-IDENT` may contain any printable ASCII character,...
In [Section 16.4](https://specification.modelica.org/master/synchronous-language-elements.html#clocked-state-variables) I read the following statements: > A variable to which previous has been applied is called a clocked state variable. > >Operator 16.6 previous > > previous(u)...
(Throughout this comment, if not mentioned differently, references relate to Modelica Specification 3.5.) **Three topics are addressed in the subsequent:** 1. **Distinction of clocked variability from discrete-time variability** 2. **Clock...
For algorithm sections the Modelica Specification requires in general all variables, which are assigned somewhere in the algorithm section, to be initialized always when the algorithm is called (Modelica specification...
Understanding the design of `spatialDistribution` isn't easy, see https://specification.modelica.org/master/operators-and-expressions.html#spatialdistribution. Here, I'm bringing up one small detail and one question. **Small detail:** In the following, the `v` is not the name...
Modelica library developers are converting their libraries to MSL 4.0.0, after almost 10 years of backwards-compatible MSL, when nobody bothered. This raises one fundamental question: what does _backwards compatible_ actually...
What started with the intention of just fixing a minor formatting issue related to `missingInngerMessage` ended up as a wider sweep of modernizing the presentation of annotations using tables. With...
**Modified by dietmarw on 2 Dec 2015 10:08 UTC** We identified several potential “levels” of semantics. The first level was the idea that all libraries must use semantic versions syntax....
I have a customer who defined two hierarchical connectors: ``` connector Hier_control Modelica.Blocks.Interfaces.RealOutput y; Modelica.Blocks.Interfaces.BooleanInput setOff_component; Modelica.Blocks.Interfaces.BooleanOutput setOff_control; end Hier_control; connector Hier_component Modelica.Blocks.Interfaces.RealInput y; Modelica.Blocks.Interfaces.BooleanInput setOff_control; Modelica.Blocks.Interfaces.BooleanOutput setOff_component; end Hier_component;...
