[Uml-devel] [Bug 95252] Deleting a class that contains another class leaves the model inconsistent

[Marcos Mayorga]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
        
http://bugs.kde.org/show_bug.cgi?id=95252        




------- Additional Comments From the drmay net  2004-12-20 21:51 -------
Yes, but when speaking about classes I rather see the deletion in cascade could result in the loose of useful work, because when a class 'belongs' to another, it means it in terms of scope or visibility, and not in terms of functionality.
example:
class line {
 class point{};
};

If I decide not to use lines but it is better to use polylines, in the model I don't want point to dissapear, because I'm going to need it in my new polyline class