|
| Re: [QVTO] Implementation specific features [message #487330 is a reply to message #487300] |
Tue, 22 September 2009 19:15  |
Eclipse User |
|
|
|
Originally posted by: dvorak.radek.gmail.com
Hi Derek,
The Element::container() operation is not Ecore specific, it's EMOF
counterpart of Ecore's EObject::eContainer() that is supposed to be
available in QVTO.
The Stdlib model shows operations that are available. You can inspect
the QVTO standard library in the Metamodel browser.
There is just a couple of implementation specific operations kept for
backward
compatibility, for instance dump(...). These are annotated as 'depreated'
so the QVTO compiler issues a warning notifying the user about this.
There is another annotation - 'unsupported', marking those operations that
are recognized by the compiler but reported as "Not yet supported".
It may rather happen that something is missing then some other impl
specific extensions found.
Remark: as for the Metamodel browser usecase, I have just found a minor
defect -
QVTO must be initialized first to have the Stdlib model visible in the
browser.
Ensure you open a *.qvto file before you open the Metamodel browser.
Regards,
/Radek
On Tue, 22 Sep 2009 19:22:20 +0200, Derek Palma <derek.palma@gmail.com>
wrote:
> Hi,
>
> I have been studying the available operations available in QVT using the
> QVT spec. However, I'd like to also know the operations added by the
> implementation that are not described in the spec. For example,
> Elements::container() seems to be Ecore specific. Is there file I can
> refer to to see this list of extensions? Maybe I should look at a model
> which contains the definitions of the operations? Knowing the ecore
> specific extensions can be quite useful.
>
> Derek
|
|
|
Powered by
FUDForum. Page generated in 0.03123 seconds
] 
Search
Help
Register
Login
Home
