Path: csiph.com!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail From: Mild Shock Newsgroups: comp.lang.javascript Subject: Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Date: Sat, 23 Mar 2024 16:43:09 +0100 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sat, 23 Mar 2024 15:43:08 -0000 (UTC) Injection-Info: solani.org; logging-data="1823767"; 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.1 Cancel-Lock: sha1:72Pg2NT2qenEfC0+QOMW6z354QM= In-Reply-To: X-User-ID: eJwFwYEBACAEBMCVkH8ap8T+I3SHRWWFE3QMJjpTirqPAKdd1z11p0SRAQnP8Ub22+JqZmQSYjrL+HzbBzkOFBQ= Xref: csiph.com comp.lang.javascript:124321 Dogelog Player is a Prolog system that features a generational garbage collector scheme and a change_arg/3 primitive built-in. So far the two didn’t go together and we had to use a cludge. With the upcoming release we provide a proper solution based on marking write-barriers. Our remembered set on the variable binding trail has the benefit that it can reduce itself during backtracking. By adopting conductor variables, i.e. instantiated variables that are not trailed, from formerly Jekejeke Prolog, we could recreate a similar benefit for Dogelog Players change_arg/3. See also: Marking Write-Barriers for Dogelog Player https://twitter.com/dogelogch/status/1771559896741192186 Marking Write-Barriers for Dogelog Player https://www.facebook.com/groups/dogelog