Re: [mdt-ocl.dev] Patch for https://bugs.eclipse.org/bugs/show_bug.cgi?i

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi Axel

There are also QVTr and QVTc, which I'm responsible for. They are not in 
themselves sufficiently useful that they should inhibit an API 
evolution. But...

In developing QVTr and QVTc and after very superficial scanning of QVTo 
and Acceleo code, I am aware how inextensible the current CST and 
Environment APIs are. As a result derived code tends to do sneaky 
interceptions of protected methods, so anything that breaks the precise 
control flow of any derivable method may break derived code. It's a 
nightmare. I will almost certainly veto any proposed API change that is 
not clearly an addition only.

    Regards

        Ed

On 06/03/2011 09:07, Axel Uhl wrote:
> Ed,
>
> > it is semantically affected. This includes a review of QVTo and Acceleo
> > code which will inherit the changed parser grammar.
>
> are there clients of the concrete syntax tree beyond the analyzers in 
> the org.eclipse.ocl.* domain?
>
> I'm currently contemplating adding flavors of the 
> tryLookupClassifier(...) methods that take an additional 
> global:boolean flag and have the existing methods delegate to them. 
> That to me sounds API-compatible, particularly since the global-flag 
> would always be false unless set by the new ::-prefix.
>
> Best,
> -- Axel
> _______________________________________________
> mdt-ocl.dev mailing list
> mdt-ocl.dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 10.0.1204 / Virus Database: 1435/3484 - Release Date: 03/05/11