This repository has been archived by the owner on Jan 5, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 86
C++, C and Java guard expression problem #355
Comments
terfloth
added a commit
that referenced
this issue
Feb 8, 2016
terfloth
added a commit
that referenced
this issue
Feb 8, 2016
terfloth
added a commit
that referenced
this issue
Feb 8, 2016
terfloth
added a commit
that referenced
this issue
Feb 8, 2016
terfloth
added a commit
that referenced
this issue
Feb 8, 2016
terfloth
added a commit
that referenced
this issue
Feb 8, 2016
before combining with trigger expression.
Merged
This issue also applied to C and Java code generators. |
terfloth
changed the title
C++ Guard expression problem
C++, C and Java guard expression problem
Feb 8, 2016
jdicks
pushed a commit
that referenced
this issue
Feb 9, 2016
jdicks
pushed a commit
that referenced
this issue
Feb 9, 2016
jdicks
pushed a commit
that referenced
this issue
Feb 9, 2016
jdicks
pushed a commit
that referenced
this issue
Feb 9, 2016
jdicks
pushed a commit
that referenced
this issue
Feb 9, 2016
jdicks
pushed a commit
that referenced
this issue
Feb 9, 2016
before combining with trigger expression.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From Daniel Buijnik's forum post: https://groups.google.com/forum/embed/?place=forum/yakindu-user#!topic/yakindu-user/1ijllodE5oo
To start with please have a look at the following:
Under simulator that FSM is behaving OK, however when running generated C++ code I discovered that for event E2 the transition taken is A-->B instead A-->C.
Quick look into generated code shows that the problem is with expression E1[c1 || c2].
It is translated to:
while it should be rather
Quick fix for the above problem is to use additional brackets like this: E1[(c1 || c2)], however in longer run it would be great to see a fix for that as it is not unusual to have more than one variable in the guard.
I've been using Yakindu 2.5.0.201512141644.
The text was updated successfully, but these errors were encountered: