Bugzilla – Full Text Bug Listing
| Summary: | [Xtend/Xbase] Compiler breaks specification of boolean operator && | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Robert von Massow <rvonmassow> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | sven.efftinge |
| Version: | 2.0.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
*** This bug has been marked as a duplicate of bug 342424 *** |
Build Identifier: The following expression is not compiled correctly: cb.contents.size == 1 && !cb.contents.head.toString.contains("\n") the compiled Java code looks like this: EList<EObject> _contents = cb.getContents(); int _size = _contents.size(); boolean _operator_equals = ObjectExtensions.operator_equals(((Object)_size), 1); EList<EObject> _contents_1 = cb.getContents(); EObject _head = IterableExtensions.<EObject>head(_contents_1); String _string = _head.toString(); boolean _contains = _string.contains("\n"); boolean _operator_not = BooleanExtensions.operator_not(_contains); boolean _operator_and = BooleanExtensions.operator_and(_operator_equals, _operator_not); According to the Xbase specification the right hand side of the operator && is not evaluated if the left hand side is already false. This is not achieved in this case, thus an exception is thrown if cb.contents is empty anthough it has been checked to be non-empty. Reproducible: Always