Deutsch   English   Français   Italiano  
<v97ju2$118im$2@solani.org>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!eternal-september.org!feeder3.eternal-september.org!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail
From: Mild Shock <janburse@fastmail.fm>
Newsgroups: comp.lang.prolog
Subject: Re: Is Scryer Prologs failure measurable? (Was: Holy Grail makes
 People Disappear)
Date: Sat, 10 Aug 2024 13:46:12 +0200
Message-ID: <v97ju2$118im$2@solani.org>
References: <v8gc6e$l44p$1@solani.org> <v952rb$10h3e$1@solani.org>
 <v97f6r$11l7k$1@solani.org> <v97h77$11m5e$1@solani.org>
 <v97het$11mct$1@solani.org> <v97i30$11mn6$1@solani.org>
 <v97icn$11mpq$1@solani.org> <v97j54$11n9o$1@solani.org>
 <v97jkv$118im$1@solani.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 10 Aug 2024 11:46:10 -0000 (UTC)
Injection-Info: solani.org;
	logging-data="1090134"; mail-complaints-to="abuse@news.solani.org"
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Firefox/91.0 SeaMonkey/2.53.18.2
Cancel-Lock: sha1:iNCgkaiEq26q6al02d7rX2IETcM=
In-Reply-To: <v97jkv$118im$1@solani.org>
X-User-ID: eJwFwYEBwCAIA7CXQEuZ52CF/09YEptOJRhETMzNxxMNB8bSW5ko+jMbsExXu86i3ZhE4tjqp9DCp2oDf0VUFSc=
Bytes: 2430
Lines: 40

Hi,

To stabilize Dogelog Player now, there
are only a few important pending tickets,
but the growing pains are basically

to identify the low hanging fruits. I
do not tend to throw a dice, it might
take some time doing nothing, before a

next important ticket is selected based
on some rationalization of a priorization.

Bye

Mild Shock schrieb:
> Hi,
> 
> Currently I have first hand experience how
> difficult it is to model single treaded async
> on top of multi-threaded Prolog,
> 
> since I want to bring Dogelog Player async
> also to formerly Jekejeke Prolog. It wasn't
> so much a problem in the Dogelog Player for
> 
> Java version, since I could replicate the
> JavaScript design. But it is a little
> nasty in the formerly Jekejeke Prolog case,
> 
> since Thread identity from multi-threaded
> Prolog and Task identity from single treaded
> async are not the same, you have to dig
> 
> deeper into stackfull and stackless coroutines,
> to get the Task identity notion correctly.
> I wasn't able to do it yet for formerly
> 
> Jekejeke Prolog, there is still a pending ticket.
> 
> Bye