You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Flatzinc reference the string syntax is informally described as "Strings have the same syntax as in C programs". This is not correct. They have a similar syntax as in C programs.
The FlatZinc Grammar is described as "a proper subset of the MiniZinc grammar", and defines string literals as follows:
(Side note: this has the same problem with the meaning of \nas in Issue #722)
This grammar seems to say that "\k" (and similar constructs, e.g. "\)") is a valid string-literal in FlatZinc but I see no description about what that would mean. In either case, this would make it no longer "a proper subset of the MiniZinc grammar", since the MiniZinc grammar does not permit e.g. \k in string literals.
PS. the casifaction Flatzinc and FlatZinc seems to be used inconsistently in the manual.
(This kind of nit picking is what you get for making a popular system where others want to build compatible parsers :-) )
The text was updated successfully, but these errors were encountered:
In the Flatzinc reference the string syntax is informally described as "Strings have the same syntax as in C programs". This is not correct. They have a similar syntax as in C programs.
The FlatZinc Grammar is described as "a proper subset of the MiniZinc grammar", and defines string literals as follows:
(Side note: this has the same problem with the meaning of
\n
as in Issue #722)This grammar seems to say that
"\k"
(and similar constructs, e.g."\)"
) is a valid string-literal in FlatZinc but I see no description about what that would mean. In either case, this would make it no longer "a proper subset of the MiniZinc grammar", since the MiniZinc grammar does not permit e.g.\k
in string literals.PS. the casifaction
Flatzinc
andFlatZinc
seems to be used inconsistently in the manual.(This kind of nit picking is what you get for making a popular system where others want to build compatible parsers :-) )
The text was updated successfully, but these errors were encountered: