prolog

Is your feature request related to a problem? Please describe.
CSV files produced in different locales have different default separators, a comma-separated file (",") is but one type of CSV.

In Sweden we usually use a semicolon (";") as separator and many CSV files use a tab as separator ("\t"). Importing CSVs requires reformatting them before import, and causes inoperability issues and f

Hi,

%%logica Engineers

@Engine("sqlite");

Employee(name: "Alice", role: "Product Manager");
Employee(name: "Bob", role: "Engineer");
Employee(name: "Caroline", role: "Engineer");
Employee(name: "David", role: "Data Scientist");
Employee(name: "Eve", role: "Data Scientist");

Engineers(..r) :- Employee(..r), r.role == "Engineer";  # <====== This fails
# Engineers(name:, role:) :-

May I suggest the following conforming extension to writing large integers in Prolog source files:

The tokenizer could be extended by accepting _ (underscore) between digits, so that large integers can for example be written as:

1_234_000

This would make large integers that occur in programs easier to read.

In addition, _ could be followed by newline so th

Hi there,

Thanks for this amazing module.

I think there is a problem with the way terms are printed.
I run some Prolog code from Python, querying Prolog with:

H = pyswip.Variable()
induce = pyswip.Functor('induce', 1)
q = Query(induce(H))
q.nextSolution()
print(H.value)

I get a result like this for H:

[Functor(319757,2,
 [Functor(9048461,3,_10560234,_10560236,_1056023