Hook objects (i.e. objects that define term- and goal-expansion rules)
can be combined to define expansion workflows. While in some cases the
expansions are independent and thus can be applied in any order, in
other cases a specific order is required. The
hook_set parametric objects in this library implement the two most
common scenarios of combining multiple hook objects for the expansion of
source files. These parametric hook objects can be combined to define
workflows of any complexity (e.g. a pipeline where one of the steps is
set with an element that is a pipeline). These two basic hook flows can
also used as examples of how to construct your own custom expansion
Open the ../../docs/library_index.html#hook-flows link in a web browser.
To load all entities in this library, load the
| ?- logtalk_load(hook_flows(loader)).
To test this library predicates, load the
| ?- logtalk_load(hook_flows(tester)).
Pre-processing a source file with a hook object can be accomplished by
either compiling the source file using the option
or by adding to the top of the file the directive:
:- set_logtalk_flag(hook, HookObject).
set_logtalk_flag/2 directives are local to a source file.
hook_pipeline(Pipeline) is a parametric object where the
parameter is a list of hook objects, interpreted as a pre-processing
pipeline: the results of a hook object are passed to the next hook
object. This parametric object is used when the expansions must be
applied in a specific order. It also allows overriding the default
compiler semantics where term-expansion rules are tried in sequence only
until one of them succeeds.
hook_set(Set) is a parametric object where the parameter is a
list of hook objects, interpreted as a set of hook objects. For
term-expansion, hooks in the set are tried until one of them succeeds.
For goal-expansion, as the compiler expands a goal until a fixed-point
is reached, all the hooks objects in the set that are applicable at any
point will be used. This parametric object is used when applying
multiple independent expansions.
When using a backend Prolog compiler that supports modules, it’s also possible to use as parameter a list of hook modules as long as their names do not coincide with the names of loaded objects.