Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #53761 > unrolled thread

ANN: Dogelog Player 2.2.2 (Unified Tabling)

Back to article view | Back to comp.lang.java.programmer

Contents

  ANN: Dogelog Player 2.2.2 (Unified Tabling) Mild Shock <janburse@fastmail.fm> - 2026-05-01 23:30 +0200
    Re: ANN: Dogelog Player 2.2.2 (Unified Tabling) root <root@root.com> - 2026-05-07 15:58 -0300
    Dogelog Player on a A18 Everest (Re: ANN: Dogelog Player 2.2.2 (Unified Tabling)) Mild Shock <janburse@fastmail.fm> - 2026-05-16 11:19 +0200

#53761 — ANN: Dogelog Player 2.2.2 (Unified Tabling)

Dear All,

We are happy to announce a new edition
of the Dogelog Player:

- Tabling Directive:
It turns out that our term expansion is fit
enough to provide a tabling directive table/1.
The directive will prepare a query and a answer
cache for the given predicate, as well as a
wrapper. The current version does not yet
realize tabling of non-wellfounded recursion.

- Hash Indexes:
The tabling does not use a table space separate
from the dynamic database, instead the caches
are realized through dynamic predicates. To
profit even more from our ground term sharing,
we now offer pre-computed hash indexes. For
large ground terms, the tabling mechanism
can then exhibit emergent local interning.

- Rubber Band:
The format/[2,3] predicates got a facelift and
we now support the rubber band ~`Ct and the
column margin ~N|. The challenge was to keep
the streaming behaviour, which we could keep
for the first rubber band separated segment.
A further challenge was scattering character
richtext, which the format specifiers
~defgq can produce.

Have Fun!

Jan Burse, https://www.herbrand.ai/ , 01.05.2026

[toc] | [next] | [standalone]

#53762

Just testing follow up.

On 1 May 2026, Mild Shock wrote
(in article <10t361t$18chr$3@solani.org>):

> Dear All,
>
> We are happy to announce a new edition
> of the Dogelog Player:
>
> - Tabling Directive:
> It turns out that our term expansion is fit
> enough to provide a tabling directive table/1.
> The directive will prepare a query and a answer
> cache for the given predicate, as well as a
> wrapper. The current version does not yet
> realize tabling of non-wellfounded recursion.
>
> - Hash Indexes:
> The tabling does not use a table space separate
> from the dynamic database, instead the caches
> are realized through dynamic predicates. To
> profit even more from our ground term sharing,
> we now offer pre-computed hash indexes. For
> large ground terms, the tabling mechanism
> can then exhibit emergent local interning.
>
> - Rubber Band:
> The format/[2,3] predicates got a facelift and
> we now support the rubber band ~`Ct and the
> column margin ~N|. The challenge was to keep
> the streaming behaviour, which we could keep
> for the first rubber band separated segment.
> A further challenge was scattering character
> richtext, which the format specifiers
> > defgq can produce.
>
> Have Fun!
>
> Jan Burse, https://www.herbrand.ai/ , 01.05.2026

[toc] | [prev] | [next] | [standalone]

#53763 — Dogelog Player on a A18 Everest (Re: ANN: Dogelog Player 2.2.2 (Unified Tabling))

Hi,

Dogelog Player is a Prolog system for JavaScript,
Python and Java targets. It has still some macOS
genes, since couple of years ago our development
environment featured a Mac Book. We recently did
a cross testing exercise for Dogelog Player on
a brand new Mac Neo.

In our Zoo of AI laptops we had to rank the Mac
Neo third. Still the Mac Neo, a beautifully silent
and affordable product, excells for example in
JavaScript and clearly leaves behind the other
Think ARM machine, since we couldn’t find a PyPy
Windows ARM build.

See also:

Dogelog Player on a A18 Everest
https://medium.com/2989/80bae0494236

Mild Shock schrieb:
> Dear All,
> 
> We are happy to announce a new edition
> of the Dogelog Player:
> 
> - Tabling Directive:
> It turns out that our term expansion is fit
> enough to provide a tabling directive table/1.
> The directive will prepare a query and a answer
> cache for the given predicate, as well as a
> wrapper. The current version does not yet
> realize tabling of non-wellfounded recursion.
> 
> - Hash Indexes:
> The tabling does not use a table space separate
> from the dynamic database, instead the caches
> are realized through dynamic predicates. To
> profit even more from our ground term sharing,
> we now offer pre-computed hash indexes. For
> large ground terms, the tabling mechanism
> can then exhibit emergent local interning.
> 
> - Rubber Band:
> The format/[2,3] predicates got a facelift and
> we now support the rubber band ~`Ct and the
> column margin ~N|. The challenge was to keep
> the streaming behaviour, which we could keep
> for the first rubber band separated segment.
> A further challenge was scattering character
> richtext, which the format specifiers
> ~defgq can produce.
> 
> Have Fun!
> 
> Jan Burse, https://www.herbrand.ai/ , 01.05.2026

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.java.programmer

csiph-web