Bug 90755 - Abstract operation (method) should lead to abstract class
Summary: Abstract operation (method) should lead to abstract class
Status: RESOLVED FIXED
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-04 16:19 UTC by Christian Tardif
Modified: 2004-10-05 08:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Tardif 2004-10-04 16:20:00 UTC
Version:           1.3.0 (using KDE KDE 3.2.2)
Installed from:    Compiled From Sources
OS:                Linux

When creating an abstract operation in a class, this class must be set to abstract as well, since a class with any number of abstract methods must be abstract. This can be done manually, but the actual behaviour breaks the UML standard.
Comment 1 Oliver Kellogg 2004-10-05 08:25:24 UTC
Note that the opposite is not true: The fact that no
operation is abstract does not imply that the class must
be non-abstract. In practice this means that setting an
operation to abstract will change the class to be
abstract, but removing the abstractness from the
operation will not remove the class' abstractness -
that must be done manually.