Prolog Necronomicon: Write an Interactive Debugger! (Re: ANN: Dogelog Player 1.3.3 (Dark Mode))

We recently started porting formerly Jekejeke
Prolog to the 100% Prolog Novacore from Dogelog
Player. The current state is that formerly Jekejeke
Prolog is now 50% Prolog, and we are continuing
the transformation.

Formerly Jekejeke Prolog did have a natively
written Interactive Debugger. Dogelog Player
does not yet have an Interactive Debugger. So we
started an experiment of writing a non-native
Interactive Debugger.

Our pathological examination of formerly Jekejeke
Prolog lead to an Internative Debugger that can
handle cuts, but that is also smart enough to
switch from 4-Port model to 2-Port model. We will
mostlikely ship it, despite some loose ends like
hiding system and library details.

See also:

Prolog Necronomicon: Write an Interactive Debugger!
https://qiita.com/j4n_bur53/items/909e114b8362ab9f3545


Mild Shock schrieb:
> 
> Dogelog Player is a Prolog system that is written
> in 100% Prolog. Formerly Jekejeke Prolog was a
> Prolog system that was written in 100% Java. We
> created a new version of Jekejeke Prolog that
> has 50% Prolog from Dogelog Player and is
> still multi-threaded.
> 
> We trashed everything beyond the core of Jekejeke
> Prolog and adopted the Dogelog Player libraries
> and top-level, even library(markup) works! The
> new Jekejeke Prolog is significantly slower than
> Dogelog Player, almost a factor two. But it can still
> serve for some cherry picking.
> 
> See also:
> 
> Dogelog Player goes Multi Threading
> https://medium.com/@janburse_2989/6720695470fe
>