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

Groups > comp.lang.prolog > #13992

Re: Request for comments, coroutines and workers ISO core standard

Show all headers | View raw

We still keep formerly Jekejeke Prolog on current
so that it has functionality to emulate Dogelog Player.
Now we have hit a spot, where we must rework it,

so that it also features task contexts. Interestingly
as a result this will also go down the drain.

Logic Engines as Interactors
Paul Tarau - 5 Aug 2008
https://arxiv.org/abs/0808.0556

The paper had lasting impact on SWI-Prolog, in that
they have an engines library. The impact on Jekejeke Prolog
was not that big. We demonstrated how to make an

interleaved call of an interpreters spun from an
interpreter. This was done by handcoding Java.
No engines library made it into our runtime library.

So in favor of coroutines we will discontinue
some designs that allowed piggy packed interpreters.
Besides that we expect that through channels,

- create_channel:
   Will create an async channel for coroutine
   communication. Thats the replacement of messages
   queues from the threads world.

we can redo engines in case this would be needed.
We expect an emergent effect of synchronizity
since these channels just like coroutines,

should also work when single threaded.

Back to comp.lang.prolog | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Request for comments, coroutines and workers ISO core standard Mild Shock <janburse@fastmail.fm> - 2024-02-23 13:58 +0100
  Re: Request for comments, coroutines and workers ISO core standard Mild Shock <janburse@fastmail.fm> - 2024-02-23 14:17 +0100
    Re: Request for comments, coroutines and workers ISO core standard Mild Shock <janburse@fastmail.fm> - 2024-02-23 19:16 +0100

csiph-web