Bugzilla – Full Text Bug Listing
| Summary: | [Xcore] Lambda Expressions difficult to use in op | ||
|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Michael Vorburger <mike> |
| Component: | Xcore | Assignee: | Ed Merks <Ed.Merks> |
| Status: | CLOSED FIXED | QA Contact: | Ed Merks <Ed.Merks> |
| Severity: | normal | ||
| Priority: | P3 | CC: | sebastian.zarnekow, sven.efftinge |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 397324 | ||
I just noticed that on http://wiki.eclipse.org/Xcore#Specifying_an_Operation there is a very similar example.. once this is addressed, it may be useful to others to change that to something like: op Book getBook(String title) { books.findFirst( book | book.title == title ) } May be as an alternative to the "classic" Java for (Book book : books) ... Just a thought. Sven, Should/does Xbase check that the referenced identifier is final? Yes, we check that. JvmFormalParameters are always assumed to be final. Unfortunately there is no way to query parameters for their actual final state in the java.lang.reflect API so we had to make some assumptions. I see! If I try to assign a parameter a new value in the XBlockExpression, it makes that same assumption and says I can't do the assignment. That implies I really should generate these parameters as final, at least for the case where I know there is a body generated based on Xbase-specified behavior... Changes to ensure that class methods corresponding to things with bodies specified in the model are generated as final are committed to master. http://git.eclipse.org/c/emf/org.eclipse.emf.git/commit/?id=c890894964aed60c99e76223ac85f14dc1f315af The changes are available in Kepler. |
This doesn't currently work in Xcore: op MdfProperty getProperty(String propertyName) { properties.findFirst( property | property.name == propertyName ) } The Xcore Editor shows no error, but the .java complains because propertyName is not final. The workaround is to use op MdfProperty getProperty(String propertyName) { val finalPropertyName = propertyName properties.findFirst( property | property.name == finalPropertyName ) } which is not so nice.