Closed eclipse-ocl-bot closed 1 month ago
By Ed Willink on Jan 18, 2010 12:51
This should be resolved via the model-driven library.
First the operation signature search should find the oclIsInState model entry.
Then the oclIsInState model entry identifies the OclIsInStateOperation Java implementation class.
The Java implementation class no doubt needs an 'analyze' method in addition to an 'evaluate' method, so that OclIsInStateOperation defines its own irregular argument conversion. Similarly iterators define their distinctive behaviour.
By Ed Willink on Feb 01, 2011 02:37
oclIsInState is no longer a special operation; just defined by the library model like everything else.
By Ed Willink on May 27, 2011 06:40
Resolved for Indigo is 3.1.0 not 3.2.0.
By Ed Willink on May 29, 2012 13:21
Closing all bugs resolved in Indigo.
| --- | --- | | Bugzilla Link | 299966 | | Status | CLOSED FIXED | | Importance | P3 normal | | Reported | Jan 18, 2010 12:40 EDT | | Modified | May 29, 2012 13:21 EDT | | Version | 3.0.0 | | Blocks | 156363 | | Reporter | Alexander Igdalov |
Description
From the code in AbstractOCLAnalyzer.operationCallExpCS it follows that oclIsInState() operation is handled in a different way than other OclAny operations. As a consequence, the implicit collect shorthand - '.' for collections - is not checked.\ In this case dot and arrow accessors produce the same AST for collection sources which is wrong.