[gecode-users] Problem with Flatzinc 1.0 on Gecode 2.0

Raffaele Cipriano cipriano at dimi.uniud.it
Thu Feb 7 11:40:31 CET 2008


> Maybe your source files have Windows newline characters instead of 
> Unix newline, I think the lexer doesn't handle those yet.  Try to run 
> the sources through dos2unix, I hope that helps.  I'll see how to 
> change the lexer accordingly.
>
Ok, using dos2unix fix the problem and I can run the test.fzn file, 
thank you very much!
Perhaps I  misunderstood... I thought the parser would have returned a 
gecode space in a c++ file, for example golomb_0.cc, to be compiled and 
executed...is the gecode space only an internal translation? is it 
directly executed by the fz command?


Anywat I have some problem with the golomb_0.fzn code: fz gives me these 
error message:

$ Error: syntax error in line no. 33

    where line 33 is

33     int: gol_length = 17;

I can delete this line (gol_length is never used in the file), but I get


$ Error: Registry: Constraint int_lin_lt not found in line no. 280

    and line 280 is

279    constraint
280          int_lin_lt([ -1, 1, 1, -1 ], [ mark[0], mark[1], mark[4], 
mark[5] ], 0);


It seems that it doesn't recognize the int_lin_lt constrain...the file 
(that correctly runs using $flatzinc golomb_0.fzn ) was generated with 
the mzn2fzn parser...suggestion?

Thank you

Cheers

Raffaele





More information about the gecode-users mailing list