|Did you know ...||Search Documentation:|
|Coroutining using Prolog engines|
Where the term coroutine in Prolog typically refer to hooks triggered by attributed variables (section 7.1), SWI-Prolog provides two other forms of coroutines. Delimited continuations (see section 4.10) allow creating coroutines that run in the same Prolog engine by capturing and restarting the continuation. This section discusses engines, also known as interactors. The idea was pinned by Paul Tarau Tarau, 2011. The API described in this chapter has been established together with Paul Tarau and Paulo Moura.
Engines are closely related to threads (section
9). An engine is a Prolog virtual machine that has its own stacks
and (virtual) machine state. Unlike normal Prolog threads though, they
are not associated with an operating system thread. Instead, you ask
an engine for a next answer (engine_next/2).
Asking an engine for the next answer attaches the engine to the calling
operating system thread and cause it to run until the engine calls engine_yield/1
or its associated goal completes with an answer, failure or an
exception. After the engine yields or completes, it is detached from the
operating system thread and the answer term is made available to the
calling thread. Communicating with an engine is similar to communicating
with a Prolog system though the terminal. In this sense engines are
related to Pengines as provided by library
but where Pengines aim primarily at accessing Prolog engines through the
network, engines are in-process entities.