Sujet : When did the Dogelog Player Quantum Leap happen? (Was: There is no flesh and blood async Prolog!)
De : janburse (at) *nospam* fastmail.fm (Mild Shock)
Groupes : comp.lang.prologDate : 19. Jun 2025, 13:11:40
Autres entêtes
Message-ID : <1030ups$10ir8$1@solani.org>
References : 1 2 3 4
User-Agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0 SeaMonkey/2.53.21
Hi,
When did the quantum leap happen in Dogelog Player?
Well very early on: The first binary release was here:
ANN: Dogelog Player 0.9.7
The new version 0.9.7 of the Dogelog
player now masters DCG.
Admin User, created 09/06/2025
And '$YIELD'/1 stuff came 9 months (sic!) later:
ANN: Dogelog Player 0.9.8
The Dogelog Player supports a new interpreter
that can relinquish control.
Admin User, created 21/03/2022
See for your self:
https://www.xlog.ch/izytab/doclet/home/12_news/package.html9 months, like Homo sapiens gestation period. (*)
LoL
Bye
(*) To be frank, it was the perfect pass time during
the COVID-19 pandemic.
Mild Shock schrieb:
Hi,
Somebody wrote:
> Right, but what I’m saying is that with the
> current implementation as a separate process,
> running independently of the editor and only
> communicating over the channel defined by the
> protocol, the ability to have fine-grained
> asynchronous communication is limited.
Not my problem not seeking the state of the art. You
need of course a Prolog system that is all flesh
and blood cooperative multitasking. If you want
to do a GUI in Prolog similar like JavaScript
does it now, or a native GUI adapter. And I don't
count Tau-Prolog, although they showed amazing
stuff. But not amazing enough, still based
on continuations, and not based on promises. Or then
async/await. I am not sure what SWI WASM now delivers?
SWI Tinker shows me errors talking about threads when
I use the query background execution feature and if I
abort. But people from cooperative multitasking tend
to not use the terminology "thread", they prefer to
talk about "tasks". Ciao Playground doesn't count either,
since their channels to a background worker can even
not process an interrupt correctly.
Bye
Mild Shock schrieb:
Hi,
>
The fukkers stole my name:
>
Jan - Local AI Assistant
https://github.com/menloresearch/jan
>
Bye
>
P.S.: Meanwhile I am struggling with Quantum Paper
whille doing a dark/light CSS. Look my light olive turned dark
olive, that is somewhere near chocolate or is it dog shit?
>
P.P.S.: Just figured out yesterday that some browser defaults
are more Motif/OSF than Material/Google, aka Quantum Paper.