Closed modelica-trac-importer closed 5 years ago
Modified by choeger on 1 Oct 2012 17:50 UTC
Comment by hansolsson on 4 Dec 2012 14:29 UTC Incorrect milestone; there are no transitions in Modelica 3.2.
Comment by hansolsson on 23 Sep 2013 15:48 UTC Language group: Priorities must be unique.
Comment by hansolsson on 22 Oct 2013 15:06 UTC Updated in r7097
Modified by choeger on 1 Oct 2012 17:50 UTC As far as I can tell, section 17.3.1 does not contain a requirement that all transition priorities need to be distinct. In fact, there is a default value for the priority. Thus, it is logical to assume that multiple transitions might exist which might fire simultaneously.
While I do not see this as a general problem (see #843), Hans argues that this should be forbidden (as it is for when equations now).
Since I prefer (and I hope there is consensus about it), to have only one event detection mechanism in an implementation, we should unify the specification in that regard.
If there already is such a requirement (which I might have overlooked), I still would like to point out that it is not actually needed (since conflicts might be detected at runtime).
Reported by choeger on 1 Oct 2012 17:50 UTC As far as I can tell, section 17.3.1 does not contain a requirement that all transition priorities need to be distinct. In fact, there is a default value for the priority. Thus, it is logical to assume that multiple transitions might exist which might fire simultaneously.
While I do not see this as a general problem (see #841), Hans argues that this should be forbidden (as it is for when equations now).
Since I prefer (and I hope there is consensus about it), to have only one event detection mechanism in an implementation, we should unify the specification in that regard.
If there already is such a requirement (which I might have overlooked), I still would like to point out that it is not actually needed (since conflicts might be detected at runtime).
Migrated-From: https://trac.modelica.org/Modelica/ticket/851