-
Key: OCL25-161
-
Legacy Issue Number: 15234
-
Status: open
-
Source: Model Driven Solutions ( Dr. Edward Willink)
-
Summary:
Issue 7341 changed a number of syntaxes to permit a PathNameCS rather than a SimpleNameCS,
so that scope ambiguities could be resolved.It is not clear why this was applied uniformly to all syntaxes where a name reference is in use. As a minimum
it just gives the user the discretion to clarify a subtle statement, and it avoids the impression that pathed-names
are special. It also avoids the need for some very similar concrete syntax expositions.More specifically in an AssociationClassCallExpCS it would allow disambiguation of Left::Link and Right::Link as
alternate AssociationClasses.Suggest allow PathNameCS in all places where there is not a specific requirement for a SimpleNameCS.
-
Reported: OCL 2.1 — Thu, 29 Apr 2010 04:00 GMT
-
Updated: Thu, 8 Oct 2015 14:12 GMT
OCL25 — OCL 2.2 Generalisation of Issue 7341 PathNames
- Key: OCL25-161
- OMG Task Force: Object Constraint Language 2.5 RTF