Re: [epsilon-dev] Changes required for Pinset (based in Epsilon 1.5) to

[Dimitris Kolovos <dimitris.kolovos@xxxxxxxxxx>]

Thank you for sharing this Alfonso - very helpful!

Going forward and as the team is growing, we should probably consider
setting up an API baseline [1] for Epsilon so that we're aware when
we're introducing API-breaking changes. I've added a card to our
Trello board [2].

Thanks,
Dimitris

[1] https://help.eclipse.org/2019-12/index.jsp?topic=%2Forg.eclipse.pde.doc.user%2Ftasks%2Fapi_tooling_baseline.htm
[2] https://trello.com/c/v0ueF25a

On Sun, 22 Mar 2020 at 13:38, Sina Madani <sinadoom@xxxxxxxxxxxxxx> wrote:
>
> Hi Alfonso,
>
>
>
> Thanks for making these notes – it goes us a good idea of the extent of compatibility and what to look out for in the future. I also noticed that since PinsetModule extends ErlModule, in the interim version you can just override the new “processRules” method rather than executeImpl, like so:
>
>
>
> @Override
>
> protected Object processRules() throws EolRuntimeException {
>
>     for (DatasetRule datasetRule : declaredDatasetRules) {
>
>         datasetRule.execute(context);
>
>     }
>
>     return null;
>
> }
>
>
>
> Also I noticed there is a setContext / getContext, which can also be omitted (it would be a compilation error currently, since getContext returns IErlContext for ErlModule).
>
>
>
> Thanks,
>
> Sina
>
>
>
> From: alfonso.delavega@xxxxxxx
> Sent: 22 March 2020 13:25
> To: Epislon Project developer discussions
> Subject: [epsilon-dev] Changes required for Pinset (based in Epsilon 1.5) to work with Epsilon Interim version
>
>
>
> Hello,
>
>
>
> As I was considering trying some things with Pinset and Picto, I had to update my pinset sources to be compatible with the Interim version of Epsilon.
>
>
>
> If the Epsilon 2.0 launch is coming, maybe this could be useful for people with plugins based in 1.5 (as Pinset was) wanting to update to the new version.
>
>
>
> Attached you can find a list of notes I took (small changes list, I think I didn't forget anything) and a diff of the concrete executed changes. I also needed to regenerate the parser classes, but I left that out of the diff to avoid polluting it with autogenerated parser rules.
>
>
>
> Cheers,
>
> Alfonso
>
>
>
> _______________________________________________
> epsilon-dev mailing list
> epsilon-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/epsilon-dev



-- 
Dimitris Kolovos
Professor of Software Engineering
Department of Computer Science
University of York
http://www.cs.york.ac.uk/~dkolovos

EMAIL DISCLAIMER http://www.york.ac.uk/docs/disclaimer/email.htm