[umbrello] [Bug 123276] multiplicities should be possible for attributes and not just for associations

[Robert Hairgrove]

https://bugs.kde.org/show_bug.cgi?id=123276

Robert Hairgrove <code at roberthairgrove.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |CONFIRMED
                 CC|                            |code at roberthairgrove.com
     Ever confirmed|0                           |1

--- Comment #3 from Robert Hairgrove <code at roberthairgrove.com> ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.