Issue 6609: OclUndefined / allInstances() clarification. (ocl2-rtf) Source: Modeling Value Group (Mr. Wim Bast, wim.bast(at)modelingvalue.nl) Nature: Uncategorized Issue Severity: Summary: think the operation allInstances() is under-specified in the current version of the OCL 2.0 specification. It does not seem to be clear whether OclUndefined is included in the returned set or not: According to the 1.5 specification of allInstances(), the instances of all subtypes are included. OclVoid is a subtype of all other types, thus OclUndefined would be a part of the set. I assume this is not the intended behaviour. For example, the "all names must be different" expression example would always yield OclUndefined or false, but never true. Resolution: Revised Text: Actions taken: November 13, 2003: received issue Discussion: Deferred for timing reasons End of Annotations:===== m: webmaster@omg.org Date: 13 Nov 2003 05:41:58 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Wim Bast Company: Compuware Corporation mailFrom: wim.bast@nl.compuware.com Notification: No Specification: OCL 2.0 Section: 11.2.4 FormalNumber: ptc/03-10-14 Version: 2.0 RevisionDate: sep 2003 Page: 151,152 Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461) Description OclUndefined / allInstances() clarification. I think the operation allInstances() is under-specified in the current version of the OCL 2.0 specification. It does not seem to be clear whether OclUndefined is included in the returned set or not: According to the 1.5 specification of allInstances(), the instances of all subtypes are included. OclVoid is a subtype of all other types, thus OclUndefined would be a part of the set. I assume this is not the intended behaviour. For example, the "all names must be different" expression example would always yield OclUndefined or false, but never true.