eclipse-ocl-bot
commented
1 month ago By Ed Willink on May 23, 2015 11:59
(In reply to Ed Willink from comment #0)
New syntax |? for explicitly non-null-free, |1 for null-free.
In Ecore, we will need an EAnnotation.
In UML, we will need a stereotype.
All done for RC2.However it is all too new so it is disabled by the default validation severities being Ignore.
Bug 468111 raised to continue work by exploiting null-free collections throughout the pivot model.
| --- | --- | | Bugzilla Link | 467388 | | Status | RESOLVED FIXED | | Importance | P3 normal | | Reported | May 15, 2015 06:19 EDT | | Modified | May 26, 2015 06:29 EDT | | Reporter | Ed Willink |
Description
Introducing the appropriate validations to assist in the use of safe navigation operators reveals that safe navigation is a real pain without the ability to declare null-free collections; every access to any existing non-null-free collection requires a safe navigation operator. RoyalAndLoyal.ocl just falls apart.
So we must have null-free collections.
In OCL, a multiplicity suffix may do: e.g. Set(String[|1]) Set of 0.. String whose per-element multiplicity is 1.
New syntax |? for explicitly non-null-free, |1 for null-free.
In Ecore, we will need an EAnnotation.
In UML, we will need a stereotype.