ModelDriven / Alf-Reference-Implementation

Open-source implementation of the Action Language for fUML (Alf) specification.
30 stars 2 forks source link

Operation mapping is not generating distinguishable names for methods of overloaded operations #46

Closed seidewitz closed 7 years ago

seidewitz commented 7 years ago

If a class has overloaded operations of the same name, then the methods for those classes are supposed to have "...$method$i" suffixes, with sequential values for "i" (assuming no other name conflicts in the class). However, they are all getting the same "...$method$1" suffix, because the original Alf namespace definition is being searched for conflicting names, instead of the mapped class (which is what actually contains the generated method activities).

seidewitz commented 7 years ago

Methods should also be private, to avoid name conflicts in a superclass with methods of operations that have the same name as but are distinguishable from inherited operations.

seidewitz commented 7 years ago

Resolved in v1.1.0.