Path: ...!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:32:53 +0200 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sat, 10 Aug 2024 11:32:52 -0000 (UTC) Injection-Info: solani.org; logging-data="1105208"; 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:9KX3QNN1pC9fksvVGkJgkD7gSnA= In-Reply-To: X-User-ID: eJwNyMEBwCAIA8CVQEnAcQBl/xHaex42le1G0DAYb8yD3z5V/6nlWyYBebnlZmhmWGwnsRyt14rLo1YJx498Tw4U1Q== Bytes: 2471 Lines: 47 Hi, Generally I don't believe in things like SWI-Prolog Janus Python integration. This type of integration has the advantage that SWI-Prolog can run in full speed, on the other hand it has the disadvantage that one cannot take advantage of Python async, because SWI-Prolog itself has no async. I am talking about the single threaded async here. My experience single treaded async and multi-threaded Prolog are quite different pairs of shoes. So when doing the C# backend for Dogelog Player, I will be faced again to provide a complete async solution for the async part of Novacore. Woa! Bye Mild Shock schrieb: > Hi, > > A few days age we improved the cross referencer, > to deal with the many target platforms. The > old cross referencer for example showed: > > xor/3        nova/Eval.java >              nova/eval.mjs >              nova/eval.py > > Meaning the evaluable function xor/3 is > available in Java, JavaScript and Python. > What we now do, we simply show: > > xor/3        nova/eval.* > > Soon the wildcard will mean C# as well, > and not only Java, JavaScript and Python. > Extending the proof of concept for Prolog > > compiler 100% written in Prolog itself. > > Bye