Issue 6887: Allow implicit type casting to boolean when a boolean is expected (ocl2-rtf)
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Uncategorized Issue
Severity: 
Summary: Example1:   if list.select(...) then … equivalent to 
                        if list.select(...)->notEmpty() then … 
     Example2:  if item then … equivalent to 
                      if item<>OCLUndefined then ... 

Resolution: The suggestion introduces a confusion for Boolean variables that may be null. For these variables <> null is required while for non-Boolean variables it can be omitted.
This seems to be a significant degradation in type safety. Not even Java permits this freedom.
Disposition: Closed, no change
Revised Text: 
Actions taken:
January 7, 2004: received issue
December 23, 2013: closed issue
Discussion: 
This is a request to improve the language. Better solved in a RTF.
End of Annotations:=====
SSUE:  Allow implicit type casting to boolean when a boolean is expected 
     in an expression. 
     Example1:   if list.select(...) then … equivalent to 
                        if list.select(...)->notEmpty() then … 
     Example2:  if item then … equivalent to 
                      if item<>OCLUndefined then ...