| [OCLinEcore][bug?] @pre tag and isPre() method not working properly [message #1053569] |
Mon, 06 May 2013 10:46  |
Eclipse User |
|
|
|
Hi,
When using the isPre() method of org.eclipse.ocl.examples.pivot.PropertyCallExp, the returned boolean is always false.
I have also noted that if a add a @pre using the OCLinEcore editor,it does not produce an error, but the tag is not stored in the ecore. This makes me think that, the tag is being parsed but it is not being processed(saved)
This might be the same bug that QVTrelations had(top not being copied from CST to AST)
Best,
Tiago Guimarães
|
|
|
| Re: [OCLinEcore][bug?] @pre tag and isPre() method not working properly [message #1053589 is a reply to message #1053569] |
Mon, 06 May 2013 11:58  |
| Eclipse User |
|
|
|
HI
QVTr 'top' was definitely a bug.
@pre is similar and easily fixed for properties, a bit harder for
operations. (Should be fixed in M7).
But I recently started thinking about implementing @pre evaluation and
realised that while for many examples it is trivial, in the general case
it is necessary to make a complete copy of the system state!
Regards
Ed Willink
On 06/05/2013 15:46, Tiago Guimarães wrote:
> Hi,
>
> When using the isPre() method of
> org.eclipse.ocl.examples.pivot.PropertyCallExp, the returned boolean
> is always false.
>
> I have also noted that if a add a @pre using the OCLinEcore editor,it
> does not produce an error, but the tag is not stored in the ecore.
> This makes me think that, the tag is being parsed but it is not being
> processed(saved)
>
>
> This might be the same bug that QVTrelations had(top not being copied
> from CST to AST)
>
>
> Best,
> Tiago Guimarães
|
|
|
|
|
|
| Re: [OCLinEcore][bug?] @pre tag and isPre() method not working properly [message #1058055 is a reply to message #1057982] |
Fri, 10 May 2013 12:30 |
| Eclipse User |
|
|
|
Hi
If you're using the Pivot model for your own purposes, you need to note
that some increased UML alignments in M7.
Removed:
NamedElement.ownedRule
Added:
Namespace.ownedRule - not used might be removed
Type.ownedInvariants
Operation.preconditions, postconditions, bodyExpression
Property.defaultExpression
There will be further minor changes for UML alignment and
auto-generation appears after Kepler.
Regards
Ed Willink
On 10/05/2013 11:29, Tiago Guimarães wrote:
> Oh, just found my mistake...
>
> I'm running in standalone, and I updated the Eclipse plug-in but did
> not change the jar being used in the build path, so it was still using
> the old version jar.(That's why the editor was working, but the api
> wasn't)
>
>
> Sorry about your lost time,
> Tiago Guimarães
|
|
|
Powered by
FUDForum. Page generated in 0.34379 seconds
Home