Did you know ... Search Documentation:
Predicate pengine_event_loop/2
Availability::- use_module(library(pengines)).(can be autoloaded)
Source[det]pengine_event_loop(:Closure, +Options)
Starts an event loop accepting event terms sent to the current pengine or thread. For each such event E, calls ignore(call(Closure, E)). A closure thus acts as a handler for the event. Some events are also treated specially:
create(ID, Term)
The ID is placed in a list of active pengines.
destroy(ID)
The ID is removed from the list of active pengines. When the last pengine ID is removed, the loop terminates.
output(ID, Term)
The predicate pengine_pull_response/2 is called.

Valid options are:

autoforward(+To)
Forwards received event terms to slaves. To is either all, all_but_sender or a Prolog list of NameOrIDs. [not yet implemented]
Tags are associated to your profile if you are logged in|Report abuse
Tags:
  • doc-needs-help
LogicalCaptain said (2020-01-26T10:53:02):0 upvotes 0 0 downvotes
Picture of user LogicalCaptain.

See also

ignore/1: Calls Goal as once/1, but succeeds, regardless of whether Goal succeeded or not.

"Closure"

"Closure" here is a bit misleading. It's just a "Goal" (necessarily atomic, as call/2 is used, so an "Event Handler Predicate"). There is no "code to be executed" in a context that was in existence when that code was wrapped into an object.

See also: https://www.swi-prolog.org/pldoc/doc_for?object=call/2