Re: [qvtd-dev] QVTc split into QVTcoreBase and QVTimperative

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi

You should n't need to worry about coreBase, it is a sharing mechanism 
for the editors.

We have no plans to evaluate anything other than QVTimperative, so you 
can just have your visitor derive from QVTimperative wherever it used to 
derive from QVTcore. (Changing your classes names name from "...core..." 
to "...imperative..." or just "...i..." might be clearer.)

    Regards

        Ed


On 13/03/2013 12:27, Horacio Hoyos Rodriguez wrote:
> Hi Ed,
>
> I have implemented separate visitors for the coreBase and imperative ASTs
> to work with the changes in the mapping composition and mapping calls.
> Still haven't tested that it is all working.
>
> Regards,
>
>
> Horacio Hoyos Rodríguez
> EngD Student
> University of York
>
>
> -----Original Message-----
> From: qvtd-dev-bounces@xxxxxxxxxxx [mailto:qvtd-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Ed Willink
> Sent: 08 March 2013 14:35
> To: qvtd-dev@xxxxxxxxxxx
> Subject: [qvtd-dev] Distinct QVTi editor
>
> Hi Horacio
>
> The distinct QVTi editor is now available on GIT master. Attached is a
> patch that eliminates the compilation errors in your plugins; no guarantee
>
> that the fixes are actually correct.
>
> A number of name changes are inevitable; e.g ImperativeModel rather than
> CoreModel. QVTimperativeVisitor rather than QVTcoreVisitor.
>
> Many names have been promoted to QVTcoreBase that is common to QVTcore and
>
> QVTimperative.
>
> I've eliminated the MappingCall from QVTc and the composed/refined
> mappings from QVTi. Anything else fundamental that should change?
>
>       Regards
>
>           Ed
> _______________________________________________
> qvtd-dev mailing list
> qvtd-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/qvtd-dev
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.2904 / Virus Database: 2641/6166 - Release Date: 03/12/13