You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While multiple inheritance is supported in the SimpleClassDiagrams formalism, creating an instance that has diamond inheritance gives an error "500:constraint (post-create noInheritanceLoops) failed".
Is this intended behavior?
If so, we must make it explicit that diamond inheritance is not allowed.
Otherwise, the constraint checking function should be fixed to allow this.
The constraint checking function is currently as follows:
My concern is that if diamond inheritance was allowed, that AToMPM would be able to correctly handle the inheritance of attributes. Not even the usual problem of resolving conflicts, but also just making sure that all attributes are properly inherited if there is more than one super-class.
Is this a blocker for you? For now, it would be best to create a third class between those two which inherits from AbstractSegment and has the attributes of the others, set manually.
Perhaps in the future we can relax this check and go through the tests to see if anything else needs updating.
While multiple inheritance is supported in the SimpleClassDiagrams formalism, creating an instance that has diamond inheritance gives an error "500:constraint (post-create noInheritanceLoops) failed".
Is this intended behavior?
The constraint checking function is currently as follows:
The text was updated successfully, but these errors were encountered: