Hi Dimitris,
Actually in both branches there are a few tests (the same tests) that fail which I have commented out (in EplTests/test.epl). Before merging maybe it's worth investigating? Perhaps the "failures" are due to my misunderstanding of the EPL specification, or they may be genuine bugs.
Thanks,
Sina
Hi Sina,
Since all tests pass, merging the new, improved version of EPL into
master sounds fine to me!
Cheers,
Dimitris
On Fri, 24 Apr 2020 at 19:31, Sina Madani <sinadoom@xxxxxxxxxxxxxx> wrote:
>
> Hi everyone,
>
>
>
> I have been working on making EPL more extensible so that alternative implementations are possible, as well as some minor bug fixes. This has resulted in a major refactoring, and I have added a more complete test (see test.epl) for the semantics. The results are the same in both the epl-refactoring branch and master. I have also added some javadocs to the refactored code so that it’s easier to understand what’s going on, although in both the master and refactoring branch the code is extremely complex and difficult to understand due to the inherent complexity of EPL. However, I hope the refactored version is a bit cleaner. If there are no objections, I propose to merge this branch into master so that a parallel implementation can be added (parallelisation based on patterns).
>
>
>
> Thanks,
>
> Sina
>
>
>
> _______________________________________________
> 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
_______________________________________________
epsilon-dev mailing list
epsilon-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/epsilon-dev
