Join GitHub today
wrong code generation for guards because of misinterpreting method calls #870
Consider the following code:
The generated code for event
Check this code out
referenced this issue
Sep 24, 2016
After fixing issue #819, it produces the following code:
So, it now uses the method getData() as stated in the umple code. However, this method isn't defined and it doesn't actually exist. Is this how it should be?
Yes, it's been fixed. It would be good to show a warning regarding this case. I mean, if there is a method called in the guard and there is not implementation for it inside its superclasses, interfaces, traits, and other events related to state machines then a warning must be raised. It can be considered as an error as well.