Closed lordpretzel closed 6 years ago
added support for that, but data types of DLVars in rules that are generated are not correct which means the problem still exists, e.g., Q(X || Y) :- R(X,Y).
fixed by using translator_dl.c code that sets data types correctly and introduces casts
integer values are not casted to strings in string concatenation in move rules. Example,
is compiled into
For instance, in the first move rule the variable
V0
is of type int, so logicblox will complain if we do not cast this into a string like this:Solution: check data type of variables used in string concatenation and add cast for non-int ones.