Nevertheless I have bad news for Prolog (Was: Scryer Prolog has dethroned SWI-Prolog)

From	Mild Shock <janburse@fastmail.fm>
Newsgroups	comp.lang.prolog
Subject	Nevertheless I have bad news for Prolog (Was: Scryer Prolog has dethroned SWI-Prolog)
Date	2025-05-26 12:31 +0200
Message-ID	<1011fub$aab8$1@solani.org> (permalink)
References	(1 earlier) <vsj1k3$m6op$1@solani.org> <vsj227$m717$1@solani.org> <vsrm16$qfne$1@solani.org> <100v02i$93oj$1@solani.org> <1011fck$a9rv$1@solani.org>

Show all headers | View raw

Hi,

But doing the obvious right, is only solid engineering,
it doesn't lead to this advertisement:

testbed for bleeding edge research in logic and constraint programming
https://github.com/mthom/scryer-prolog

Also I doubt that this leads to anywhere, since we
live in a new era of subsymbolic AI and generative AI,
mostlikely pushing the boundaries of some symbolic pipe

dreams which have been anyway invalidated by computational
complexity research, without offering something really
innovative, i.e. only copy pasting SWI-Prolog including

nonsense like libray(sgml) mostlikely leads to nowhere.

Bye

Mild Shock schrieb:
> Hi,
> 
> Interestingly Scryer Prolog does many things right.
> I find the following test case:
> 
> /* Scryer Prolog 0.9.4-403 */
> ?- length(L,2), f(L) = R, S = [_A].
> L = [_B, _C],
> R = f([_B, _C]),
> S = [_A].
> 
> While SWI-Prolog still makes the following error. The
> newly generated _A and _B are not checked whether they
> already appear in the answer elsewhere, causing a name clash:
> 
> /* SWI-Prolog 9.3.22 */
> ?- length(L,2), f(L) = R, S = [_A].
>   = [_A, _B],
> R = f([_A, _B]),
> S = [_A].
> 
> Other Prolog systems that avoid the clash as well are
> Trealla Prolog, and since today Dogelog Player.
> 
> Bye
> 
> Mild Shock schrieb:
>> Hi,
>>
>> It is time for the 2025 Prolog Awards.
>> Are you excited yet?
>>
>> https://9gag.com/gag/aPAXyEP
>>
>> Here is the list:
>>
>> 1. Place: Scryer Prolog, it uses rustyline,
>> very convenient:
>>
>> app<tab>     gives append
>> a<tab><tab>  cycles through letter a predicates
>> length(foo)  shows the matching braket in blue
>> Etc..
>>
>> -1. Place: SWI-Prolog, has no line edit at all
>>
>> Bye
>

Back to comp.lang.prolog | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Streamable DOM and obsolete put_code/[1,2] Mild Shock <janburse@fastmail.fm> - 2025-04-02 11:51 +0200
  Re: Streamable DOM and obsolete put_code/[1,2] Mild Shock <janburse@fastmail.fm> - 2025-04-02 11:56 +0200
    Re: Streamable DOM and obsolete put_code/[1,2] Mild Shock <janburse@fastmail.fm> - 2025-04-02 12:03 +0200
      Space Junk might fall on your head [Scryer Prolog WASM] (Was: Streamable DOM and obsolete put_code/[1,2]) Mild Shock <janburse@fastmail.fm> - 2025-04-05 18:33 +0200
        Editor’s Draf, 10 January 2025 - Trusted Types (Was: Space Junk might fall on your head [Scryer Prolog WASM]) Mild Shock <janburse@fastmail.fm> - 2025-04-05 19:00 +0200
        *** 2025 Prolog Awards *** (Was: Space Junk might fall on your head [Scryer Prolog WASM]) Mild Shock <janburse@fastmail.fm> - 2025-05-25 13:48 +0200
          Scryer Prolog has dethroned SWI-Prolog (Was: *** 2025 Prolog Awards ***) Mild Shock <janburse@fastmail.fm> - 2025-05-26 12:22 +0200
            Nevertheless I have bad news for Prolog (Was: Scryer Prolog has dethroned SWI-Prolog) Mild Shock <janburse@fastmail.fm> - 2025-05-26 12:31 +0200
            Cannot consult/1 after listing/1 (Was: Scryer Prolog has dethroned SWI-Prolog) Mild Shock <janburse@fastmail.fm> - 2025-05-28 12:09 +0200
        Tau-Prolog Code Mirror Integration has Flaws (Was: Space Junk might fall on your head) Mild Shock <janburse@fastmail.fm> - 2025-06-05 09:54 +0200
  Code Generation with write/[1,2] [Some Testcases] (Was: Streamable DOM and obsolete put_code/[1,2]) Mild Shock <janburse@fastmail.fm> - 2025-04-07 09:58 +0200

csiph-web