-
Key: UML14-868
-
Legacy Issue Number: 1508
-
Status: closed
-
Source: Anonymous
-
Summary:
Summary: It is not very clear how types of attributes and parameters should be instantiated. For example, consider the following C++ methods:
void Draw(Window win);
void Draw(Window* win);
void Draw(Window& win);In all three cases the name of the parameter is "win". The types are "Window", "Window*" and "Window&" respectively. How can these types be modeled? In the first case I can imagine creating a link between the parameter "win" and the Classifier "Window". But what about the remaining two cases?
UML 1.0 represented attribute and parameter types by simple uninterpretted strings. This allowed user to specify any complex language expression for types. I would prefer that this mechanism be reintroduced. The current mechanism may be left in place in case users or tools like to specify tighter bindings to Classifier instances.
-
Reported: UML 1.1 — Sat, 6 Jun 1998 04:00 GMT
-
Disposition: Resolved — UML 1.2
-
Disposition Summary:
Fixed in UML 1.3.
-
Updated: Fri, 6 Mar 2015 21:35 GMT
UML14 — Clarify how types of attributes and parameters should be instantiated
- Key: UML14-868
- OMG Task Force: UML 1.4 RTF