Summary: | multiplicities should be possible for attributes and not just for associations | ||
---|---|---|---|
Product: | [Applications] umbrello | Reporter: | Edward Nash <edward.nash> |
Component: | general | Assignee: | Umbrello Development Group <umbrello-devel> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | code, me, ralf.habacker |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Edward Nash
2006-03-08 13:40:04 UTC
multiplicities for attributes shown as e.g. + street [0..1] : CharacterString This remains an issue over 3 years later, as of version 2.2.90 (from kubuntu's KDE 4.3 beta2 packages). And, believe it or not, it is still an issue in 2020! Together with multiplicity and the In/InOut/Out type for parameters, there would be almost no need to define special types for pointers and references (in C++, at least): For multiplicity of 1: IN Parameters, if they are datatypes, would be passed by value; INOUT and OUT parameters by non-const reference; IN parameters of class type passed by const reference. For multiplicity of 0..*: IN parameters should be passed as pointer to const type; INOUT and OUT parameters as pointer to non-const type. However, there is quite often the need to model things like char** which would probably need additional constraint extensions if actual pointers as datatypes are added to the existing primitive types. (In reply to Robert Hairgrove from comment #3) > And, believe it or not, it is still an issue in 2020! According to https://umbrello.kde.org/openbugs.php there are about 300 bugs open, and it was already hard work to bring the code into the current form; so any help is welcome :-) |