From: triska <triska@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New Package: scryer-prolog-0.8.123
Date: Tue, 28 Jul 2020 20:59:44 +0200 [thread overview]
Message-ID: <20200728185944.ijiNnS9sDSenzvprPP2Ys5UDiZCHBdWkXMWwtrbdgHg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23821@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
New comment by triska on void-packages repository
https://github.com/void-linux/void-packages/pull/23821#issuecomment-665219062
Comment:
Thank you a lot @Chocimier for merging this!
In several respects, Scryer Prolog is one of the most advanced Prolog systems that currently exists, even though it is still in its early stages of development. For instance, it conforms syntactically to the Prolog ISO standard, it includes extensions for constraint logic programming (CLP), and is the first Prolog system that implements a very compact internal representation of strings as lists of characters. It is an excellent platform to teach Prolog.
For your concrete example, try SLG resolution by adding the following two lines at the start of the program:
<pre>
:- use_module(library(tabling)).
:- table p/2.
</pre>
We then get for the most general query:
<pre>
<b>?- p(A, B).</b>
A = a, B = b
; A = a, B = c
; A = b, B = c
; false.
</pre>
i.e., all solutions are enumerated, and the query *terminates*.
Thank you a again!
next prev parent reply other threads:[~2020-07-28 18:59 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 22:14 [PR PATCH] " mkohlhaas
2020-07-24 23:18 ` [PR PATCH] [Updated] " mkohlhaas
2020-07-24 23:20 ` mkohlhaas
2020-07-25 8:02 ` Chocimier
2020-07-25 8:15 ` [PR PATCH] [Updated] " mkohlhaas
2020-07-25 8:18 ` mkohlhaas
2020-07-25 12:00 ` mkohlhaas
2020-07-25 12:51 ` mkohlhaas
2020-07-26 23:20 ` mkohlhaas
2020-07-26 23:21 ` mkohlhaas
2020-07-27 1:34 ` mkohlhaas
2020-07-27 2:09 ` mkohlhaas
2020-07-27 2:32 ` mkohlhaas
2020-07-27 3:21 ` mkohlhaas
2020-07-27 3:33 ` mkohlhaas
2020-07-27 5:57 ` [PR PATCH] [Updated] " mkohlhaas
2020-07-27 6:15 ` mkohlhaas
2020-07-27 6:44 ` mkohlhaas
2020-07-27 10:59 ` mkohlhaas
2020-07-27 11:21 ` mkohlhaas
2020-07-27 12:05 ` mkohlhaas
2020-07-27 13:46 ` mkohlhaas
2020-07-27 14:26 ` mkohlhaas
2020-07-27 14:29 ` mkohlhaas
2020-07-27 14:38 ` mkohlhaas
2020-07-27 15:38 ` [PR PATCH] [Updated] " mkohlhaas
2020-07-27 15:45 ` mkohlhaas
2020-07-27 16:53 ` mkohlhaas
2020-07-27 16:56 ` mkohlhaas
2020-07-27 17:40 ` Chocimier
2020-07-27 17:42 ` Chocimier
2020-07-27 17:46 ` Chocimier
2020-07-27 18:42 ` [PR PATCH] [Updated] " mkohlhaas
2020-07-27 20:10 ` mkohlhaas
2020-07-28 18:48 ` [PR PATCH] [Updated] " Chocimier
2020-07-28 18:50 ` Chocimier
2020-07-28 18:50 ` [PR PATCH] [Merged]: " Chocimier
2020-07-28 18:53 ` mkohlhaas
2020-07-28 18:54 ` Chocimier
2020-07-28 18:59 ` triska [this message]
2020-07-28 22:43 ` Johnnynator
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200728185944.ijiNnS9sDSenzvprPP2Ys5UDiZCHBdWkXMWwtrbdgHg@z \
--to=triska@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).