search

eclipse-ocl / org.eclipse.ocl

Eclipse Public License 2.0
0 stars 0 forks source link

[pivot] PropertyCallExp.type uses behavioral type #1626

Closed eclipse-ocl-bot closed 1 month ago

eclipse-ocl-bot commented 1 month ago

| --- | --- | | Bugzilla Link | 480018 | | Status | RESOLVED FIXED | | Importance | P3 normal | | Reported | Oct 17, 2015 06:36 EDT | | Modified | Oct 22, 2015 06:56 EDT | | Reporter | Ed Willink |

Description

The use of the behavioral type for PropertyCallExp.type causes a problem for the QVTd HSV2HLS trnasformayion that finds itself dealing with String rather than a relevant DataType.

Behavioral types should not be persisted, just used to find alternatives when looking up, e.g. on types of sources.

eclipse-ocl-bot commented 1 month ago

By Ed Willink on Oct 22, 2015 06:48

This hits a few FIXMEs nicely, but there are about 20 getType() that no longer do a getBehavioralClass resolution inside. A few of these are flushed out by JUnit tests in OCL and some more in QVTd.

Fundamentally the clean up carries a risk that some uses of e.g. Ecore::EInt may fail to be treated as Integer.

eclipse-ocl-bot commented 1 month ago

By Ed Willink on Oct 22, 2015 06:56

Pushed to master for M3