| --- | --- |
| Bugzilla Link | 252976 |
| Status | CLOSED FIXED |
| Importance | P3 minor |
| Reported | Oct 31, 2008 10:34 EDT |
| Modified | May 27, 2011 02:47 EDT |
| Reporter | Ed Willink |
Description
The pathNameCS ‘(‘ argumentsCS? ‘)’ syntax for an operationCallExpCS is realised by the dotArrowExpCS production that covers the operationCallExpCS rather than as specified by operationCallExpCS.
This makes little difference to OCL itself where operationCallExpCS is never used directly. It does however matter to QVTr which re-uses the operationCallExpCS production.
Promoting the G syntax from dotArrowExpCS to operationCallExpCS fixes the problem and introduces no parsing conflicts.
| --- | --- | | Bugzilla Link | 252976 | | Status | CLOSED FIXED | | Importance | P3 minor | | Reported | Oct 31, 2008 10:34 EDT | | Modified | May 27, 2011 02:47 EDT | | Reporter | Ed Willink |
Description
The pathNameCS ‘(‘ argumentsCS? ‘)’ syntax for an operationCallExpCS is realised by the dotArrowExpCS production that covers the operationCallExpCS rather than as specified by operationCallExpCS.
This makes little difference to OCL itself where operationCallExpCS is never used directly. It does however matter to QVTr which re-uses the operationCallExpCS production.
Promoting the G syntax from dotArrowExpCS to operationCallExpCS fixes the problem and introduces no parsing conflicts.