Re: Is a PIP for Syntax extensions necessary? (Was; post-N246 Read- and Write-Option variable_names/1)

Liste des GroupesRevenir à l prolog 
Sujet : Re: Is a PIP for Syntax extensions necessary? (Was; post-N246 Read- and Write-Option variable_names/1)
De : janburse (at) *nospam* fastmail.fm (Mild Shock)
Groupes : comp.lang.prolog
Date : 11. Aug 2024, 00:16:31
Autres entêtes
Message-ID : <v98ort$12bb4$1@solani.org>
References : 1 2 3 4 5
User-Agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.18.2
So we have two victims in 2024, two
things died in 2024, are pepsi now:
- Scryer Prolog
- SWI-Prolog Dicts
LoL
Mild Shock schrieb:
Anything that touches or depends on syntax
is a complete can of worms. The ISO commitee
was not able to find an initial *english natural
 language specification wording* for character
look-ahead, so that we find now character
look-ahead in Prolog compounds practially
 implemented by all Prolog systems, but character
look-ahead interpretation may differ for
negative numbers, like here:
 /* SWI-Prolog */
?- X = - 1^2, write_canonical(X), nl.
-(^(1,2))
 /* Scryer Prolog */
?- X = - 1^2, write_canonical(X), nl.
^(-1,2)
 But in the case of Scryer Prolog it doesn't
matter, since Scryer Prolog is anyway dead.
 Mild Shock schrieb:
I have a question, does SWI-Prolog not anymore use
their dict syntax in the Janus interface:
>
 > import janus_swi as janus
 > janus.query_once("Y is X+1", {"X":1})
{'Y': 2, 'truth': True}
>
I don’t see _{...} anymore. When and how did this
happen? I was just thinking whether a Syntax
extension PIP is necessary. Such a PIP isn’t listed:
>
https://prolog-lang.org/ImplementersForum/PIPs.html
>
Is SWI-Prolog safe, against parsing problems,
when it still has block operators in the
background? Like can one mix and match
>
code that uses Janus interface with the
“new” dicts with other code that uses the
SWI-Prolog dicts based on _{...}
>
which we might now term the “old” dicts.
How do you access and manipulate the
“new” dicts, do the “old” operations work?

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

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal