post-N246 Read- and Write-Option variable_names/1 (Was: DCG restrictions on the left-hand side [Novacore])

Sujet : post-N246 Read- and Write-Option variable_names/1 (Was: DCG restrictions on the left-hand side [Novacore])
De : janburse (at) *nospam* fastmail.fm (Mild Shock)
Groupes : comp.lang.prolog
Date : 10. Aug 2024, 20:20:44

Autres entêtes

Message-ID : <v98b1p$123qt$1@solani.org>
References : 1
User-Agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.18.2

UWN is testing Prolog systems that don't exist anymore:
Jekejeke 1.5.0
https://www.complang.tuwien.ac.at/ulrich/iso-prolog/variable_names#73
a) There is no more publicitly available Jekejeke
Prolog anymore, I think I wrote UWN already in the
past about that.
b) There is only Dogelog Player, which has a 100%
Prolog written read/write predicates including
the variable_name/1 option. Source code is here,
you also find GIT access etc to the Prolog system:
Quelltexte und Archive des Dogelog Spieler.
https://www.xlog.ch/izytab/doclet/docs/07_spec/02_dogelog.html
c) There is an internal version of Jekejeke Prolog,
which is way after 1.5.0, with version 1.7.0, but
it also uses the Dogelog Payer 100% Prolog
written read/write, so no need to test.
Mild Shock schrieb:

Guess how many newer Prolog systems allow this here:
?- [user].
p;q --> r.
true.
On the other hand SWI-Prolog disallows it:
?- [user].
p;q --> r.
ERROR: user://1:29:
ERROR: No permission to define dcg_nonterminal `p;q'

Date	Sujet	#	Auteur
30 Jul 24	DCG restrictions on the left-hand side [Novacore]	15	Mild Shock
30 Jul 24	Re: DCG restrictions on the left-hand side [Novacore]	4	Mild Shock
30 Jul 24	Re: DCG restrictions on the left-hand side [Novacore]	3	Mild Shock
31 Jul 24	Re: DCG restrictions on the left-hand side [Novacore]	2	Mild Shock
31 Jul 24	Re: DCG restrictions on the left-hand side [Novacore]	1	Mild Shock
10 Aug 24	post-N246 Read- and Write-Option variable_names/1 (Was: DCG restrictions on the left-hand side [Novacore])	7	Mild Shock
10 Aug 24	Re: post-N246 Read- and Write-Option variable_names/1 (Was: DCG restrictions on the left-hand side [Novacore])	6	Mild Shock
11 Aug 24	Is a PIP for Syntax extensions necessary? (Was; post-N246 Read- and Write-Option variable_names/1)	5	Mild Shock
11 Aug 24	Re: Is a PIP for Syntax extensions necessary? (Was; post-N246 Read- and Write-Option variable_names/1)	4	Mild Shock
11 Aug 24	Re: Is a PIP for Syntax extensions necessary? (Was; post-N246 Read- and Write-Option variable_names/1)	3	Mild Shock
11 Aug 24	Re: Is a PIP for Syntax extensions necessary? (Was; post-N246 Read- and Write-Option variable_names/1)	2	Mild Shock
11 Aug 24	Re: Is a PIP for Syntax extensions necessary? (Was; post-N246 Read- and Write-Option variable_names/1)	1	Mild Shock
13 Aug 24	A PIP classification scheme is needed (Was: DCG restrictions on the left-hand side [Novacore])	3	Mild Shock
13 Aug 24	Re: A PIP classification scheme is needed (Was: DCG restrictions on the left-hand side [Novacore])	2	Mild Shock
13 Aug 24	Re: A PIP classification scheme is needed (Was: DCG restrictions on the left-hand side [Novacore])	1	Mild Shock

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal