Dear SWI-Prolog user, SWI-Prolog 8.3.19 is ready for download. Highlights: Several bug fixes, notably for incremental and monotonic tabling. More SICStus 4 emulation by @dgelessus Several documentation fixes by various people Addition of single sided unification and committed choice rules (=>,…

Hi Jan, Picat’s single sided unification rules (“pattern matching” and Neng-Fa Zhou refers to them) looks a quite interesting addition! We also considered adding them (or some similar mechanism) to Ciao Prolog but we were a bit unsure about syntax and semantics, specially because we already cover s…

The subsumes_term/2 guarantees the clause head is more generic than the goal term and thus unifying the two does not affect any of the arguments of the goal. I reread this many times and can not make sense out of this — what is the “goal term”, and what “affecting” does this aim to avoid … Could…

[image] jfmc: Do you think that this may become a more or less standard Prolog feature (clear and stable syntax and semantics) a-la DCGs? I’m afraid I don’t have a crystal ball :slight_smile: We’ll see. I’m quite definitely going to be a serious user. Considering likes and some private di…

From SWI-Prolog manual It is likely that in due time significant parts of the libraries will be migrated to use SSU rules, turning many silent failures on type errors into errors. As I am one who does look at the source code for SWI-Prolog for examples, upon reading that I can fully understand h…

[image] EricGT: Perhaps the version of Prolog just before this should be archived for historical purposes because once => starts to creep in I think many who are not up with the current code will be lost when looking at the new code using => Or just look at this: …

I think you are missing my point. The code most recently before => was introduced is IMHO the last version of the SWI-Prolog code that was built using classic Prolog, e.g. syntactic unification (Yes I know SWI-Prolog uses cuts and other things that are not pure but it is mostly classic Prolog that …

Something in 3.8.19 has broken my code that works with 3.8.18. I will try to isolate the change using binary search on the commits, but it’ll take a while. (I don’t think it’s the Picat-ish changes to lists.pl because the problem shows as a failure deep inside processing a complex data structure an…

It appears that ADDED: Single sided unification with commit clauses using `=>`. · SWI-Prolog/swipl-devel@f24b5cf · GitHub caused the breakage. I’ll try to isolate the problem further, but don’t know if I’ll be able to do that today.

It is archived, all the source code and the docs are kept in git. You could check out the last commit before => was introduced and fork it for posterity.

And ordsets.pl was modified here (along with the the VM changes that added SSU) - warning: Discourse mangles the URL, so you’ll have to search down the page for ordsets.pl: ADDED: Single sided unification with commit clauses using `=>`. co…

Ann; SWI-Prolog 8.3.19

Releases

peter.ludemann February 10, 2021, 10:11pm 6

Or just look at this:

Topic		Replies	Views
Ann: SWI-Prolog 8.3.21 Releases	1	644	March 26, 2021
Ann: SWI-Prolog 8.4.0 Releases ssu	2	1375	October 10, 2021
Ann: SWI-Prolog 8.3.22 Releases	0	393	April 6, 2021
Ann: SWI-Prolog 8.3.14 Releases	5	681	December 2, 2020
Ann: SWI-Prolog 8.3.1 Releases	0	389	June 8, 2020

Ann; SWI-Prolog 8.3.19

Related topics