Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

state machine behaves differently in scala and c/c++ #33

Closed
vassik opened this issue Feb 5, 2014 · 2 comments
Closed

state machine behaves differently in scala and c/c++ #33

vassik opened this issue Feb 5, 2014 · 2 comments

Comments

@vassik
Copy link
Contributor

vassik commented Feb 5, 2014

empty transition in c does not trigger shift to another state while it works for scala. The code bellow works for scala, but does not for c and cpp
....
state Started {
transition -> Stopped
}
state Stopped {
}
....

@brice-morin
Copy link
Collaborator

Yes, I think auto-transitions (typically useful after an initialisation state) should be kept in the language. Franck will thus fix the C compiler :-)

@ghost ghost assigned ffleurey Feb 5, 2014
@brice-morin brice-morin added this to the ThingML v1 milestone Feb 6, 2014
@brice-morin
Copy link
Collaborator

@acartero has developed an automatic test suite to assess the consistency of the different compilers. The Scala compiler will shortly be deprecated, replaced by the (plain) Java one. The C compiler has been improved (it now manage auto-transition) and the overall consistency between Java and C is almost perfect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants