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 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: References: 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: 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