Issue 18516: Introduce a Safe Navigation Operator (ocl2-rtf) Source: Model Driven Solutions (Dr. Edward Willink, ed(at)willink.me.uk) Nature: Clarification Severity: Minor Summary: Languages such as Groovy have found it helpful to intrioduce the safe navigation operator ?: so that navigation over null yields null rather than a problem (invalid in OCL). In OCL it could be a pure syntax sugar: (x?.y) = (if x == null then null else x.y endif) or perhaps an additional PropertyCallExp operator Resolution: Revised Text: Actions taken: March 1, 2013: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 01 Mar 2013 05:09:26 -0500 To: Subject: Issue/Bug Report X-Brightmail-Tracker: AAAAAR0YqyA= X-Brightmail-Tracker: AAAAAA== ******************************************************************************* Name: Edward Willink Employer: mailFrom: ed@willink.me.uk Terms_Agreement: Specification: OCL Section: n/a FormalNumber: 12-01-01 Version: 2.3.1 Doc_Year: Year Doc_Month: Month Doc_Day: Day Page: n/a Title: Introduce a Safe Navigation Operator Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Description: Languages such as Groovy have found it helpful to intrioduce the safe navigation operator ?: so that navigation over null yields null rather than a problem (invalid in OCL). In OCL it could be a pure syntax sugar: (x?.y) = (if x == null then null else x.y endif) or perhaps an additional PropertyCallExp operator