search

ikuraj / alloy4eclipse

Automatically exported from code.google.com/p/alloy4eclipse
0 stars 0 forks source link

Evaluator no longer works #86

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The evaluator no longer works since the update to A4 4.2.0 snapshot.

It is only possible to display the univ. For all other sets, the answer is:

X is not bound to a legal value during translation

Original issue reported on code.google.com by daniel.l...@gmail.com on 15 Mar 2010 at 4:04

GoogleCodeExporter commented 8 years ago 
I took a look at it today, and cannot find the root of the problem. It looks 
like an exception is thrown when translating the request from Alloy to kodkod.

The world and ans objects look fine (contain the expected content).

Original comment by daniel.l...@gmail.com on 20 Mar 2011 at 6:30

GoogleCodeExporter commented 8 years ago 
The problem continues with 4.2 RC from April 21, 2011.

We need someone from the Alloy team to check why the evaluator context is no 
longer properly fed.

Original comment by daniel.l...@gmail.com on 5 May 2011 at 8:13

GoogleCodeExporter commented 8 years ago

Original comment by daniel.l...@gmail.com on 19 May 2011 at 8:53

GoogleCodeExporter commented 8 years ago 
We need to sort this out for the new release this year.

The source code for the evaluator is here:
http://code.google.com/p/alloy4eclipse/source/browse/trunk/fr.univartois.cril.xt
ext2.ui/src/fr/univartois/cril/xtext2/alloyplugin/console/AlloyEvaluatorConsole.
java#118

Original comment by daniel.l...@gmail.com on 17 Apr 2012 at 6:33

GoogleCodeExporter commented 8 years ago 
Working on that issue with Aleks from A4 group.

Original comment by daniel.l...@gmail.com on 18 Apr 2012 at 7:36

GoogleCodeExporter commented 8 years ago 
The issue has been fixed: it was caused by a wrong way to retrieve the solution 
from a file.

Original comment by daniel.l...@gmail.com on 6 Jun 2012 at 6:09