# YAP User’s Manual

### Version 6.2.2

Vítor Santos Costa,
Luís Damas,
Rogério Reis, and
Rúben Azevedo

Copyright © 1989-2000 L. Damas, V. Santos Costa and Universidade do Porto.

Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies.

Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.

Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions.

# Table of Contents

- Introduction
- 1 Installing YAP
  - 1.1 Tuning the Functionality of YAP
  - 1.2 Tuning YAP for a Particular Machine and Compiler
  - 1.3 Tuning YAP for `GCC`.
    - 1.3.1 Compiling Under Visual C++
    - 1.3.2 Compiling Under SGI’s cc
- 2 Running YAP
  - 2.1 Running YAP Interactively
  - 2.2 Running Prolog Files
- 3 Syntax
  - 3.1 Syntax of Terms
  - 3.2 Prolog Tokens
    - 3.2.1 Numbers
      - 3.2.1.1 Integers
      - 3.2.1.2 Floating-point Numbers
    - 3.2.2 Character Strings
    - 3.2.3 Atoms
    - 3.2.4 Variables
    - 3.2.5 Punctuation Tokens
    - 3.2.6 Layout
  - 3.3 Wide Character Support
    - 3.3.1 Wide character encodings on streams
    - 3.3.2 BOM: Byte Order Mark
- 4 Loading Programs
  - 4.1 Program loading and updating
  - 4.2 Changing the Compiler’s Behavior
  - 4.3 Conditional Compilation
  - 4.4 Saving and Loading Prolog States
- 5 The Module System
  - 5.1 Module Concepts
  - 5.2 Defining a New Module
  - 5.3 Using Modules
  - 5.4 Meta-Predicates in Modules
  - 5.5 Re-Exporting Predicates From Other Modules
- 6 Built-In Predicates
  - 6.1 Control Predicates
  - 6.2 Handling Undefined Procedures
  - 6.3 Message Handling
  - 6.4 Predicates on terms
  - 6.5 Predicates on Atoms
  - 6.6 Predicates on Characters
  - 6.7 Comparing Terms
  - 6.8 Arithmetic
  - 6.9 I/O Predicates
    - 6.9.1 Handling Streams and Files
    - 6.9.2 Handling Streams and Files
    - 6.9.3 Handling Input/Output of Terms
    - 6.9.4 Handling Input/Output of Characters
    - 6.9.5 Input/Output Predicates applied to Streams
    - 6.9.6 Compatible C-Prolog predicates for Terminal I/O
    - 6.9.7 Controlling Input/Output
    - 6.9.8 Using Sockets From YAP
  - 6.10 Using the Clausal Data Base
    - 6.10.1 Modification of the Data Base
    - 6.10.2 Looking at the Data Base
    - 6.10.3 Using Data Base References
  - 6.11 Internal Data Base
  - 6.12 The Blackboard
  - 6.13 Collecting Solutions to a Goal
  - 6.14 Grammar Rules
  - 6.15 Access to Operating System Functionality
  - 6.16 Term Modification
  - 6.17 Global Variables
  - 6.18 Profiling Prolog Programs
    - 6.18.1 The Count Profiler
    - 6.18.2 Tick Profiler
  - 6.19 Counting Calls
  - 6.20 Arrays
  - 6.21 Predicate Information
  - 6.22 Miscellaneous
- 7 Library Predicates
  - 7.1 Aggregate
  - 7.2 Apply Macros
  - 7.3 Association Lists
  - 7.4 AVL Trees
  - 7.5 Heaps
  - 7.6 List Manipulation
  - 7.7 Line Manipulation Utilities
  - 7.8 Maplist
  - 7.9 Matrix Library
  - 7.10 MATLAB Package Interface
  - 7.11 Non-Backtrackable Data Structures
  - 7.12 Ordered Sets
  - 7.13 Pseudo Random Number Integer Generator
  - 7.14 Queues
  - 7.15 Random Number Generator
  - 7.16 Read Utilities
  - 7.17 Red-Black Trees
  - 7.18 Regular Expressions
  - 7.19 SWI-Prolog’s shlib library
  - 7.20 Splay Trees
  - 7.21 Reading From and Writing To Strings
  - 7.22 Calling The Operating System from YAP
  - 7.23 Utilities On Terms
  - 7.24 Trie DataStructure
  - 7.25 Call Cleanup
  - 7.26 Calls With Timeout
  - 7.27 Updatable Binary Trees
  - 7.28 Unweighted Graphs
  - 7.29 Directed Graphs
  - 7.30 Undirected Graphs
  - 7.31 Lambda Expressions
  - 7.32 LAM
  - 7.33 Block Diagram
- 8 SWI-Prolog Emulation
  - 8.1 Invoking Predicates on all Members of a List
  - 8.2 Forall
- 9 SWI Global variables
  - 9.1 Compatibility of Global Variables
- 10 Extensions to Prolog
  - 10.1 Rational Trees
  - 10.2 Co-routining
- 11 Attributed Variables
  - 11.1 hProlog and SWI-Prolog style Attribute Declarations
  - 11.2 SICStus Prolog style Attribute Declarations
    - 11.2.1 Attribute Declarations
    - 11.2.2 Attribute Manipulation
    - 11.2.3 Attributed Unification
    - 11.2.4 Displaying Attributes
    - 11.2.5 Projecting Attributes
    - 11.2.6 Attribute Examples
- 12 Constraint Logic Programming over Reals
  - 12.1 Solver Predicates
  - 12.2 Syntax of the predicate arguments
  - 12.3 Use of unification
  - 12.4 Non-Linear Constraints
- 13 CHR: Constraint Handling Rules
  - 13.1 Introduction
  - 13.2 Syntax and Semantics
    - 13.2.1 Syntax
    - 13.2.2 Semantics
      - Rule Types
      - Rule Names
      - Pragmas
      - Options
  - 13.3 CHR in YAP Programs
    - 13.3.1 Embedding in Prolog Programs
    - 13.3.2 Constraint declaration
    - 13.3.3 Compilation
  - 13.4 Debugging
    - 13.4.1 Ports
    - 13.4.2 Tracing
    - 13.4.3 CHR Debugging Predicates
  - 13.5 Examples
  - 13.6 Compatibility with SICStus CHR
  - 13.7 Guidelines
- 14 Logtalk
- 15 MYDDAS
  - 15.1 Requirements and Installation Guide
  - 15.2 MYDDAS Architecture
  - 15.3 Loading MYDDAS
  - 15.4 Connecting to and disconnecting from a Database Server
  - 15.5 Accessing a Relation
  - 15.6 View Level Interface
  - 15.7 Accessing Tables in Data Sources Using SQL
  - 15.8 Insertion of Rows
  - 15.9 Types of Attributes
  - 15.10 Number of Fields
  - 15.11 Describing a Relation
  - 15.12 Enumeration Relations
  - 15.13 The MYDDAS MySQL Top Level
  - 15.14 Other MYDDAS Properties
- 16 Threads
  - 16.1 Creating and Destroying Prolog Threads
  - 16.2 Monitoring Threads
  - 16.3 Thread communication
    - 16.3.1 Message Queues
    - 16.3.2 Signalling Threads
    - 16.3.3 Threads and Dynamic Predicates
  - 16.4 Thread Synchronisation
- 17 Parallelism
- 18 Tabling
- 19 Tracing at Low Level
- 20 Profiling the Abstract Machine
- 21 Debugging
  - 21.1 Debugging Predicates
  - 21.2 Interacting with the debugger
- 22 Efficiency Considerations
  - 22.1 Deterministic Programs
  - 22.2 Non-Deterministic Programs
  - 22.3 Data-Base Operations
  - 22.4 Indexing
  - 22.5 Profiling
- 23 C Language interface to YAP
  - 23.1 Terms
  - 23.2 Unification
  - 23.3 Strings
  - 23.4 Memory Allocation
  - 23.5 Controlling YAP Streams from `C`
  - 23.6 Utility Functions in `C`
  - 23.7 From `C` back to Prolog
  - 23.8 Module Manipulation in C
  - 23.9 Miscellaneous C Functions
  - 23.10 Writing predicates in C
  - 23.11 Loading Object Files
  - 23.12 Saving and Restoring
  - 23.13 Changes to the C-Interface in YAP4
- 24 Using YAP as a Library
- 25 Compatibility with Other Prolog systems
  - 25.1 Compatibility with the C-Prolog interpreter
    - 25.1.1 Major Differences between YAP and C-Prolog.
    - 25.1.2 YAP predicates fully compatible with C-Prolog
    - 25.1.3 YAP predicates not strictly compatible with C-Prolog
    - 25.1.4 YAP predicates not available in C-Prolog
    - 25.1.5 YAP predicates not available in C-Prolog
  - 25.2 Compatibility with the Quintus and SICStus Prolog systems
    - 25.2.1 Major Differences between YAP and SICStus Prolog.
    - 25.2.2 YAP predicates fully compatible with SICStus Prolog
    - 25.2.3 YAP predicates not strictly compatible with SICStus Prolog
    - 25.2.4 YAP predicates not available in SICStus Prolog
  - 25.3 Compatibility with the ISO Prolog standard
- Appendix A Summary of YAP Predefined Operators
- Predicate Index
- Concept Index

[ < ] | [ > ] |  | [Contents] | [Index] | [ ? ]

# YAP Prolog

This file documents the YAP Prolog System version 6.2.2, a high-performance Prolog compiler developed at LIACC, Universidade do Porto. YAP is based on David H. D. Warren’s WAM (Warren Abstract Machine), with several optimizations for better performance. YAP follows the Edinburgh tradition, and is largely compatible with DEC-10 Prolog, Quintus Prolog, and especially with C-Prolog.

This file contains extracts of the SWI-Prolog manual, as written by Jan Wielemaker. Our thanks to the author for his kind permission in allowing us to include his text in this document.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# Introduction

This document provides User information on version 6.2.2 of YAP (Yet Another Prolog). The YAP Prolog System is a high-performance Prolog compiler developed at LIACC, Universidade do Porto. YAP provides several important features:

- Speed: YAP is widely considered one of the fastest available Prolog systems.
- Functionality: it supports stream I/O, sockets, modules, exceptions, Prolog debugger, C-interface, dynamic code, internal database, DCGs, saved states, co-routining, arrays, threads.
- We explicitly allow both commercial and non-commercial use of YAP.

YAP is based on the David H. D. Warren’s WAM (Warren Abstract Machine), with several optimizations for better performance. YAP follows the Edinburgh tradition, and was originally designed to be largely compatible with DEC-10 Prolog, Quintus Prolog, and especially with C-Prolog.

YAP implements most of the ISO-Prolog standard. We are striving at full compatibility, and the manual describes what is still missing. The manual also includes a (largely incomplete) comparison with SICStus Prolog.

The document is intended neither as an introduction to Prolog nor to the implementation aspects of the compiler. A good introduction to programming in Prolog is the book The Art of Prolog, by L. Sterling and E. Shapiro, published by "The MIT Press, Cambridge MA". Other references should include the classical Programming in Prolog, by W.F. Clocksin and C.S. Mellish, published by Springer-Verlag.

YAP 4.3 is known to build with many versions of gcc (<= gcc-2.7.2, >= gcc-2.8.1, >= egcs-1.0.1, gcc-2.95.*) and on a variety of Unixen: SunOS 4.1, Solaris 2.*, Irix 5.2, HP-UX 10, Dec Alpha Unix, Linux 1.2 and Linux 2.* (RedHat 4.0 thru 5.2, Debian 2.*) in both the x86 and alpha platforms. It has been built on Windows NT 4.0 using Cygwin from Cygnus Solutions (see README.nt) and using Visual C++ 6.0.

The overall copyright and permission notice for YAP4.3 can be found in the Artistic file in this directory. YAP follows the Perl Artistic license, and it is thus non-copylefted freeware.

If you have a question about this software, desire to add code, found a bug, want to request a feature, or wonder how to get further assistance, please send e-mail to yap-users AT lists.sourceforge.net. To subscribe to the mailing list, visit the page https://lists.sourceforge.net/lists/listinfo/yap-users.

On-line documentation is available for YAP at:

http://www.ncc.up.pt/~vsc/YAP/

Recent versions of YAP, including both source and selected binaries, can be found from this same URL.

This manual was written by Vítor Santos Costa, Luís Damas, Rogério Reis, and Rúben Azevedo. The manual is largely based on the DECsystem-10 Prolog User’s Manual by D.L. Bowen, L. Byrd, F. C. N. Pereira, L. M. Pereira, and D. H. D. Warren. We have also used comments from the Edinburgh Prolog library written by R. O’Keefe. We would also like to gratefully acknowledge the contributions from Ashwin Srinivasian.

We are happy to include in YAP several excellent packages developed under separate licenses. Our thanks to the authors for their kind authorization to include these packages.

The packages are, in alphabetical order:

- The CHR package developed by Tom Schrijvers, Christian Holzbaur, and Jan Wielemaker.
- The CLP(R) package developed by Leslie De Koninck, Bart Demoen, Tom Schrijvers, and Jan Wielemaker, based on the CLP(Q,R) implementation by Christian Holzbaur.
- The Logtalk Object-Oriented system is developed at the University of Beira Interior, Portugal, by Paulo Moura:

  http://logtalk.org/

  Logtalk is no longer distributed with YAP. Please use the Logtalk standalone installer for a smooth integration with YAP.

- The Pillow WEB library developed at Universidad Politecnica de Madrid by the CLIP group. This package is distributed under the FSF’s LGPL. Documentation on this package is distributed separately from yap.tex.
- The `yap2swi` library implements some of the functionality of SWI’s PL interface. Please do refer to the SWI-Prolog home page:

  http://www.swi-prolog.org

  for more information on SWI-Prolog and for a detailed description of its foreign language interface.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 1 Installing YAP

To compile YAP it should be sufficient to:

1. `mkdir ARCH`.
2. `cd ARCH`.
3. `../configure ...options...`.

   Notice that by default `configure` gives you a vanilla configuration. For instance, in order to use co-routining and/or CLP you need to do

       ../configure --enable-coroutining ...options...

   Please see section Tuning the Functionality of YAP for extra options.

4. check the Makefile for any extensions or changes you want to make.

   YAP uses `autoconf`. Recent versions of YAP try to follow GNU conventions on where to place software.

   - The main executable is placed at `BINDIR`. This executable is actually a script that calls the Prolog engine, stored at `LIBDIR`.
   - `LIBDIR` is the directory where libraries are stored. YAPLIBDIR is a subdirectory that contains the Prolog engine and a Prolog library.
   - `INCLUDEDIR` is used if you want to use YAP as a library.
   - `INFODIR` is where to store `info` files. Usually `/usr/local/info`, `/usr/info`, or `/usr/share/info`.
5. `make`.
6. If the compilation succeeds, try `./yap`.
7. If you feel satisfied with the result, do `make install`.
8. `make install-info` will create the info files in the standard info directory.
9. `make html` will create documentation in html format in the predefined directory.

   In most systems you will need to be superuser in order to do `make install` and `make info` on the standard directories.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 1.1 Tuning the Functionality of YAP

Compiling YAP with the standard options give you a plain vanilla Prolog. You can tune YAP to include extra functionality by calling `configure` with the appropriate options:

- `--enable-rational-trees=yes` gives you support for infinite rational trees.
- `--enable-coroutining=yes` gives you support for coroutining, including freezing of goals, attributed variables, and constraints. This will also enable support for infinite rational trees.
- `--enable-depth-limit=yes` allows depth limited evaluation, say for implementing iterative deepening.
- `--enable-low-level-tracer=yes` allows support for tracing all calls, retries, and backtracks in the system. This can help in debugging your application, but results in performance loss.
- `--enable-wam-profile=yes` allows profiling of abstract machine instructions. This is useful when developing YAP, should not be so useful for normal users.
- `--enable-condor=yes` allows using the Condor system that support High Throughput Computing (HTC) on large collections of distributively owned computing resources.
- `--enable-tabling=yes` allows tabling support. This option is still experimental.
- `--enable-parallelism={env-copy,sba,a-cow}` allows or-parallelism supported by one of these three forms. This option is still highly experimental.
- `--with-max-workers` allows definition of the maximum number of parallel processes (its value can be consulted at runtime using the flag `max_workers`).
- `--with-gmp[=DIR]` give a path to where one can find the `GMP` library if not installed in the default path.
- `--enable-threads` allows using of the multi-threading predicates provided by YAP. Depending on the operating system, the option `--enable-pthread-locking` may also need to be used.
- `--with-max-threads` allows definition of the maximum number of threads (the default value is 1024; its value can be consulted at runtime using the flag `max_threads`).

Next section discusses machine dependent details.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 1.2 Tuning YAP for a Particular Machine and Compiler

The default options should give you best performance under `GCC`. Although the system is tuned for this compiler we have been able to compile versions of YAP under lcc in Linux, Sun’s cc compiler, IBM’s xlc, SGI’s cc, and Microsoft’s Visual C++ 6.0.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 1.3 Tuning YAP for `GCC`.

YAP has been developed to take advantage of `GCC` (but not to depend on it). The major advantage of `GCC` is threaded code and explicit register reservation.

YAP is set by default to compile with the best compilation flags we know. Even so, a few specific options reduce portability. The option

- `--enable-max-performance=yes` will try to support the best available flags for a specific architectural model. Currently, the option assumes a recent version of `GCC`.
- `--enable-debug-yap` compiles YAP so that it can be debugged by tools such as `dbx` or `gdb`.

Here follow a few hints:

On x86 machines the flags:

    YAP_EXTRAS= ... -DBP_FREE=1

tells us to use the `%bp` register (frame-pointer) as the emulator’s program counter. This seems to be stable and is now default.

On Sparc/Solaris2 use:

    YAP_EXTRAS= ...   -mno-app-regs -DOPTIMISE_ALL_REGS_FOR_SPARC=1

and YAP will get two extra registers! This trick does not work on SunOS 4 machines.

Note that versions of GCC can be tweaked to recognize different processors within the same instruction set, e.g. 486, Pentium, and PentiumPro for the x86; or Ultrasparc, and Supersparc for Sparc. Unfortunately, some of these tweaks do may make YAP run slower or not at all in other machines with the same instruction set, so they cannot be made default.

Last, the best options also depends on the version of GCC you are using, and it is a good idea to consult the GCC manual under the menus "Invoking GCC"/"Submodel Options". Specifically, you should check `-march=XXX` for recent versions of GCC/EGCS. In the case of `GCC2.7` and other recent versions of `GCC` you can check:

`486:`

  In order to take advantage of 486 specific optimizations in GCC 2.7.*:

      YAP_EXTRAS= ... -m486 -DBP_FREE=1

`Pentium:`

      YAP_EXTRAS= ... -m486 -malign-loops=2 -malign-jumps=2 \
                            -malign-functions=2

`PentiumPro and other recent Intel and AMD machines:`

  PentiumPros are known not to require alignment. Check your version of `GCC` for the best `-march` option.

`Super and UltraSparcs:`

      YAP_EXTRAS= ... -msupersparc

`MIPS: if have a recent machine and you need a 64 bit wide address`

  space you can use the abi 64 bits or eabi option, as in:

      CC="gcc -mabi=64" ./configure --...

  Be careful. At least for some versions of `GCC`, compiling with `-g` seems to result in broken code.

`WIN32: GCC is distributed in the MINGW32 and CYGWIN packages.`

  The Mingw32 environment is available from the URL:

  `http://www.mingw.org`

  You will need to install the `msys` and `mingw` packages. You should be able to do configure, make and make install.

  If you use mingw32 you may want to search the contributed packages for the `gmp` multi-precision arithmetic library. If you do setup YAP with `gmp` note that `libgmp.dll` must be in the path, otherwise YAP will not be able to execute.

  CygWin environment is available from the URL:

  `http://www.cygwin.com`

  and mirrors. We suggest using recent versions of the cygwin shell. The compilation steps under the cygwin shell are as follows:

      mkdir cyg
      $YAPSRC/configure --enable-coroutining \\
                        --enable-depth-limit \\
                        --enable-max-performance
      make
      make install

  By default, YAP will use the `-mno-cygwin` option to disable the use of the cygwin dll and to enable the mingw32 subsystem instead. YAP thus will not need the cygwin dll. It instead accesses the system’s `CRTDLL.DLL` `C` run time library supplied with Win32 platforms through the mingw32 interface. Note that some older WIN95 systems may not have `CRTDLL.DLL`, in this case it should be sufficient to import the file from a newer WIN95 or WIN98 machine.

  You should check the default installation path which is set to `/YAP` in the standard Makefile. This string will usually be expanded into `c:\YAP` by Windows.

  The cygwin environment does not provide `gmp` on the MINGW subsystem. You can fetch a dll for the `gmp` library from http://www.sf.net/projects/mingwrep.

  It is also possible to configure YAP to be a part of the cygwin environment. In this case you should use:

      mkdir cyg
      $YAPSRC/configure --enable-max-performance \\
                        --enable-cygwin=yes
      make
      make install

  YAP will then compile using the cygwin library and will be installed in cygwin’s `/usr/local`. You can use YAP from a cygwin console, or as a standalone application as long as it can find `cygwin1.dll` in its path. Note that you may use to use `--enable-depth-limit` for Aleph compatibility, and that you may want to be sure that GMP is installed.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 1.3.1 Compiling Under Visual C++

YAP compiles cleanly under Microsoft’s Visual C++ release 6.0. We next give a step-by-step tutorial on how to compile YAP manually using this environment.

First, it is a good idea to build YAP as a DLL:

1. create a project named yapdll using File.New. The project will be a DLL project, initially empty.

   Notice that either the project is named yapdll or you must replace the preprocessors variable YAPDLL_EXPORTS to match your project names in the files `YAPInterface.h` and `c_interface.c`.

2. add all .c files in the $YAPSRC/C directory and in the $YAPSRC\OPTYAP directory to the Project’s `Source Files` (use FileView).
3. add all .h files in the $YAPSRC/H directory, $YAPSRC\include directory and in the $YAPSRC\OPTYAP subdirectory to the Project’s `Header Files`.
4. Ideally, you should now use `m4` to generate extra .h from .m4 files and use `configure` to create a `config.h`. Or, you can be lazy, and fetch these files from $YAPSRC\VC\include.
5. You may want to go to `Build.Set Active Configuration` and set `Project Type` to `Release`
6. To use YAP’s own include directories you have to set the Project option `Project.Project Settings.C/C++.Preprocessor.Additional Include Directories` to include the directories $YAPSRC\H, $YAPSRC\VC\include, $YAPSRC\OPTYAP and $YAPSRC\include. The syntax is:

       $YAPSRC\H, $YAPSRC\VC\include, $YAPSRC\OPTYAP, $YAPSRC\include

7. Build: the system should generate an `yapdll.dll` and an `yapdll.lib`.
8. Copy the file `yapdll.dll` to your path. The file `yapdll.lib` should also be copied to a location where the linker can find it.

Now you are ready to create a console interface for YAP:

1. create a second project say `wyap` with `File.New`. The project will be a WIN32 console project, initially empty.
2. add $YAPSRC\console\yap.c to the `Source Files`.
3. add $YAPSRC\VC\include\config.h and the files in $YAPSRC\include to the `Header Files`.
4. You may want to go to `Build.Set Active Configuration` and set `Project Type` to `Release`.
5. you will eventually need to bootstrap the system by booting from `boot.yap`, so write:

               -b $YAPSRC\pl\boot.yap

   in `Project.Project Settings.Debug.Program Arguments`.

6. You need the sockets and yap libraries. Add

       ws2_32.lib yapdll.lib to

   to

   to `Project.Project Settings.Link.Object/Library Modules`

   You may also need to set the `Link Path` so that VC++ will find `yapdll.lib`.

7. set `Project.Project Settings.C/C++.Preprocessor.Additional Include Directories` to include the $YAPSRC/VC/include and $YAPSRC/include.

   The syntax is:

       $YAPSRC\VC\include, $YAPSRC\include

8. Build the system.
9. Use `Build.Start Debug` to boot the system, and then create the saved state with

       ['$YAPSRC\\pl\\init'].
       save_program('startup.yss').
       ^Z

   That’s it, you’ve got YAP and the saved state!

The $YAPSRC\VC directory has the make files to build YAP4.3.17 under VC++ 6.0.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 1.3.2 Compiling Under SGI’s cc

YAP should compile under the Silicon Graphic’s `cc` compiler, although we advise using the GNUCC compiler, if available.

`64 bit`

  Support for 64 bits should work by using (under Bourne shell syntax):

      CC="cc -64" $YAP_SRC_PATH/configure --...

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 2 Running YAP

We next describe how to invoke YAP in Unix systems.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 2.1 Running YAP Interactively

Most often you will want to use YAP in interactive mode. Assuming that YAP is in the user’s search path, the top-level can be invoked under Unix with the following command:

    yap [-s n] [-h n] [-a n] [-c IP_HOST port ] [filename]

All the arguments and flags are optional and have the following meaning:

`-?`

  print a short error message.

`-sSize`

  allocate Size K bytes for local and global stacks. The user may specify `M` bytes.

`-hSize`

  allocate Size K bytes for heap and auxiliary stacks

`-tSize`

  allocate Size K bytes for the trail stack

`-LSize`

  SWI-compatible option to allocate Size K bytes for local and global stacks, the local stack cannot be expanded. To avoid confusion with the load option, Size must immediately follow the letter `L`.

`-GSize`

  SWI-compatible option to allocate Size K bytes for local and global stacks; the global stack cannot be expanded

`-TSize`

  SWI-compatible option to allocate Size K bytes for the trail stack; the trail cannot be expanded.

`-l YAP_FILE`

  compile the Prolog file YAP_FILE before entering the top-level.

`-L YAP_FILE`

  compile the Prolog file YAP_FILE and then halt. This option is useful for implementing scripts.

`-g Goal`

  run the goal Goal before top-level. The goal is converted from an atom to a Prolog term.

`-z Goal`

  run the goal Goal as top-level. The goal is converted from an atom to a Prolog term.

`-b BOOT_FILE`

  boot code is in Prolog file BOOT_FILE. The filename must define the predicate `'$live'/0`.

`-c `IP_HOST` `port``

  connect standard streams to host `IP_HOST` at port `port`

`filename`

  restore state saved in the given file

`-f`

  do not consult initial files

`-q`

  do not print informational messages

`--`

  separator for arguments to Prolog code. These arguments are visible through the `unix/1` built-in predicate.

Note that YAP will output an error message on the following conditions:

- a file name was given but the file does not exist or is not a saved YAP state;
- the necessary amount of memory could not be allocated;
- the allocated memory is not enough to restore the state.

When restoring a saved state, YAP will allocate the same amount of memory as that in use when the state was saved, unless a different amount is specified by flags in the command line. By default, YAP restores the file ‘`startup.yss`’ from the current directory or from the YAP library.

- YAP usually boots from a saved state. The saved state will use the default installation directory to search for the YAP binary unless you define the environment variable YAPBINDIR.
- YAP always tries to find saved states from the current directory first. If it cannot it will use the environment variable YAPLIBDIR, if defined, or search the default library directory.
- YAP will try to find library files from the YAPSHAREDIR/library directory.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 2.2 Running Prolog Files

YAP can also be used to run Prolog files as scripts, at least in Unix-like environments. A simple example is shown next (do not forget that the shell comments are very important):

    #!/usr/local/bin/yap -L --
    #
    # Hello World script file using YAP
    #
    # put a dot because of syntax errors .

    :- write('Hello World'), nl.

The `#!` characters specify that the script should call the binary file YAP. Notice that many systems will require the complete path to the YAP binary. The `-L` flag indicates that YAP should consult the current file when booting and then halt. The remaining arguments are then passed to YAP. Note that YAP will skip the first lines if they start with `#` (the comment sign for Unix’s shell). YAP will consult the file and execute any commands.

A slightly more sophisticated example is:

    #!/usr/bin/yap -L --
    #
    # Hello World script file using YAP
    # .

    :- initialization(main).

    main :- write('Hello World'), nl.

The `initialization` directive tells YAP to execute the goal main after consulting the file. Source code is thus compiled and `main` executed at the end. The `.` is useful while debugging the script as a Prolog program: it guarantees that the syntax error will not propagate to the Prolog code.

Notice that the `--` is required so that the shell passes the extra arguments to YAP. As an example, consider the following script `dump_args`:

    #!/usr/bin/yap -L --
    #.

    main( [] ).
    main( [H|T] ) :-
            write( H ), nl,
            main( T ).

    :- unix( argv(AllArgs) ), main( AllArgs ).

If you this run this script with the arguments:

    ./dump_args -s 10000

the script will start an YAP process with stack size `10MB`, and the list of arguments to the process will be empty.

Often one wants to run the script as any other program, and for this it is convenient to ignore arguments to YAP. This is possible by using `L --` as in the next version of `dump_args`:

    #!/usr/bin/yap -L --

    main( [] ).
    main( [H|T] ) :-
            write( H ), nl,
            main( T ).

    :- unix( argv(AllArgs) ), main( AllArgs ).

The `--` indicates the next arguments are not for YAP. Instead, they must be sent directly to the `argv` built-in. Hence, running

    ./dump_args test

will write `test` on the standard output.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 3 Syntax

We will describe the syntax of YAP at two levels. We first will describe the syntax for Prolog terms. In a second level we describe the tokens from which Prolog terms are built.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 3.1 Syntax of Terms

Below, we describe the syntax of YAP terms from the different classes of tokens defined above. The formalism used will be BNF, extended where necessary with attributes denoting integer precedence or operator type.

     term       ---->     subterm(1200)   end_of_term_marker

     subterm(N) ---->     term(M)         [M <= N]

     term(N)    ---->     op(N, fx) subterm(N-1)
                 |        op(N, fy) subterm(N)
                 |        subterm(N-1) op(N, xfx) subterm(N-1)
                 |        subterm(N-1) op(N, xfy) subterm(N)
                 |        subterm(N) op(N, yfx) subterm(N-1)
                 |        subterm(N-1) op(N, xf)
                 |        subterm(N) op(N, yf)

     term(0)   ---->      atom '(' arguments ')'
                 |        '(' subterm(1200)  ')'
                 |        '{' subterm(1200)  '}'
                 |        list
                 |        string
                 |        number
                 |        atom
                 |        variable

     arguments ---->      subterm(999)
                 |        subterm(999) ',' arguments

     list      ---->      '[]'
                 |        '[' list_expr ']'

     list_expr ---->      subterm(999)
                 |        subterm(999) list_tail

     list_tail ---->      ',' list_expr
                 |        ',..' subterm(999)
                 |        '|' subterm(999)

Notes:

- op(N,T) denotes an atom which has been previously declared with type T and base precedence N.
- Since ’,’ is itself a pre-declared operator with type xfy and precedence 1000, is subterm starts with a ’(’, op must be followed by a space to avoid ambiguity with the case of a functor followed by arguments, e.g.:

       + (a,b)        [the same as '+'(','(a,b)) of arity one]

  versus

       +(a,b)         [the same as '+'(a,b) of arity two]

- In the first rule for term(0) no blank space should exist between atom and ’(’.
- Each term to be read by the YAP parser must end with a single dot, followed by a blank (in the sense mentioned in the previous paragraph). When a name consisting of a single dot could be taken for the end of term marker, the ambiguity should be avoided by surrounding the dot with single quotes.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 3.2 Prolog Tokens

Prolog tokens are grouped into the following categories:

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 3.2.1 Numbers

Numbers can be further subdivided into integer and floating-point numbers.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

#### 3.2.1.1 Integers

Integer numbers are described by the following regular expression:

    <integer> := {<digit>+<single-quote>|0{xXo}}<alpha_numeric_char>+

where {...} stands for optionality, + optional repetition (one or more times), <digit> denotes one of the characters 0 ... 9, | denotes or, and <single-quote> denotes the character "’". The digits before the <single-quote> character, when present, form the number basis, that can go from 0, 1 and up to 36. Letters from `A` to `Z` are used when the basis is larger than 10.

Note that if no basis is specified then base 10 is assumed. Note also that the last digit of an integer token can not be immediately followed by one of the characters ’e’, ’E’, or ’.’.

Following the ISO standard, YAP also accepts directives of the form `0x` to represent numbers in hexadecimal base and of the form `0o` to represent numbers in octal base. For usefulness, YAP also accepts directives of the form `0X` to represent numbers in hexadecimal base.

Example: the following tokens all denote the same integer

    10  2'1010  3'101  8'12  16'a  36'a  0xa  0o12

Numbers of the form `0'a` are used to represent character constants. So, the following tokens denote the same integer:

    0'd  100

YAP (version 6.2.2) supports integers that can fit the word size of the machine. This is 32 bits in most current machines, but 64 in some others, such as the Alpha running Linux or Digital Unix. The scanner will read larger or smaller integers erroneously.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

#### 3.2.1.2 Floating-point Numbers

Floating-point numbers are described by:

       <float> := <digit>+{<dot><digit>+}
                   <exponent-marker>{<sign>}<digit>+
                |<digit>+<dot><digit>+
                   {<exponent-marker>{<sign>}<digit>+}

where <dot> denotes the decimal-point character ’.’, <exponent-marker> denotes one of ’e’ or ’E’, and <sign> denotes one of ’+’ or ’-’.

Examples:

    10.0   10e3   10e-3   3.1415e+3

Floating-point numbers are represented as a double in the target machine. This is usually a 64-bit number.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 3.2.2 Character Strings

Strings are described by the following rules:

      string --> '"' string_quoted_characters '"'

      string_quoted_characters --> '"' '"' string_quoted_characters
      string_quoted_characters --> '\'
                              escape_sequence string_quoted_characters
      string_quoted_characters -->
                              string_character string_quoted_characters

      escape_sequence --> 'a' | 'b' | 'r' | 'f' | 't' | 'n' | 'v'
      escape_sequence --> '\' | '"' | ''' | '`'
      escape_sequence --> at_most_3_octal_digit_seq_char '\'
      escape_sequence --> 'x' at_most_2_hexa_digit_seq_char '\'

where `string_character` in any character except the double quote and escape characters.

Examples:

    ""   "a string"   "a double-quote:"""

The first string is an empty string, the last string shows the use of double-quoting. The implementation of YAP represents strings as lists of integers. Since YAP 4.3.0 there is no static limit on string size.

Escape sequences can be used to include the non-printable characters `a` (alert), `b` (backspace), `r` (carriage return), `f` (form feed), `t` (horizontal tabulation), `n` (new line), and `v` (vertical tabulation). Escape sequences also be include the meta-characters `\`, `"`, `'`, and ```. Last, one can use escape sequences to include the characters either as an octal or hexadecimal number.

The next examples demonstrates the use of escape sequences in YAP:

    "\x0c\" "\01\" "\f" "\\"

The first three examples return a list including only character 12 (form feed). The last example escapes the escape character.

Escape sequences were not available in C-Prolog and in original versions of YAP up to 4.2.0. Escape sequences can be disable by using:

    :- yap_flag(character_escapes,off).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 3.2.3 Atoms

Atoms are defined by one of the following rules:

       atom --> solo-character
       atom --> lower-case-letter name-character*
       atom --> symbol-character+
       atom --> single-quote  single-quote
       atom --> ''' atom_quoted_characters '''

      atom_quoted_characters --> ''' ''' atom_quoted_characters
      atom_quoted_characters --> '\' atom_sequence string_quoted_characters
      atom_quoted_characters --> character string_quoted_characters

where:

       <solo-character>     denotes one of:    ! ;
       <symbol-character>   denotes one of:    # & * + - . / : <
                                               = > ? @ \ ^ ` ~
       <lower-case-letter>  denotes one of:    a...z
       <name-character>     denotes one of:    _ a...z A...Z 0....9
       <single-quote>       denotes:           '

and `string_character` denotes any character except the double quote and escape characters. Note that escape sequences in strings and atoms follow the same rules.

Examples:

    a   a12x   '$a'   !   =>  '1 2'

Version `4.2.0` of YAP removed the previous limit of 256 characters on an atom. Size of an atom is now only limited by the space available in the system.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 3.2.4 Variables

Variables are described by:

       <variable-starter><variable-character>+

where

      <variable-starter>   denotes one of:    _ A...Z
      <variable-character> denotes one of:    _ a...z A...Z

If a variable is referred only once in a term, it needs not to be named and one can use the character `_` to represent the variable. These variables are known as anonymous variables. Note that different occurrences of `_` on the same term represent different anonymous variables.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 3.2.5 Punctuation Tokens

Punctuation tokens consist of one of the following characters:

    ( ) , [ ] { } |

These characters are used to group terms.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 3.2.6 Layout

Any characters with ASCII code less than or equal to 32 appearing before a token are ignored.

All the text appearing in a line after the character % is taken to be a comment and ignored (including %). Comments can also be inserted by using the sequence `/*` to start the comment and `*/` to finish it. In the presence of any sequence of comments or layout characters, the YAP parser behaves as if it had found a single blank character. The end of a file also counts as a blank character for this purpose.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 3.3 Wide Character Support

YAP now implements a SWI-Prolog compatible interface to wide characters and the Universal Character Set (UCS). The following text was adapted from the SWI-Prolog manual.

YAP now supports wide characters, characters with character codes above 255 that cannot be represented in a single byte. Universal Character Set (UCS) is the ISO/IEC 10646 standard that specifies a unique 31-bits unsigned integer for any character in any language. It is a superset of 16-bit Unicode, which in turn is a superset of ISO 8859-1 (ISO Latin-1), a superset of US-ASCII. UCS can handle strings holding characters from multiple languages and character classification (uppercase, lowercase, digit, etc.) and operations such as case-conversion are unambiguously defined.

For this reason YAP, following SWI-Prolog, has two representations for atoms. If the text fits in ISO Latin-1, it is represented as an array of 8-bit characters. Otherwise the text is represented as an array of wide chars, which may take 16 or 32 bits. This representational issue is completely transparent to the Prolog user. Users of the foreign language interface sometimes need to be aware of these issues though.

Character coding comes into view when characters of strings need to be read from or written to file or when they have to be communicated to other software components using the foreign language interface. In this section we only deal with I/O through streams, which includes file I/O as well as I/O through network sockets.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 3.3.1 Wide character encodings on streams

Although characters are uniquely coded using the UCS standard internally, streams and files are byte (8-bit) oriented and there are a variety of ways to represent the larger UCS codes in an 8-bit octet stream. The most popular one, especially in the context of the web, is UTF-8. Bytes 0...127 represent simply the corresponding US-ASCII character, while bytes 128...255 are used for multi-byte encoding of characters placed higher in the UCS space. Especially on MS-Windows the 16-bit Unicode standard, represented by pairs of bytes is also popular.

Prolog I/O streams have a property called encoding which specifies the used encoding that influence `get_code/2` and `put_code/2` as well as all the other text I/O predicates.

The default encoding for files is derived from the Prolog flag `encoding`, which is initialised from the environment. If the environment variable `LANG` ends in "UTF-8", this encoding is assumed. Otherwise the default is `text` and the translation is left to the wide-character functions of the C-library (note that the Prolog native UTF-8 mode is considerably faster than the generic `mbrtowc()` one). The encoding can be specified explicitly in `load_files/2` for loading Prolog source with an alternative encoding, `open/4` when opening files or using `set_stream/2` on any open stream (not yet implemented). For Prolog source files we also provide the `encoding/1` directive that can be used to switch between encodings that are compatible to US-ASCII (`ascii`, `iso_latin_1`, `utf8` and many locales). For additional information and Unicode resources, please visit http://www.unicode.org/.

YAP currently defines and supports the following encodings:

`octet`

  Default encoding for binary streams. This causes the stream to be read and written fully untranslated.

`ascii`

  7-bit encoding in 8-bit bytes. Equivalent to `iso_latin_1`, but generates errors and warnings on encountering values above 127.

`iso_latin_1`

  8-bit encoding supporting many western languages. This causes the stream to be read and written fully untranslated.

`text`

  C-library default locale encoding for text files. Files are read and written using the C-library functions `mbrtowc()` and `wcrtomb()`. This may be the same as one of the other locales, notably it may be the same as `iso_latin_1` for western languages and `utf8` in a UTF-8 context.

`utf8`

  Multi-byte encoding of full UCS, compatible to `ascii`. See above.

`unicode_be`

  Unicode Big Endian. Reads input in pairs of bytes, most significant byte first. Can only represent 16-bit characters.

`unicode_le`

  Unicode Little Endian. Reads input in pairs of bytes, least significant byte first. Can only represent 16-bit characters.

Note that not all encodings can represent all characters. This implies that writing text to a stream may cause errors because the stream cannot represent these characters. The behaviour of a stream on these errors can be controlled using `open/4` or `set_stream/2` (not implemented). Initially the terminal stream write the characters using Prolog escape sequences while other streams generate an I/O exception.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 3.3.2 BOM: Byte Order Mark

From Wide character encodings on streams, you may have got the impression text-files are complicated. This section deals with a related topic, making live often easier for the user, but providing another worry to the programmer. BOM or Byte Order Marker is a technique for identifying Unicode text-files as well as the encoding they use. Such files start with the Unicode character `0xFEFF`, a non-breaking, zero-width space character. This is a pretty unique sequence that is not likely to be the start of a non-Unicode file and uniquely distinguishes the various Unicode file formats. As it is a zero-width blank, it even doesn’t produce any output. This solves all problems, or ...

Some formats start of as US-ASCII and may contain some encoding mark to switch to UTF-8, such as the `encoding="UTF-8"` in an XML header. Such formats often explicitly forbid the the use of a UTF-8 BOM. In other cases there is additional information telling the encoding making the use of a BOM redundant or even illegal.

The BOM is handled by the `open/4` predicate. By default, text-files are probed for the BOM when opened for reading. If a BOM is found, the encoding is set accordingly and the property `bom(true)` is available through `stream_property/2`. When opening a file for writing, writing a BOM can be requested using the option `bom(true)` with `open/4`.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 4 Loading Programs

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 4.1 Program loading and updating

`consult(+F)`

  Adds the clauses written in file F or in the list of files F to the program.

  In YAP `consult/1` does not remove previous clauses for the procedures defined in F. Moreover, note that all code in YAP is compiled.

`reconsult(+F)`

  Updates the program replacing the previous definitions for the predicates defined in F.

`[+F]`

  The same as `consult(F)`.

`[-+F]`

  The same as `reconsult(F)`

  Example:

      ?- [file1, -file2, -file3, file4].

  will consult `file1` `file4` and reconsult `file2` and `file3`.

`compile(+F)`

  In YAP, the same as `reconsult/1`.

`load_files(+Files, +Options)`

  General implementation of `consult`. Execution is controlled by the following flags:

  `autoload(+Autoload)`

    SWI-compatible option where if Autoload is `true` predicates are loaded on first call. Currently not supported.

  `derived_from(+File)`

    SWI-compatible option to control make. Currently not supported.

  `encoding(+Encoding)`

    Character encoding used in consulting files. Please see section Wide Character Support for supported encodings.

  `expand(+Bool)`

    Not yet implemented. In SWI-Prolog, if `true`, run the filenames through `expand_file_name/2` and load the returned files. Default is false, except for `consult/1` which is intended for interactive use.

  `if(+Condition)`

    Load the file only if the specified Condition is satisfied. The value `true` the file unconditionally, `changed` loads the file if it was not loaded before, or has been modified since it was loaded the last time, `not_loaded` loads the file if it was not loaded before.

  `imports(+ListOrAll)`

    If `all` and the file is a module file, import all public predicates. Otherwise import only the named predicates. Each predicate is referred to as `<name>/<arity>`. This option has no effect if the file is not a module file.

  `must_be_module(+Bool)`

    If true, raise an error if the file is not a module file. Used by `use_module/[1,2]`.

  `silent(+Bool)`

    If true, load the file without printing a message. The specified value is the default for all files loaded as a result of loading the specified files.

  `stream(+Input)`

    This SWI-Prolog extension compiles the data from the stream Input. If this option is used, Files must be a single atom which is used to identify the source-location of the loaded clauses as well as remove all clauses if the data is re-consulted.

    This option is added to allow compiling from non-file locations such as databases, the web, the user (see consult/1) or other servers.

  `compilation_mode(+Mode)`

    This extension controls how procedures are compiled. If Mode is `compact` clauses are compiled and no source code is stored; if it is `source` clauses are compiled and source code is stored; if it is `assert_all` clauses are asserted into the data-base.

`ensure_loaded(+F) [ISO]`

  When the files specified by F are module files, `ensure_loaded/1` loads them if they have note been previously loaded, otherwise advertises the user about the existing name clashes and prompts about importing or not those predicates. Predicates which are not public remain invisible.

  When the files are not module files, `ensure_loaded/1` loads them if they have not been loaded before, does nothing otherwise.

  F must be a list containing the names of the files to load.

`make`

  SWI-Prolog built-in to consult all source files that have been changed since they were consulted. It checks all loaded source files. make/0 can be combined with the compiler to speed up the development of large packages. In this case compile the package using

          sun% pl -g make -o my_program -c file ...

  If ‘my_program’ is started it will first reconsult all source files that have changed since the compilation.

`include(+F) [ISO]`

  The `include` directive includes the text files or sequence of text files specified by F into the file being currently consulted.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 4.2 Changing the Compiler’s Behavior

This section presents a set of built-ins predicates designed to set the environment for the compiler.

`source_mode(-O,+N)`

  The state of source mode can either be on or off. When the source mode is on, all clauses are kept both as compiled code and in a "hidden" database. O is unified with the previous state and the mode is set according to N.

`source`

  After executing this goal, YAP keeps information on the source of the predicates that will be consulted. This enables the use of `listing/0`, `listing/1` and `clause/2` for those clauses.

  The same as `source_mode(_,on)` or as declaring all newly defined static procedures as `public`.

`no_source`

  The opposite to `source`.

  The same as `source_mode(_,off)`.

`compile_expressions`

  After a call to this predicate, arithmetical expressions will be compiled. (see example below). This is the default behavior.

`do_not_compile_expressions`

  After a call to this predicate, arithmetical expressions will not be compiled.

      ?- source, do_not_compile_expressions.
      yes
      ?- [user].
      | p(X) :- X is 2 * (3 + 8).
      | :- end_of_file.
      ?- compile_expressions.
      yes
      ?- [user].
      | q(X) :- X is 2 * (3 + 8).
      | :- end_of_file.
      :- listing.

      p(A):-
            A is 2 * (3 + 8).

      q(A):-
            A is 22.

`hide(+Atom)`

  Make atom Atom invisible.

`unhide(+Atom)`

  Make hidden atom Atom visible.

`hide_predicate(+Pred)`

  Make predicate Pred invisible to `current_predicate/2`, `listing`, and friends.

`expand_exprs(-O,+N)`

  Puts YAP in state N (`on` or `off`) and unify O with the previous state, where On is equivalent to `compile_expressions` and `off` is equivalent to `do_not_compile_expressions`. This predicate was kept to maintain compatibility with C-Prolog.

`path(-D)`

  Unifies D with the current directory search-path of YAP. Note that this search-path is only used by YAP to find the files for `consult/1`, `reconsult/1` and `restore/1` and should not be taken for the system search path.

`add_to_path(+D)`

  Adds D to the end of YAP’s directory search path.

`add_to_path(+D,+N)`

  Inserts D in the position, of the directory search path of YAP, specified by N. N must be either of `first` or `last`.

`remove_from_path(+D)`

  Remove D from YAP’s directory search path.

`style_check(+X)`

  Turns on style checking according to the attribute specified by X, which must be one of the following:

  `single_var`

    Checks single occurrences of named variables in a clause.

  `discontiguous`

    Checks non-contiguous clauses for the same predicate in a file.

  `multiple`

    Checks the presence of clauses for the same predicate in more than one file when the predicate has not been declared as `multifile`

  `all`

    Performs style checking for all the cases mentioned above.

  By default, style checking is disabled in YAP unless we are in `sicstus` or `iso` language mode.

  The `style_check/1` built-in is now deprecated. Please use the `set_prolog_flag/1` instead.

`no_style_check(+X)`

  Turns off style checking according to the attribute specified by X, which has the same meaning as in `style_check/1`.

  The `no_style_check/1` built-in is now deprecated. Please use the `set_prolog_flag/1` instead.

`multifile P [ISO]`

  Instructs the compiler about the declaration of a predicate P in more than one file. It must appear in the first of the loaded files where the predicate is declared, and before declaration of any of its clauses.

  Multifile declarations affect `reconsult/1` and `compile/1`: when a multifile predicate is reconsulted, only the clauses from the same file are removed.

  Since YAP4.3.0 multifile procedures can be static or dynamic.

`discontiguous(+G) [ISO]`

  Declare that the arguments are discontiguous procedures, that is, clauses for discontigous procedures may be separated by clauses from other procedures.

`initialization(+G) [ISO]`

  The compiler will execute goals G after consulting the current file.

`initialization(+Goal,+When)`

  Similar to `initialization/1`, but allows for specifying when Goal is executed while loading the program-text:

  `now`

    Execute Goal immediately.

  `after_load`

    Execute Goal after loading program-text. This is the same as initialization/1.

  `restore`

    Do not execute Goal while loading the program, but only when restoring a state (not implemented yet).

`library_directory(+D)`

  Succeeds when D is a current library directory name. Library directories are the places where files specified in the form `library(File)` are searched by the predicates `consult/1`, `reconsult/1`, `use_module/1` or `ensure_loaded/1`.

`file_search_path(+NAME,-DIRECTORY)`

  Allows writing file names as compound terms. The NAME and DIRECTORY must be atoms. The predicate may generate multiple solutions. The predicate is originally defined as follows:

      file_search_path(library,A) :-
         library_directory(A).
      file_search_path(system,A) :-
         prolog_flag(host_type,A).

  Thus, `[library(A)]` will search for a file using `library_directory/1` to obtain the prefix.

`library_directory(+D)`

  Succeeds when D is a current library directory name. Library directories are the places where files specified in the form `library(File)` are searched by the predicates `consult/1`, `reconsult/1`, `use_module/1` or `ensure_loaded/1`.

`prolog_file_name(+Name,-FullPath)`

  Unify FullPath with the absolute path YAP would use to consult file Name.

`prolog_to_os_filename(+PrologPath,-OsPath)`

  This is an SWI-Prolog built-in. Converts between the internal Prolog pathname conventions and the operating-system pathname conventions. The internal conventions are Unix and this predicates is equivalent to =/2 (unify) on Unix systems. On DOS systems it will change the directory-separator, limit the filename length map dots, except for the last one, onto underscores.

`expand_file_name(+WildCard,-List)`

  This is an SWI-Prolog built-in. Unify List with a sorted list of files or directories matching WildCard. The normal Unix wildcard constructs `?`, `*`, `[ ... ]` and `{...}` are recognised. The interpretation of `{...}` is interpreted slightly different from the C shell (csh(1)). The comma separated argument can be arbitrary patterns, including `{...}` patterns. The empty pattern is legal as well: `{.pl,}` matches either `.pl` or the empty string.

  If the pattern contains wildcard characters, only existing files and directories are returned. Expanding a pattern’ without wildcard characters returns the argument, regardless on whether or not it exists.

  Before expanding wildcards, the construct $var is expanded to the value of the environment variable var and a possible leading ~ character is expanded to the user’s home directory. In Windows, the home directory is determined as follows: if the environment variable `HOME` exists, this is used. If the variables `HOMEDRIVE` and `HOMEPATH` exist (Windows-NT), these are used. At initialisation, the system will set the environment variable `HOME` to point to the YAP home directory if neither `HOME` nor `HOMEPATH` and `HOMEDRIVE` are defined.

`public P [ISO extension]`

  Instructs the compiler that the source of a predicate of a list of predicates P must be kept. This source is then accessible through the `clause/2` procedure and through the `listing` family of built-ins.

  Note that all dynamic procedures are public. The `source` directive defines all new or redefined predicates to be public.

  Since YAP4.3.0 multifile procedures can be static or dynamic.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 4.3 Conditional Compilation

Conditional compilation builds on the same principle as `term_expansion/2`, `goal_expansion/2` and the expansion of grammar rules to compile sections of the source-code conditionally. One of the reasons for introducing conditional compilation is to simplify writing portable code.

Note that these directives can only be appear as separate terms in the input. Typical usage scenarios include:

- Load different libraries on different dialects
- Define a predicate if it is missing as a system predicate
- Realise totally different implementations for a particular part of the code due to different capabilities.
- Realise different configuration options for your software.

`if(+Goal)`

  Compile subsequent code only if Goal succeeds. For enhanced portability, Goal is processed by `expand_goal/2` before execution. If an error occurs, the error is printed and processing proceeds as if Goal has failed.

`else`

  Start ‘else’ branch.

`endif`

  End of conditional compilation.

`elif(+Goal)`

  Equivalent to `:- else. :-if(Goal) ... :- endif.` In a sequence as below, the section below the first matching elif is processed, If no test succeeds the else branch is processed.

      :- if(test1).
      section_1.
      :- elif(test2).
      section_2.
      :- elif(test3).
      section_3.
      :- else.
      section_else.
      :- endif.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 4.4 Saving and Loading Prolog States

`save(+F)`

  Saves an image of the current state of YAP in file F. From YAP4.1.3 onwards, YAP saved states are executable files in the Unix ports.

`save(+F,-OUT)`

  Saves an image of the current state of YAP in file F. From YAP4.1.3 onwards, YAP saved states are executable files in the Unix ports.

  Unify OUT with 1 when saving the file and OUT with 0 when restoring the saved state.

`save_program(+F)`

  Saves an image of the current state of the YAP database in file F.

`save_program(+F, :G)`

  Saves an image of the current state of the YAP database in file F, and guarantee that execution of the restored code will start by trying goal G.

`restore(+F)`

  Restores a previously saved state of YAP from file F.

  YAP always tries to find saved states from the current directory first. If it cannot it will use the environment variable YAPLIBDIR, if defined, or search the default library directory.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 5 The Module System

Module systems are quite important for the development of large applications. YAP implements a module system compatible with the Quintus Prolog module system.

The YAP module system is predicate-based. This means a module consists of a set of predicates (or procedures), such that some predicates are public and the others are local to a module. Atoms and terms in general are global to the system. Moreover, the module system is flat, meaning that we do not support a hierarchy of modules. Modules can automatically import other modules, though. For compatibility with other module systems the YAP module system is non-strict, meaning both that there is a way to access predicates private to a module and that it is possible to declare predicates for a module from some other module.

YAP allows one to ignore the module system if one does not want to use it. Last note that using the module system does not introduce any significant overheads.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 5.1 Module Concepts

The YAP module system applies to predicates. All predicates belong to a module. System predicates belong to the module `primitives`, and by default new predicates belong to the module `user`. Predicates from the module `primitives` are automatically visible to every module.

Every predicate must belong to a module. This module is called its source module.

By default, the source module for a clause occurring in a source file with a module declaration is the declared module. For goals typed in a source file without module declarations, their module is the module the file is being loaded into. If no module declarations exist, this is the current type-in module. The default type-in module is `user`, but one can set the current module by using the built-in `module/1`.

Note that in this module system one can explicitly specify the source mode for a clause by prefixing a clause with its module, say:

    user:(a :- b).

In fact, to specify the source module for a clause it is sufficient to specify the source mode for the clause’s head:

    user:a :- b.

The rules for goals are similar. If a goal appears in a text file with a module declaration, the goal’s source module is the declared module. Otherwise, it is the module the file is being loaded into or the type-in module.

One can override this rule by prefixing a goal with the module it is supposed to be executed in, say:

    nasa:launch(apollo,13).

will execute the goal `launch(apollo,13)` as if the current source module was `nasa`.

Note that this rule breaks encapsulation and should be used with care.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 5.2 Defining a New Module

A new module is defined by a `module` declaration:

`module(+M,+L)`

  This directive defines the file where it appears as a module file; it must be the first declaration in the file. M must be an atom specifying the module name; L must be a list containing the module’s public predicates specification, in the form `[predicate_name/arity,...]`.

  The public predicates of a module file can be made accessible by other files through the directives `use_module/1`, `use_module/2`, `ensure_loaded/1` and the predicates `consult/1` or `reconsult/1`. The non-public predicates of a module file are not visible by other files; they can, however, be accessed by prefixing the module name with the `:/2` operator.

The built-in `module/1` sets the current source module:

`module(+M,+L, +Options)`

  Similar to `module/2`, this directive defines the file where it appears in as a module file; it must be the first declaration in the file. M must be an atom specifying the module name; L must be a list containing the module’s public predicates specification, in the form `[predicate_name/arity,...]`.

  The last argument Options must be a list of options, which can be:

  `filename`

    the filename for a module to import into the current module.

  `library(file)`

    a library file to import into the current module.

  `hide(Opt)`

    if Opt is `false`, keep source code for current module, if `true`, disable.

`module(+M)`

  Defines M to be the current working or type-in module. All files which are not bound to a module are assumed to belong to the working module (also referred to as type-in module). To compile a non-module file into a module which is not the working one, prefix the file name with the module name, in the form `Module:File`, when loading the file.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 5.3 Using Modules

By default, all procedures to consult a file will load the modules defined therein. The two following declarations allow one to import a module explicitly. They differ on whether one imports all predicate declared in the module or not.

`use_module(+F)`

  Loads the files specified by F, importing all their public predicates. Predicate name clashes are resolved by asking the user about importing or not the predicate. A warning is displayed when F is not a module file.

`use_module(+F,+L)`

  Loads the files specified by F, importing the predicates specified in the list L. Predicate name clashes are resolved by asking the user about importing or not the predicate. A warning is displayed when F is not a module file.

`use_module(?M,?F,+L)`

  If module M has been defined, import the procedures in L to the current module. Otherwise, load the files specified by F, importing the predicates specified in the list L.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 5.4 Meta-Predicates in Modules

The module system must know whether predicates operate on goals or clauses. Otherwise, such predicates would call a goal in the module they were defined, instead of calling it in the module they are currently executing. So, for instance, consider a file example.pl:

    :- module(example,[a/1]).

    a(G) :- call(G)

We import this module with `use_module(example)` into module `user`. The expected behavior for a goal `a(p)` is to execute goal `p` within the module `user`. However, `a/1` will call `p` within module `example`.

The `meta_predicate/1` declaration informs the system that some arguments of a predicate are goals, clauses, clauses heads or other terms related to a module, and that these arguments must be prefixed with the current source module:

`meta_predicate G1,....,Gn`

  Each Gi is a mode specification.

  If the argument is `:`, it does not refer directly to a predicate but must be module expanded. If the argument is an integer, the argument is a goal or a closure and must be expanded. Otherwise, the argument is not expanded. Note that the system already includes declarations for all built-ins.

  For example, the declaration for `call/1` and `setof/3` are:

      :- meta_predicate call(0), setof(?,0,?).

The previous example is expanded to the following code which explains, why the goal `a(p)` calls `p` in `example` and not in `user`. The goal `call(G)` is expanded because of the meta-predicate declaration for `call/1`.

    :- module(example,[a/1]).

    a(G) :- call(example:G)

By adding a meta-predicate declaration for `a/1`, the goal `a(p)` in module user will be expanded to `a(user:p)` thereby preserving the module information.

    :- module(example,[a/1]).

    :- meta_predicate a(:).
    a(G) :- call(G)

An alternate mechanism is the directive `module_transparent/1` offered for compatibility with SWI-Prolog.

`module_transparent +Preds`

  Preds is a comma separated sequence of name/arity predicate indicators (like `dynamic/1`). Each goal associated with a transparent declared predicate will inherit the context module from its parent goal.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 5.5 Re-Exporting Predicates From Other Modules

It is sometimes convenient to re-export predicates originally defined in a different module. This is often useful if you are adding to the functionality of a module, or if you are composing a large module with several small modules. The following declarations can be used for that purpose:

`reexport(+F)`

  Export all predicates defined in file F as if they were defined in the current module.

`reexport(+F,+Decls)`

  Export predicates defined in file F according to Decls. The declarations may be of the form:

  - A list of predicate declarations to be exported. Each declaration may be a predicate indicator or of the form “PI `as` NewName”, meaning that the predicate with indicator PI is to be exported under name NewName.
  - `except`(List) In this case, all predicates not in List are exported. Moreover, if “PI `as` NewName” is found, the predicate with indicator PI is to be exported under name NewName as before.

Re-exporting predicates must be used with some care. Please, take into account the following observations:

- The `reexport` declarations must be the first declarations to follow the `module` declaration.
- It is possible to use both `reexport` and `use_module`, but all predicates reexported are automatically available for use in the current module.
- In order to obtain efficient execution, YAP compiles dependencies between re-exported predicates. In practice, this means that changing a `reexport` declaration and then just recompiling the file may result in incorrect execution.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 6 Built-In Predicates

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.1 Control Predicates

This chapter describes the predicates for controlling the execution of Prolog programs.

In the description of the arguments of functors the following notation will be used:

- a preceding plus sign will denote an argument as an "input argument" - it cannot be a free variable at the time of the call;
- a preceding minus sign will denote an "output argument";
- an argument with no preceding symbol can be used in both ways.

`+P, +Q [ISO]`

  Conjunction of goals (and).

  Example:

       p(X) :- q(X), r(X).

  should be read as "p(X) if q(X) and r(X)".

`+P ; +Q [ISO]`

  Disjunction of goals (or).

  Example:

       p(X) :- q(X); r(X).

  should be read as "p(X) if q(X) or r(X)".

`true [ISO]`

  Succeeds once.

`fail [ISO]`

  Fails always.

`false`

  The same as fail

`! [ISO]`

  Read as "cut". Cuts any choices taken in the current procedure. When first found "cut" succeeds as a goal, but if backtracking should later return to it, the parent goal (the one which matches the head of the clause containing the "cut", causing the clause activation) will fail. This is an extra-logical predicate and cannot be explained in terms of the declarative semantics of Prolog.

  example:

       member(X,[X|_]).
       member(X,[_|L]) :- member(X,L).

  With the above definition

       ?- member(X,[1,2,3]).

  will return each element of the list by backtracking. With the following definition:

       member(X,[X|_]) :- !.
       member(X,[_|L]) :- member(X,L).

  the same query would return only the first element of the list, since backtracking could not "pass through" the cut.

`\+ +P [ISO]`

  Goal P is not provable. The execution of this predicate fails if and only if the goal P finitely succeeds. It is not a true logical negation, which is impossible in standard Prolog, but "negation-by-failure".

  This predicate might be defined as:

       \+(P) :- P, !, fail.
       \+(_).

  if P did not include "cuts".

`not +P`

  Goal P is not provable. The same as `'\+ P'`.

  This predicate is kept for compatibility with C-Prolog and previous versions of YAP. Uses of `not/1` should be replace by `(\+)/1`, as YAP does not implement true negation.

`+P -> +Q [ISO]`

  Read as "if-then-else" or "commit". This operator is similar to the conditional operator of imperative languages and can be used alone or with an else part as follows:

  `+P -> +Q`

    "if P then Q".

  `+P -> +Q; +R`

    "if P then Q else R".

  These two predicates could be defined respectively in Prolog as:

       (P -> Q) :- P, !, Q.

  and

       (P -> Q; R) :- P, !, Q.
       (P -> Q; R) :- R.

  if there were no "cuts" in P, Q and R.

  Note that the commit operator works by "cutting" any alternative solutions of P.

  Note also that you can use chains of commit operators like:

          P -> Q ; R -> S ; T.

  Note that `(->)/2` does not affect the scope of cuts in its arguments.

`+Condition *-> +Action ; +Else`

  This construct implements the so-called soft-cut. The control is defined as follows: If Condition succeeds at least once, the semantics is the same as (Condition, Action). If Condition does not succeed, the semantics is that of (\+ Condition, Else). In other words, If Condition succeeds at least once, simply behave as the conjunction of Condition and Action, otherwise execute Else.

  The construct A *-> B, i.e. without an Else branch, is translated as the normal conjunction A, B.

`repeat [ISO]`

  Succeeds repeatedly.

  In the next example, `repeat` is used as an efficient way to implement a loop. The next example reads all terms in a file:

       a :- repeat, read(X), write(X), nl, X=end_of_file, !.

  the loop is effectively terminated by the cut-goal, when the test-goal `X=end` succeeds. While the test fails, the goals `read(X)`, `write(X)`, and `nl` are executed repeatedly, because backtracking is caught by the `repeat` goal.

  The built-in `repeat/1` could be defined in Prolog by:

       repeat.
       repeat :- repeat.

`call(+P) [ISO]`

  If P is instantiated to an atom or a compound term, the goal `call(P)` is executed as if the value of `P` was found instead of the call to `call/1`, except that any "cut" occurring in P only cuts alternatives in the execution of P.

`incore(+P)`

  The same as `call/1`.

`call(+Closure,...,?Ai,...)`

  Meta-call where Closure is a closure that is converted into a goal by appending the Ai additional arguments. The number of arguments varies between 0 and 10.

`call_with_args(+Name,...,?Ai,...)`

  Meta-call where Name is the name of the procedure to be called and the Ai are the arguments. The number of arguments varies between 0 and 10. New code should use `call/N` for better portability.

  If Name is a complex term, then `call_with_args/n` behaves as `call/n`:

      call(p(X1,...,Xm), Y1,...,Yn) :- p(X1,...,Xm,Y1,...,Yn).

`+P`

  The same as `call(P)`. This feature has been kept to provide compatibility with C-Prolog. When compiling a goal, YAP generates a `call(X)` whenever a variable X is found as a goal.

       a(X) :- X.

  is converted to:

       a(X) :- call(X).

`if(?G,?H,?I)`

  Call goal H once per each solution of goal H. If goal H has no solutions, call goal I.

  The built-in `if/3` is similar to `->/3`, with the difference that it will backtrack over the test goal. Consider the following small data-base:

      a(1).        b(a).          c(x).
      a(2).        b(b).          c(y).

  Execution of an `if/3` query will proceed as follows:

         ?- if(a(X),b(Y),c(Z)).

      X = 1,
      Y = a ? ;

      X = 1,
      Y = b ? ;

      X = 2,
      Y = a ? ;

      X = 2,
      Y = b ? ;

      no

  The system will backtrack over the two solutions for `a/1` and the two solutions for `b/1`, generating four solutions.

  Cuts are allowed inside the first goal G, but they will only prune over G.

  If you want G to be deterministic you should use if-then-else, as it is both more efficient and more portable.

`once(:G) [ISO]`

  Execute the goal G only once. The predicate is defined by:

       once(G) :- call(G), !.

  Note that cuts inside `once/1` can only cut the other goals inside `once/1`.

`forall(:Cond,:Action)`

  For all alternative bindings of Cond Action can be proven. The example verifies that all arithmetic statements in the list L are correct. It does not say which is wrong if one proves wrong.

      ?- forall(member(Result = Formula, [2 = 1 + 1, 4 = 2 * 2]),
                       Result =:= Formula).

`ignore(:Goal)`

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

      ignore(Goal) :-
              Goal, !.
      ignore(_).

`abort`

  Abandons the execution of the current goal and returns to top level. All break levels (see `break/0` below) are terminated. It is mainly used during debugging or after a serious execution error, to return to the top-level.

`break`

  Suspends the execution of the current goal and creates a new execution level similar to the top level, displaying the following message:

       [ Break (level <number>) ]

  telling the depth of the break level just entered. To return to the previous level just type the end-of-file character or call the end_of_file predicate. This predicate is especially useful during debugging.

`halt [ISO]`

  Halts Prolog, and exits to the calling application. In YAP, `halt/0` returns the exit code `0`.

`halt(+ I) [ISO]`

  Halts Prolog, and exits to the calling application returning the code given by the integer I.

`catch(+Goal,+Exception,+Action) [ISO]`

  The goal `catch(Goal,Exception,Action)` tries to execute goal Goal. If during its execution, Goal throws an exception E’ and this exception unifies with Exception, the exception is considered to be caught and Action is executed. If the exception E’ does not unify with Exception, control again throws the exception.

  The top-level of YAP maintains a default exception handler that is responsible to capture uncaught exceptions.

`throw(+Ball) [ISO]`

  The goal `throw(Ball)` throws an exception. Execution is stopped, and the exception is sent to the ancestor goals until reaching a matching `catch/3`, or until reaching top-level.

`garbage_collect`

  The goal `garbage_collect` forces a garbage collection.

`garbage_collect_atoms`

  The goal `garbage_collect` forces a garbage collection of the atoms in the data-base. Currently, only atoms are recovered.

`gc`

  The goal `gc` enables garbage collection. The same as `yap_flag(gc,on)`.

`nogc`

  The goal `nogc` disables garbage collection. The same as `yap_flag(gc,off)`.

`grow_heap(+Size)`

  Increase heap size Size kilobytes.

`grow_stack(+Size)`

  Increase stack size Size kilobytes.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.2 Handling Undefined Procedures

A predicate in a module is said to be undefined if there are no clauses defining the predicate, and if the predicate has not been declared to be dynamic. What YAP does when trying to execute undefined predicates can be specified in three different ways:

- By setting an YAP flag, through the `yap_flag/2` or `set_prolog_flag/2` built-ins. This solution generalizes the ISO standard.
- By using the `unknown/2` built-in (this solution is compatible with previous releases of YAP).
- By defining clauses for the hook predicate `user:unknown_predicate_handler/3`. This solution is compatible with SICStus Prolog.

In more detail:

`unknown(-O,+N)`

  Specifies an handler to be called is a program tries to call an undefined static procedure P.

  The arity of N may be zero or one. If the arity is `0`, the new action must be one of `fail`, `warning`, or `error`. If the arity is `1`, P is an user-defined handler and at run-time, the argument to the handler P will be unified with the undefined goal. Note that N must be defined prior to calling `unknown/2`, and that the single argument to N must be unbound.

  In YAP, the default action is to `fail` (note that in the ISO Prolog standard the default action is `error`).

  After defining `undefined/1` by:

      undefined(A) :- format('Undefined predicate: ~w~n',[A]), fail.

  and executing the goal:

      unknown(U,undefined(X)).

  a call to a predicate for which no clauses were defined will result in the output of a message of the form:

      Undefined predicate: user:xyz(A1,A2)

  followed by the failure of that call.

`yap_flag(unknown,+SPEC)`

  Alternatively, one can use `yap_flag/2`, `current_prolog_flag/2`, or `set_prolog_flag/2`, to set this functionality. In this case, the first argument for the built-ins should be `unknown`, and the second argument should be either `error`, `warning`, `fail`, or a goal.

`user:unknown_predicate_handler(+G,+M,?NG)`

  The user may also define clauses for `user:unknown_predicate_handler/3` hook predicate. This user-defined procedure is called before any system processing for the undefined procedure, with the first argument G set to the current goal, and the second M set to the current module. The predicate G will be called from within the user module.

  If `user:unknown_predicate_handler/3` succeeds, the system will execute NG. If `user:unknown_predicate_handler/3` fails, the system will execute default action as specified by `unknown/2`.

`exception(+Exception, +Context, -Action)`

  Dynamic predicate, normally not defined. Called by the Prolog system on run-time exceptions that can be repaired ‘just-in-time’. The values for Exception are described below. See also `catch/3` and `throw/1`. If this hook predicate succeeds it must instantiate the Action argument to the atom `fail` to make the operation fail silently, `retry` to tell Prolog to retry the operation or `error` to make the system generate an exception. The action `retry` only makes sense if this hook modified the environment such that the operation can now succeed without error.

  `undefined_predicate`

    Context is instantiated to a predicate-indicator (Module:Name/Arity). If the predicate fails Prolog will generate an existence_error exception. The hook is intended to implement alternatives to the SWI built-in autoloader, such as autoloading code from a database. Do not use this hook to suppress existence errors on predicates. See also `unknown`.

  `undefined_global_variable`

    Context is instantiated to the name of the missing global variable. The hook must call `nb_setval/2` or `b_setval/2` before returning with the action retry.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.3 Message Handling

The interaction between YAP and the user relies on YAP’s ability to portray messages. These messages range from prompts to error information. All message processing is performed through the builtin `print_message/2`, in two steps:

- The message is processed into a list of commands
- The commands in the list are sent to the `format/3` builtin in sequence.

The first argument to `print_message/2` specifies the importance of the message. The options are:

`error`

  error handling

`warning`

  compilation and run-time warnings,

`informational`

  generic informational messages

`help`

  help messages (not currently implemented in YAP)

`query`

  query used in query processing (not currently implemented in YAP)

`silent`

  messages that do not produce output but that can be intercepted by hooks.

The next table shows the main predicates and hooks associated to message handling in YAP:

`print_message(+Kind, Term)`

  The predicate print_message/2 is used to print messages, notably from exceptions in a human-readable format. Kind is one of `informational`, `banner`, `warning`, `error`, `help` or `silent`. A human-readable message is printed to the stream `user_error`.

  If the Prolog flag `verbose` is `silent`, messages with Kind `informational`, or `banner` are treated as silent.

  This predicate first translates the Term into a list of ‘message lines’ (see `print_message_lines/3` for details). Next it will call the hook `message_hook/3` to allow the user intercepting the message. If `message_hook/3` fails it will print the message unless Kind is silent.

  If you need to report errors from your own predicates, we advise you to stick to the existing error terms if you can; but should you need to invent new ones, you can define corresponding error messages by asserting clauses for `prolog:message/2`. You will need to declare the predicate as multifile.

`print_message_lines(+Stream, +Prefix, +Lines)`

  Print a message (see `print_message/2`) that has been translated to a list of message elements. The elements of this list are:

  ``<Format>`-`<Args>``

    Where Format is an atom and Args is a list of format argument. Handed to `format/3`.

  ``flush``

    If this appears as the last element, Stream is flushed (see `flush_output/1`) and no final newline is generated.

  ``at_same_line``

    If this appears as first element, no prefix is printed for the first line and the line-position is not forced to 0 (see `format/1`, `~N`).

  ``<Format>``

    Handed to `format/3` as `format(Stream, Format, [])`.

  `nl`

    A new line is started and if the message is not complete the Prefix is printed too.

`user:message_hook(+Term, +Kind, +Lines)`

  Hook predicate that may be define in the module `user` to intercept messages from `print_message/2`. Term and Kind are the same as passed to `print_message/2`. Lines is a list of format statements as described with `print_message_lines/3`.

  This predicate should be defined dynamic and multifile to allow other modules defining clauses for it too.

`message_to_string(+Term, -String)`

  Translates a message-term into a string object. Primarily intended for SWI-Prolog emulation.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.4 Predicates on terms

`var(T) [ISO]`

  Succeeds if T is currently a free variable, otherwise fails.

`atom(T) [ISO]`

  Succeeds if and only if T is currently instantiated to an atom.

`atomic(T) [ISO]`

  Checks whether T is an atomic symbol (atom or number).

`compound(T) [ISO]`

  Checks whether T is a compound term.

`db_reference(T)`

  Checks whether T is a database reference.

`float(T) [ISO]`

  Checks whether T is a floating point number.

`rational(T)`

  Checks whether `T` is a rational number.

`integer(T) [ISO]`

  Succeeds if and only if T is currently instantiated to an integer.

`nonvar(T) [ISO]`

  The opposite of `var(T)`.

`number(T) [ISO]`

  Checks whether `T` is an integer, rational or a float.

`primitive(T)`

  Checks whether T is an atomic term or a database reference.

`simple(T)`

  Checks whether T is unbound, an atom, or a number.

`callable(T)`

  Checks whether T is a callable term, that is, an atom or a compound term.

`numbervars(T,+N1,-Nn)`

  Instantiates each variable in term T to a term of the form: `'$VAR'(I)`, with I increasing from N1 to Nn.

`ground(T)`

  Succeeds if there are no free variables in the term T.

`arg(+N,+T,A) [ISO]`

  Succeeds if the argument N of the term T unifies with A. The arguments are numbered from 1 to the arity of the term.

  The current version will generate an error if T or N are unbound, if T is not a compound term, of if N is not a positive integer. Note that previous versions of YAP would fail silently under these errors.

`functor(T,F,N) [ISO]`

  The top functor of term T is named F and has arity N.

  When T is not instantiated, F and N must be. If N is 0, F must be an atomic symbol, which will be unified with T. If N is not 0, then F must be an atom and T becomes instantiated to the most general term having functor F and arity N. If T is instantiated to a term then F and N are respectively unified with its top functor name and arity.

  In the current version of YAP the arity N must be an integer. Previous versions allowed evaluable expressions, as long as the expression would evaluate to an integer. This feature is not available in the ISO Prolog standard.

`T =.. L [ISO]`

  The list L is built with the functor and arguments of the term T. If T is instantiated to a variable, then L must be instantiated either to a list whose head is an atom, or to a list consisting of just a number.

`X = Y [ISO]`

  Tries to unify terms X and Y.

`X \= Y [ISO]`

  Succeeds if terms X and Y are not unifiable.

`unify_with_occurs_check(?T1,?T2) [ISO]`

  Obtain the most general unifier of terms T1 and T2, if there is one.

  This predicate implements the full unification algorithm. An example:n

      unify_with_occurs_check(a(X,b,Z),a(X,A,f(B)).

  will succeed with the bindings `A = b` and `Z = f(B)`. On the other hand:

      unify_with_occurs_check(a(X,b,Z),a(X,A,f(Z)).

  would fail, because `Z` is not unifiable with `f(Z)`. Note that `(=)/2` would succeed for the previous examples, giving the following bindings `A = b` and `Z = f(Z)`.

`copy_term(?TI,-TF) [ISO]`

  Term TF is a variant of the original term TI, such that for each variable V in the term TI there is a new variable V’ in term TF. Notice that:

  - suspended goals and attributes for attributed variables in TI are also duplicated;
  - ground terms are shared between the new and the old term.

  If you do not want any sharing to occur please use `duplicate_term/2`.

`duplicate_term(?TI,-TF)`

  Term TF is a variant of the original term TI, such that for each variable V in the term TI there is a new variable V’ in term TF, and the two terms do not share any structure. All suspended goals and attributes for attributed variables in TI are also duplicated.

  Also refer to `copy_term/2`.

`is_list(+List)`

  True when List is a proper list. That is, List is bound to the empty list (nil) or a term with functor ’.’ and arity 2.

`?Term1 =@= ?Term2`

  Same as `variant/2`, succeeds if Term1 and Term2 are variant terms.

`subsumes_term(?Subsumer, ?Subsumed)`

  Succeed if Submuser subsumes Subsuned but does not bind any variable in Subsumer.

`acyclic_term(?Term)`

  Succeed if the argument Term is an acyclic term.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.5 Predicates on Atoms

The following predicates are used to manipulate atoms:

`name(A,L)`

  The predicate holds when at least one of the arguments is ground (otherwise, an error message will be displayed). The argument A will be unified with an atomic symbol and L with the list of the ASCII codes for the characters of the external representation of A.

       name(yap,L).

  will return:

       L = [121,97,112].

  and

       name(3,L).

  will return:

       L = [51].

`atom_chars(?A,?L) [ISO]`

  The predicate holds when at least one of the arguments is ground (otherwise, an error message will be displayed). The argument A must be unifiable with an atom, and the argument L with the list of the characters of A.

`atom_codes(?A,?L) [ISO]`

  The predicate holds when at least one of the arguments is ground (otherwise, an error message will be displayed). The argument A will be unified with an atom and L with the list of the ASCII codes for the characters of the external representation of A.

`atom_concat(+As,?A)`

  The predicate holds when the first argument is a list of atoms, and the second unifies with the atom obtained by concatenating all the atoms in the first list.

`atomic_concat(+As,?A)`

  The predicate holds when the first argument is a list of atomic terms, and the second unifies with the atom obtained by concatenating all the atomic terms in the first list. The first argument thus may contain atoms or numbers.

`atomic_list_concat(+As,?A)`

  The predicate holds when the first argument is a list of atomic terms, and the second unifies with the atom obtained by concatenating all the atomic terms in the first list. The first argument thus may contain atoms or numbers.

`atomic_list_concat(?As,+Separator,?A)`

  Creates an atom just like `atomic_list_concat/2`, but inserts Separator between each pair of atoms. For example:

      ?- atomic_list_concat([gnu, gnat], ', ', A).

      A = 'gnu, gnat'

  YAP emulates the SWI-Prolog version of this predicate that can also be used to split atoms by instantiating Separator and Atom as shown below.

      ?- atomic_list_concat(L, -, 'gnu-gnat').

      L = [gnu, gnat]

`atom_length(+A,?I) [ISO]`

  The predicate holds when the first argument is an atom, and the second unifies with the number of characters forming that atom.

`atom_concat(?A1,?A2,?A12) [ISO]`

  The predicate holds when the third argument unifies with an atom, and the first and second unify with atoms such that their representations concatenated are the representation for A12.

  If A1 and A2 are unbound, the built-in will find all the atoms that concatenated give A12.

`number_chars(?I,?L) [ISO]`

  The predicate holds when at least one of the arguments is ground (otherwise, an error message will be displayed). The argument I must be unifiable with a number, and the argument L with the list of the characters of the external representation of I.

`number_codes(?A,?L) [ISO]`

  The predicate holds when at least one of the arguments is ground (otherwise, an error message will be displayed). The argument A will be unified with a number and L with the list of the ASCII codes for the characters of the external representation of A.

`atom_number(?Atom,?Number)`

  The predicate holds when at least one of the arguments is ground (otherwise, an error message will be displayed). If the argument Atom is an atom, Number must be the number corresponding to the characters in Atom, otherwise the characters in Atom must encode a number Number.

`number_atom(?I,?L)`

  The predicate holds when at least one of the arguments is ground (otherwise, an error message will be displayed). The argument I must be unifiable with a number, and the argument L must be unifiable with an atom representing the number.

`sub_atom(+A,?Bef, ?Size, ?After, ?At_out) [ISO]`

  True when A and At_out are atoms such that the name of At_out has size Size and is a sub-string of the name of A, such that Bef is the number of characters before and After the number of characters afterwards.

  Note that A must always be known, but At_out can be unbound when calling this built-in. If all the arguments for `sub_atom/5` but A are unbound, the built-in will backtrack through all possible sub-strings of A.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.6 Predicates on Characters

The following predicates are used to manipulate characters:

`char_code(?A,?I) [ISO]`

  The built-in succeeds with A bound to character represented as an atom, and I bound to the character code represented as an integer. At least, one of either A or I must be bound before the call.

`char_type(?Char, ?Type)`

  Tests or generates alternative Types or Chars. The character-types are inspired by the standard `C` `<ctype.h>` primitives.

  `alnum`

    Char is a letter (upper- or lowercase) or digit.

  `alpha`

    Char is a letter (upper- or lowercase).

  `csym`

    Char is a letter (upper- or lowercase), digit or the underscore (_). These are valid C- and Prolog symbol characters.

  `csymf`

    Char is a letter (upper- or lowercase) or the underscore (_). These are valid first characters for C- and Prolog symbols

  `ascii`

    Char is a 7-bits ASCII character (0..127).

  `white`

    Char is a space or tab. E.i. white space inside a line.

  `cntrl`

    Char is an ASCII control-character (0..31).

  `digit`

    Char is a digit.

  `digit(Weight)`

    Char is a digit with value Weight. I.e. `char_type(X, digit(6))` yields `X = '6'`. Useful for parsing numbers.

  `xdigit(Weight)`

    Char is a hexa-decimal digit with value Weight. I.e. char_type(a, xdigit(X) yields X = ’10’. Useful for parsing numbers.

  `graph`

    Char produces a visible mark on a page when printed. Note that the space is not included!

  `lower`

    Char is a lower-case letter.

  `lower(Upper)`

    Char is a lower-case version of Upper. Only true if Char is lowercase and Upper uppercase.

  `to_lower(Upper)`

    Char is a lower-case version of Upper. For non-letters, or letter without case, Char and Lower are the same. See also upcase_atom/2 and downcase_atom/2.

  `upper`

    Char is an upper-case letter.

  `upper(Lower)`

    Char is an upper-case version of Lower. Only true if Char is uppercase and Lower lowercase.

  `to_upper(Lower)`

    Char is an upper-case version of Lower. For non-letters, or letter without case, Char and Lower are the same. See also upcase_atom/2 and downcase_atom/2.

  `punct`

    Char is a punctuation character. This is a graph character that is not a letter or digit.

  `space`

    Char is some form of layout character (tab, vertical-tab, newline, etc.).

  `end_of_file`

    Char is -1.

  `end_of_line`

    Char ends a line (ASCII: 10..13).

  `newline`

    Char is a the newline character (10).

  `period`

    Char counts as the end of a sentence (.,!,?).

  `quote`

    Char is a quote-character (", ’, ‘).

  `paren(Close)`

    Char is an open-parenthesis and Close is the corresponding close-parenthesis.

`code_type(?Code, ?Type)`

  As `char_type/2`, but uses character-codes rather than one-character atoms. Please note that both predicates are as flexible as possible. They handle either representation if the argument is instantiated and only will instantiate with an integer code or one-character atom depending of the version used. See also the prolog-flag `double_quotes` and the built-in predicates `atom_chars/2` and `atom_codes/2`.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.7 Comparing Terms

The following predicates are used to compare and order terms, using the standard ordering:

- variables come before numbers, numbers come before atoms which in turn come before compound terms, i.e.: variables @< numbers @< atoms @< compound terms.
- Variables are roughly ordered by "age" (the "oldest" variable is put first);
- Floating point numbers are sorted in increasing order;
- Rational numbers are sorted in increasing order;
- Integers are sorted in increasing order;
- Atoms are sorted in lexicographic order;
- Compound terms are ordered first by arity of the main functor, then by the name of the main functor, and finally by their arguments in left-to-right order.

`compare(C,X,Y)`

  As a result of comparing X and Y, C may take one of the following values:

  - `=` if X and Y are identical;
  - `<` if X precedes Y in the defined order;
  - `>` if Y precedes X in the defined order;
`X == Y [ISO]`

  Succeeds if terms X and Y are strictly identical. The difference between this predicate and `=/2` is that, if one of the arguments is a free variable, it only succeeds when they have already been unified.

      ?- X == Y.

  fails, but,

      ?- X = Y, X == Y.

  succeeds.

      ?- X == 2.

  fails, but,

      ?- X = 2, X == 2.

  succeeds.

`X \== Y [ISO]`

  Terms X and Y are not strictly identical.

`X @< Y [ISO]`

  Term X precedes term Y in the standard order.

`X @=< Y [ISO]`

  Term X does not follow term Y in the standard order.

`X @> Y [ISO]`

  Term X follows term Y in the standard order.

`X @>= Y [ISO]`

  Term X does not precede term Y in the standard order.

`sort(+L,-S)`

  Unifies S with the list obtained by sorting L and merging identical (in the sense of `==`) elements.

`keysort(+L,S)`

  Assuming L is a list of the form `Key-Value`, `keysort(+L,S)` unifies S with the list obtained from L, by sorting its elements according to the value of Key.

      ?- keysort([3-a,1-b,2-c,1-a,1-b],S).

  would return:

      S = [1-b,1-a,1-b,2-c,3-a]

`predsort(+Pred, +List, -Sorted)`

  Sorts similar to sort/2, but determines the order of two terms by calling Pred(-Delta, +E1, +E2) . This call must unify Delta with one of `<`, `>` or `=`. If built-in predicate compare/3 is used, the result is the same as sort/2.

`length(?L,?S)`

  Unify the well-defined list L with its length. The procedure can be used to find the length of a pre-defined list, or to build a list of length S.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.8 Arithmetic

YAP now supports several different numeric types:

`integers`

  When YAP is built using the GNU multiple precision arithmetic library (GMP), integer arithmetic is unbounded, which means that the size of integers is limited by available memory only. Without GMP, SWI-Prolog integers have the same size as an address. The type of integer support can be detected using the Prolog flags bounded, min_integer and max_integer. As the use of GMP is default, most of the following descriptions assume unbounded integer arithmetic.

  Internally, SWI-Prolog has three integer representations. Small integers (defined by the Prolog flag max_tagged_integer) are encoded directly. Larger integers are represented as cell values on the global stack. Integers that do not fit in 64-bit are represented as serialised GNU MPZ structures on the global stack.

`number`

  Rational numbers (Q) are quotients of two integers. Rational arithmetic is only provided if GMP is used (see above). Rational numbers that are returned from is/2 are canonical, which means M is positive and N and M have no common divisors. Rational numbers are introduced in the computation using the rational/1, rationalize/1 or the rdiv/2 (rational division) function.

`float`

  Floating point numbers are represented using the C-type double. On most today platforms these are 64-bit IEEE floating point numbers.

Arithmetic functions that require integer arguments accept, in addition to integers, rational numbers with denominator ‘1’ and floating point numbers that can be accurately converted to integers. If the required argument is a float the argument is converted to float. Note that conversion of integers to floating point numbers may raise an overflow exception. In all other cases, arguments are converted to the same type using the order integer to rational number to floating point number.

Arithmetic expressions in YAP may use the following operators or evaluable predicates:

`+X`

  The value of X itself.

`-X [ISO]`

  Symmetric value.

`X+Y [ISO]`

  Sum.

`X-Y [ISO]`

  Difference.

`X*Y [ISO]`

  Product.

`X/Y [ISO]`

  Quotient.

`X//Y [ISO]`

  Integer quotient.

`X mod Y [ISO]`

  Integer module operator, always positive.

`X rem Y [ISO]`

  Integer remainder, similar to `mod` but always has the same sign `X`.

`X div Y [ISO]`

  Integer division, as if defined by `(X - X mod Y) // Y`.

`exp(X) [ISO]`

  Natural exponential.

`log(X) [ISO]`

  Natural logarithm.

`log10(X)`

  Decimal logarithm.

`sqrt(X) [ISO]`

  Square root.

`sin(X) [ISO]`

  Sine.

`cos(X) [ISO]`

  Cosine.

`tan(X)`

  Tangent.

`asin(X)`

  Arc sine.

`acos(X)`

  Arc cosine.

`atan(X) [ISO]`

  Arc tangent.

`atan(X,Y)`

  Four-quadrant arc tangent. Also available as `atan2/2`.

`sinh(X)`

  Hyperbolic sine.

`cosh(X)`

  Hyperbolic cosine.

`tanh(X)`

  Hyperbolic tangent.

`asinh(X)`

  Hyperbolic arc sine.

`acosh(X)`

  Hyperbolic arc cosine.

`atanh(X)`

  Hyperbolic arc tangent.

`lgamma(X)`

  Logarithm of gamma function.

`erf(X)`

  Gaussian error function.

`erfc(X)`

  Complementary gaussian error function.

`random(X) [ISO]`

  An integer random number between 0 and X.

  In `iso` language mode the argument must be a floating point-number, the result is an integer and it the float is equidistant it is rounded up, that is, to the least integer greater than X.

`integer(X)`

  If X evaluates to a float, the integer between the value of X and 0 closest to the value of X, else if X evaluates to an integer, the value of X.

`float(X) [ISO]`

  If X evaluates to an integer, the corresponding float, else the float itself.

`float_fractional_part(X) [ISO]`

  The fractional part of the floating point number X, or `0.0` if X is an integer. In the `iso` language mode, X must be an integer.

`float_integer_part(X) [ISO]`

  The float giving the integer part of the floating point number X, or X if X is an integer. In the `iso` language mode, X must be an integer.

`abs(X) [ISO]`

  The absolute value of X.

`ceiling(X) [ISO]`

  The integer that is the smallest integral value not smaller than X.

  In `iso` language mode the argument must be a floating point-number and the result is an integer.

`floor(X) [ISO]`

  The integer that is the greatest integral value not greater than X.

  In `iso` language mode the argument must be a floating point-number and the result is an integer.

`round(X) [ISO]`

  The nearest integral value to X. If X is equidistant to two integers, it will be rounded to the closest even integral value.

  In `iso` language mode the argument must be a floating point-number, the result is an integer and it the float is equidistant it is rounded up, that is, to the least integer greater than X.

`sign(X) [ISO]`

  Return 1 if the X evaluates to a positive integer, 0 it if evaluates to 0, and -1 if it evaluates to a negative integer. If X evaluates to a floating-point number return 1.0 for a positive X, 0.0 for 0.0, and -1.0 otherwise.

`truncate(X) [ISO]`

  The integral value between X and 0 closest to X.

`rational(X)`

  Convert the expression X to a rational number or integer. The function returns the input on integers and rational numbers. For floating point numbers, the returned rational number exactly represents the float. As floats cannot exactly represent all decimal numbers the results may be surprising. In the examples below, doubles can represent `0.25` and the result is as expected, in contrast to the result of `rational(0.1)`. The function `rationalize/1` gives a more intuitive result.

      ?- A is rational(0.25).

      A is 1 rdiv 4
      ?- A is rational(0.1).
      A = 3602879701896397 rdiv 36028797018963968

`rationalize(X)`

  Convert the Expr to a rational number or integer. The function is similar to `rational/1`, but the result is only accurate within the rounding error of floating point numbers, generally producing a much smaller denominator.

      ?- A is rationalize(0.25).

      A = 1 rdiv 4
      ?- A is rationalize(0.1).

      A = 1 rdiv 10

`max(X,Y)`

  The greater value of X and Y.

`min(X,Y)`

  The lesser value of X and Y.

`X ^ Y`

  X raised to the power of Y, (from the C-Prolog syntax).

`exp(X,Y)`

  X raised to the power of Y, (from the Quintus Prolog syntax).

`X ** Y [ISO]`

  X raised to the power of Y (from ISO).

`X /\ Y [ISO]`

  Integer bitwise conjunction.

`X \/ Y [ISO]`

  Integer bitwise disjunction.

`X # Y`
`X >< Y`
`xor(X , Y)`

  Integer bitwise exclusive disjunction.

`X << Y`

  Integer bitwise left logical shift of X by Y places.

`X >> Y [ISO]`

  Integer bitwise right logical shift of X by Y places.

`\ X [ISO]`

  Integer bitwise negation.

`gcd(X,Y)`

  The greatest common divisor of the two integers X and Y.

`msb(X)`

  The most significant bit of the non-negative integer X.

`lsb(X)`

  The least significant bit of the non-negative integer X.

`popcount(X)`

  The number of bits set to `1` in the binary representation of the non-negative integer X.

`[X]`

  Evaluates to X for expression X. Useful because character strings in Prolog are lists of character codes.

      X is Y*10+C-"0"

  is the same as

      X is Y*10+C-[48].

  which would be evaluated as:

      X is Y*10+C-48.

Besides numbers and the arithmetic operators described above, certain atoms have a special meaning when present in arithmetic expressions:

`pi`

  The value of pi, the ratio of a circle’s circumference to its diameter.

`e`

  The base of the natural logarithms.

`epsilon`

  The difference between the float `1.0` and the first larger floating point number.

`inf`

  Infinity according to the IEEE Floating-Point standard. Note that evaluating this term will generate a domain error in the `iso` language mode.

`nan`

  Not-a-number according to the IEEE Floating-Point standard. Note that evaluating this term will generate a domain error in the `iso` language mode.

`cputime`

  CPU time in seconds, since YAP was invoked.

`heapused`

  Heap space used, in bytes.

`local`

  Local stack in use, in bytes.

`global`

  Global stack in use, in bytes.

`random`

  A "random" floating point number between 0 and 1.

The primitive YAP predicates involving arithmetic expressions are:

`X is +Y [2]`

  This predicate succeeds iff the result of evaluating the expression Y unifies with X. This is the predicate normally used to perform evaluation of arithmetic expressions:

      X is 2+3*4

  succeeds with `X = 14`.

`+X < +Y [ISO]`

  The value of the expression X is less than the value of expression Y.

`+X =< +Y [ISO]`

  The value of the expression X is less than or equal to the value of expression Y.

`+X > +Y [ISO]`

  The value of the expression X is greater than the value of expression Y.

`+X >= +Y [ISO]`

  The value of the expression X is greater than or equal to the value of expression Y.

`+X =:= +Y [ISO]`

  The value of the expression X is equal to the value of expression Y.

`+X =\= +Y [ISO]`

  The value of the expression X is different from the value of expression Y.

`srandom(+X)`

  Use the argument X as a new seed for YAP’s random number generator. The argument should be an integer, but floats are acceptable.

Notes:

- Since YAP4, YAP does not convert automatically between integers and floats.
- arguments to trigonometric functions are expressed in radians.
- if a (non-instantiated) variable occurs in an arithmetic expression YAP will generate an exception. If no error handler is available, execution will be thrown back to the top-level.

The following predicates provide counting:

`between(+Low, +High, ?Value)`

  Low and High are integers, High >=Low. If Value is an integer, Low =<Value =<High. When Value is a variable it is successively bound to all integers between Low and High. If High is inf or infinite `between/3` is true iff Value >= Low, a feature that is particularly interesting for generating integers from a certain value.

`succ(?Int1, ?Int2)`

  True if Int2 = Int1 + 1 and Int1 >= 0. At least one of the arguments must be instantiated to a natural number. This predicate raises the domain-error not_less_than_zero if called with a negative integer. E.g. `succ(X, 0)` fails silently and succ(X, -1) raises a domain-error. The behaviour to deal with natural numbers only was defined by Richard O’Keefe to support the common count-down-to-zero in a natural way.

`plus(?Int1, ?Int2, ?Int3)`

  True if Int3 = Int1 + Int2. At least two of the three arguments must be instantiated to integers.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.9 I/O Predicates

Some of the I/O predicates described below will in certain conditions provide error messages and abort only if the file_errors flag is set. If this flag is cleared the same predicates will just fail. Details on setting and clearing this flag are given under 7.7.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.9.1 Handling Streams and Files

`open(+F,+M,-S) [ISO]`

  Opens the file with name F in mode M (’read’, ’write’ or ’append’), returning S unified with the stream name.

  At most, there are 17 streams opened at the same time. Each stream is either an input or an output stream but not both. There are always 3 open streams: `user_input` for reading, `user_output` for writing and `user_error` for writing. If there is no ambiguity, the atoms `user_input` and `user_output` may be referred to as `user`.

  The `file_errors` flag controls whether errors are reported when in mode ’read’ or ’append’ the file F does not exist or is not readable, and whether in mode ’write’ or ’append’ the file is not writable.

`open(+F,+M,-S,+Opts) [ISO]`

  Opens the file with name F in mode M (’read’, ’write’ or ’append’), returning S unified with the stream name, and following these options:

  `type(+T) [ISO]`

    Specify whether the stream is a `text` stream (default), or a `binary` stream.

  `reposition(+Bool) [ISO]`

    Specify whether it is possible to reposition the stream (`true`), or not (`false`). By default, YAP enables repositioning for all files, except terminal files and sockets.

  `eof_action(+Action) [ISO]`

    Specify the action to take if attempting to input characters from a stream where we have previously found an `end_of_file`. The possible actions are `error`, that raises an error, `reset`, that tries to reset the stream and is used for `tty` type files, and `eof_code`, which generates a new `end_of_file` (default for non-tty files).

  `alias(+Name) [ISO]`

    Specify an alias to the stream. The alias `Name` must be an atom. The alias can be used instead of the stream descriptor for every operation concerning the stream.

    The operation will fail and give an error if the alias name is already in use. YAP allows several aliases for the same file, but only one is returned by `stream_property/2`

  `bom(+Bool)`

    If present and `true`, a BOM (Byte Order Mark) was detected while opening the file for reading or a BOM was written while opening the stream. See BOM: Byte Order Mark for details.

  `encoding(+Encoding)`

    Set the encoding used for text. See Wide Character Support for an overview of wide character and encoding issues.

  `representation_errors(+Mode)`

    Change the behaviour when writing characters to the stream that cannot be represented by the encoding. The behaviour is one of `error` (throw and I/O error exception), `prolog` (write `\u...\` escape code or `xml` (write `&#...;` XML character entity). The initial mode is `prolog` for the user streams and `error` for all other streams. See also Wide Character Support.

  `expand_filename(+Mode)`

    If Mode is `true` then do filename expansion, then ask Prolog to do file name expansion before actually trying to opening the file: this includes processing `~` characters and processing `$` environment variables at the beginning of the file. Otherwise, just try to open the file using the given name.

    The default behavior is given by the Prolog flag `open_expands_filename`.

`close(+S) [ISO]`

  Closes the stream S. If S does not stand for a stream currently opened an error is reported. The streams `user_input`, `user_output`, and `user_error` can never be closed.

`close(+S,+O) [ISO]`

  Closes the stream S, following options O.

  The only valid options are `force(true)` and `force(false)`. YAP currently ignores these options.

`time_file(+File,-Time)`

  Unify the last modification time of File with Time. Time is a floating point number expressing the seconds elapsed since Jan 1, 1970.

`absolute_file_name(+Name,+Options, -FullPath)`
`absolute_file_name(+Name, -FullPath,+Options)`

  Converts the given file specification into an absolute path. Option is a list of options to guide the conversion:

  `extensions(+ListOfExtensions)`

    List of file-extensions to try. Default is ‘`''`’. For each extension, `absolute_file_name/3` will first add the extension and then verify the conditions imposed by the other options. If the condition fails, the next extension of the list is tried. Extensions may be specified both as `.ext` or plain `ext`.

  `relative_to(+FileOrDir)`

    Resolve the path relative to the given directory or directory the holding the given file. Without this option, paths are resolved relative to the working directory (see `working_directory/2`) or, if Spec is atomic and `absolute_file_name/[2,3]` is executed in a directive, it uses the current source-file as reference.

  `access(+Mode)`

    Imposes the condition access_file(File, Mode). Mode is on of `read`, `write`, `append`, `exist` or `none` (default). See also `access_file/2`.

  `file_type(+Type)`

    Defines extensions. Current mapping: `txt` implies `['']`, `prolog` implies `['.pl', '']`, `executable` implies `['.so', '']`, `qlf` implies `['.qlf', '']` and `directory` implies `['']`. The file-type `source` is an alias for `prolog` for compatibility to SICStus Prolog. See also `prolog_file_type/2`. Notice also that this predicate only returns non-directories, unless the option `file_type(directory)` is specified, or unless `access(none)`.

  `file_errors(`fail`/`error`)`

    If `error` (default), throw and `existence_error` exception if the file cannot be found. If `fail`, stay silent.

  `solutions(`first`/`all`)`

    If `first` (default), the predicates leaves no choice-point. Otherwise a choice-point will be left and backtracking may yield more solutions.

  Compatibility considerations to common argument-order in ISO as well as SICStus `absolute_file_name/3` forced us to be flexible here. If the last argument is a list and the 2nd not, the arguments are swapped, making the call `absolute_file_name`(+Spec, -Path, +Options) valid as well.

`absolute_file_name(+Name,-FullPath)`

  Give the path a full path FullPath YAP would use to consult a file named Name. Unify FullPath with `user` if the file name is `user`.

`file_base_name(+Name,-FileName)`

  Give the path a full path FullPath extract the FileName.

`file_name_extension(?Base,?Extension, ?Name)`

  This predicate is used to add, remove or test filename extensions. The main reason for its introduction is to deal with different filename properties in a portable manner. If the file system is case-insensitive, testing for an extension will be done case-insensitive too. Extension may be specified with or without a leading dot (.). If an Extension is generated, it will not have a leading dot.

`current_stream(F,M,S)`

  Defines the relation: The stream S is opened on the file F in mode M. It might be used to obtain all open streams (by backtracking) or to access the stream for a file F in mode M, or to find properties for a stream S.

`is_stream(S)`

  Succeeds if S is a currently open stream.

`flush_output [ISO]`

  Send out all data in the output buffer of the current output stream.

`flush_output(+S) [ISO]`

  Send all data in the output buffer for stream S.

`set_input(+S) [ISO]`

  Set stream S as the current input stream. Predicates like `read/1` and `get/1` will start using stream S.

`set_output(+S) [ISO]`

  Set stream S as the current output stream. Predicates like `write/1` and `put/1` will start using stream S.

`stream_select(+STREAMS,+TIMEOUT,-READSTREAMS)`

  Given a list of open STREAMS opened in read mode and a TIMEOUT return a list of streams who are now available for reading.

  If the TIMEOUT is instantiated to `off`, `stream_select/3` will wait indefinitely for a stream to become open. Otherwise the timeout must be of the form `SECS:USECS` where `SECS` is an integer gives the number of seconds to wait for a timeout and `USECS` adds the number of micro-seconds.

  This built-in is only defined if the system call `select` is available in the system.

`current_input(-S) [ISO]`

  Unify S with the current input stream.

`current_output(-S) [ISO]`

  Unify S with the current output stream.

`at_end_of_stream [ISO]`

  Succeed if the current stream has stream position end-of-stream or past-end-of-stream.

`at_end_of_stream(+S) [ISO]`

  Succeed if the stream S has stream position end-of-stream or past-end-of-stream. Note that S must be a readable stream.

`set_stream_position(+S, +POS) [ISO]`

  Given a stream position POS for a stream S, set the current stream position for S to be POS.

`stream_property(?Stream,?Prop) [ISO]`

  Obtain the properties for the open streams. If the first argument is unbound, the procedure will backtrack through all open streams. Otherwise, the first argument must be a stream term (you may use `current_stream` to obtain a current stream given a file name).

  The following properties are recognized:

  `file_name(P)`

    An atom giving the file name for the current stream. The file names are `user_input`, `user_output`, and `user_error` for the standard streams.

  `mode(P)`

    The mode used to open the file. It may be one of `append`, `read`, or `write`.

  `input`

    The stream is readable.

  `output`

    The stream is writable.

  `alias(A)`

    ISO-Prolog primitive for stream aliases. `YAP` returns one of the existing aliases for the stream.

  `position(P)`

    A term describing the position in the stream.

  `end_of_stream(E)`

    Whether the stream is `at` the end of stream, or it has found the end of stream and is `past`, or whether it has `not` yet reached the end of stream.

  `eof_action(A)`

    The action to take when trying to read after reaching the end of stream. The action may be one of `error`, generate an error, `eof_code`, return character code `-1`, or `reset` the stream.

  `reposition(B)`

    Whether the stream can be repositioned or not, that is, whether it is seekable.

  `type(T)`

    Whether the stream is a `text` stream or a `binary` stream.

  `bom(+Bool)`

    If present and `true`, a BOM (Byte Order Mark) was detected while opening the file for reading or a BOM was written while opening the stream. See BOM: Byte Order Mark for details.

  `encoding(+Encoding)`

    Query the encoding used for text. See Wide Character Support for an overview of wide character and encoding issues in YAP.

  `representation_errors(+Mode)`

    Behaviour when writing characters to the stream that cannot be represented by the encoding. The behaviour is one of `error` (throw and I/O error exception), `prolog` (write `\u...\` escape code or `xml` (write `&#...;` XML character entity). The initial mode is `prolog` for the user streams and `error` for all other streams. See also Wide Character Support and `open/4`.

`current_line_number(-LineNumber)`

  Unify LineNumber with the line number for the current stream.

`current_line_number(+Stream,-LineNumber)`

  Unify LineNumber with the line number for the Stream.

`line_count(+Stream,-LineNumber)`

  Unify LineNumber with the line number for the Stream.

`character_count(+Stream,-CharacterCount)`

  Unify CharacterCount with the number of characters written to or read to Stream.

`line_position(+Stream,-LinePosition)`

  Unify LinePosition with the position on current text stream Stream.

`stream_position(+Stream,-StreamPosition)`

  Unify StreamPosition with the packaged information of position on current stream Stream. Use `stream_position_data/3` to retrieve information on character or line count.

`stream_position_data(+Field,+StreamPosition,-Info)`

  Given the packaged stream position term StreamPosition, unify Info with Field `line_count`, `byte_count`, or `char_count`.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.9.2 Handling Streams and Files

`tell(+S)`

  If S is a currently opened stream for output, it becomes the current output stream. If S is an atom it is taken to be a filename. If there is no output stream currently associated with it, then it is opened for output, and the new output stream created becomes the current output stream. If it is not possible to open the file, an error occurs. If there is a single opened output stream currently associated with the file, then it becomes the current output stream; if there are more than one in that condition, one of them is chosen.

  Whenever S is a stream not currently opened for output, an error may be reported, depending on the state of the file_errors flag. The predicate just fails, if S is neither a stream nor an atom.

`telling(-S)`

  The current output stream is unified with S.

`told`

  Closes the current output stream, and the user’s terminal becomes again the current output stream. It is important to remember to close streams after having finished using them, as the maximum number of simultaneously opened streams is 17.

`see(+S)`

  If S is a currently opened input stream then it is assumed to be the current input stream. If S is an atom it is taken as a filename. If there is no input stream currently associated with it, then it is opened for input, and the new input stream thus created becomes the current input stream. If it is not possible to open the file, an error occurs. If there is a single opened input stream currently associated with the file, it becomes the current input stream; if there are more than one in that condition, then one of them is chosen.

  When S is a stream not currently opened for input, an error may be reported, depending on the state of the `file_errors` flag. If S is neither a stream nor an atom the predicates just fails.

`seeing(-S)`

  The current input stream is unified with S.

`seen`

  Closes the current input stream (see 6.7.).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.9.3 Handling Input/Output of Terms

`read(-T) [ISO]`

  Reads the next term from the current input stream, and unifies it with T. The term must be followed by a dot (’.’) and any blank-character as previously defined. The syntax of the term must match the current declarations for operators (see op). If the end-of-stream is reached, T is unified with the atom `end_of_file`. Further reads from of the same stream may cause an error failure (see `open/3`).

`read_term(-T,+Options) [ISO]`

  Reads term T from the current input stream with execution controlled by the following options:

  `term_position(-Position)`

    Unify Position with a term describing the position of the stream at the start of parse. Use `stream_position_data/3` to obtain extra information.

  `singletons(-Names)`

    Unify Names with a list of the form Name=Var, where Name is the name of a non-anonymous singleton variable in the original term, and `Var` is the variable’s representation in YAP.

  `syntax_errors(+Val)`

    Control action to be taken after syntax errors. See `yap_flag/2` for detailed information.

  `variable_names(-Names)`

    Unify Names with a list of the form Name=Var, where Name is the name of a non-anonymous variable in the original term, and Var is the variable’s representation in YAP.

  `variables(-Names)`

    Unify Names with a list of the variables in term T.

`char_conversion(+IN,+OUT) [ISO]`

  While reading terms convert unquoted occurrences of the character IN to the character OUT. Both IN and OUT must be bound to single characters atoms.

  Character conversion only works if the flag `char_conversion` is on. This is default in the `iso` and `sicstus` language modes. As an example, character conversion can be used for instance to convert characters from the ISO-LATIN-1 character set to ASCII.

  If IN is the same character as OUT, `char_conversion/2` will remove this conversion from the table.

`current_char_conversion(?IN,?OUT) [ISO]`

  If IN is unbound give all current character translations. Otherwise, give the translation for IN, if one exists.

`write(T) [ISO]`

  The term T is written to the current output stream according to the operator declarations in force.

`writeln(T) [ISO]`

  Same as `write/1` followed by `nl/0`.

`display(+T)`

  Displays term T on the current output stream. All Prolog terms are written in standard parenthesized prefix notation.

`write_canonical(+T) [ISO]`

  Displays term T on the current output stream. Atoms are quoted when necessary, and operators are ignored, that is, the term is written in standard parenthesized prefix notation.

`write_term(+T, +Opts) [ISO]`

  Displays term T on the current output stream, according to the following options:

  `quoted(+Bool) [ISO]`

    If `true`, quote atoms if this would be necessary for the atom to be recognized as an atom by YAP’s parser. The default value is `false`.

  `ignore_ops(+Bool) [ISO]`

    If `true`, ignore operator declarations when writing the term. The default value is `false`.

  `numbervars(+Bool) [ISO]`

    If `true`, output terms of the form `'$VAR'(N)`, where N is an integer, as a sequence of capital letters. The default value is `false`.

  `portrayed(+Bool)`

    If `true`, use `portray/1` to portray bound terms. The default value is `false`.

  `portray(+Bool)`

    If `true`, use `portray/1` to portray bound terms. The default value is `false`.

  `max_depth(+Depth)`

    If `Depth` is a positive integer, use `Depth` as the maximum depth to portray a term. The default is `0`, that is, unlimited depth.

  `priority(+Piority)`

    If `Priority` is a positive integer smaller than `1200`, give the context priority. The default is `1200`.

  `cycles(+Bool)`

    Do not loop in rational trees (default).

`writeq(T) [ISO]`

  Writes the term T, quoting names to make the result acceptable to the predicate ’read’ whenever necessary.

`print(T)`

  Prints the term T to the current output stream using `write/1` unless T is bound and a call to the user-defined predicate `portray/1` succeeds. To do pretty printing of terms the user should define suitable clauses for `portray/1` and use `print/1`.

`format(+T,+L)`

  Print formatted output to the current output stream. The arguments in list L are output according to the string or atom T.

  A control sequence is introduced by a `w`. The following control sequences are available in YAP:

  `'~~'`

    Print a single tilde.

  `'~a'`

    The next argument must be an atom, that will be printed as if by `write`.

  `'~Nc'`

    The next argument must be an integer, that will be printed as a character code. The number N is the number of times to print the character (default 1).

  `'~Ne'`
  `'~NE'`
  `'~Nf'`
  `'~Ng'`
  `'~NG'`

    The next argument must be a floating point number. The float F, the number N and the control code `c` will be passed to `printf` as:

            printf("%s.Nc", F)

    As an example:

        ?- format("~8e, ~8E, ~8f, ~8g, ~8G~w",
                  [3.14,3.14,3.14,3.14,3.14,3.14]).
        3.140000e+00, 3.140000E+00, 3.140000, 3.14, 3.143.14

  `'~Nd'`

    The next argument must be an integer, and N is the number of digits after the decimal point. If N is `0` no decimal points will be printed. The default is N = 0.

        ?- format("~2d, ~d",[15000, 15000]).
        150.00, 15000

  `'~ND'`

    Identical to `'~Nd'`, except that commas are used to separate groups of three digits.

        ?- format("~2D, ~D",[150000, 150000]).
        1,500.00, 150,000

  `'~i'`

    Ignore the next argument in the list of arguments:

        ?- format('The ~i met the boregrove',[mimsy]).
        The  met the boregrove

  `'~k'`

    Print the next argument with `write_canonical`:

        ?- format("Good night ~k",a+[1,2]).
        Good night +(a,[1,2])

  `'~Nn'`

    Print N newlines (where N defaults to 1).

  `'~NN'`

    Print N newlines if at the beginning of the line (where N defaults to 1).

  `'~Nr'`

    The next argument must be an integer, and N is interpreted as a radix, such that `2 <= N <= 36` (the default is 8).

        ?- format("~2r, 0x~16r, ~r",
                  [150000, 150000, 150000]).
        100100100111110000, 0x249f0, 444760

    Note that the letters `a-z` denote digits larger than 9.

  `'~NR'`

    Similar to ’~NR’. The next argument must be an integer, and N is interpreted as a radix, such that `2 <= N <= 36` (the default is 8).

        ?- format("~2r, 0x~16r, ~r",
                  [150000, 150000, 150000]).
        100100100111110000, 0x249F0, 444760

    The only difference is that letters `A-Z` denote digits larger than 9.

  `'~p'`

    Print the next argument with `print/1`:

        ?- format("Good night ~p",a+[1,2]).
        Good night a+[1,2]

  `'~q'`

    Print the next argument with `writeq/1`:

        ?- format("Good night ~q",'Hello'+[1,2]).
        Good night 'Hello'+[1,2]

  `'~Ns'`

    The next argument must be a list of character codes. The system then outputs their representation as a string, where N is the maximum number of characters for the string (N defaults to the length of the string).

        ?- format("The ~s are ~4s",["woods","lovely"]).
        The woods are love

  `'~w'`

    Print the next argument with `write/1`:

        ?- format("Good night ~w",'Hello'+[1,2]).
        Good night Hello+[1,2]

  The number of arguments, `N`, may be given as an integer, or it may be given as an extra argument. The next example shows a small procedure to write a variable number of `a` characters:

      write_many_as(N) :-
              format("~*c",[N,0'a]).

  The `format/2` built-in also allows for formatted output. One can specify column boundaries and fill the intermediate space by a padding character:

  `'~N|'`

    Set a column boundary at position N, where N defaults to the current position.

  `'~N+'`

    Set a column boundary at N characters past the current position, where N defaults to `8`.

  `'~Nt'`

    Set padding for a column, where N is the fill code (default is <SPC>).

  The next example shows how to align columns and padding. We first show left-alignment:

         ?- format("~n*Hello~16+*~n",[]).
      *Hello          *

  Note that we reserve 16 characters for the column.

  The following example shows how to do right-alignment:

         ?- format("*~tHello~16+*~n",[]).
      *          Hello*

  The `~t` escape sequence forces filling before `Hello`.

  We next show how to do centering:

         ?- format("*~tHello~t~16+*~n",[]).
      *     Hello     *

  The two `~t` escape sequence force filling both before and after `Hello`. Space is then evenly divided between the right and the left sides.

`format(+T)`

  Print formatted output to the current output stream.

`format(+S,+T,+L)`

  Print formatted output to stream S.

`with_output_to(+Ouput,:Goal)`

  Run Goal as `once/1`, while characters written to the current output are sent to Output. The predicate is SWI-Prolog specific.

  Applications should generally avoid creating atoms by breaking and concatenating other atoms as the creation of large numbers of intermediate atoms generally leads to poor performance, even more so in multi-threaded applications. This predicate supports creating difference-lists from character data efficiently. The example below defines the DCG rule `term/3` to insert a term in the output:

       term(Term, In, Tail) :-
              with_output_to(codes(In, Tail), write(Term)).

      ?- phrase(term(hello), X).

      X = [104, 101, 108, 108, 111]

  `A Stream handle or alias`

    Temporary switch current output to the given stream. Redirection using with_output_to/2 guarantees the original output is restored, also if Goal fails or raises an exception. See also call_cleanup/2.

  `atom(-Atom)`

    Create an atom from the emitted characters. Please note the remark above.

  `string(-String)`

    Create a string-object (not supported in YAP).

  `codes(-Codes)`

    Create a list of character codes from the emitted characters, similar to atom_codes/2.

  `codes(-Codes, -Tail)`

    Create a list of character codes as a difference-list.

  `chars(-Chars)`

    Create a list of one-character-atoms codes from the emitted characters, similar to atom_chars/2.

  `chars(-Chars, -Tail)`

    Create a list of one-character-atoms as a difference-list.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.9.4 Handling Input/Output of Characters

`put(+N)`

  Outputs to the current output stream the character whose ASCII code is N. The character N must be a legal ASCII character code, an expression yielding such a code, or a list in which case only the first element is used.

`put_byte(+N) [ISO]`

  Outputs to the current output stream the character whose code is N. The current output stream must be a binary stream.

`put_char(+N) [ISO]`

  Outputs to the current output stream the character who is used to build the representation of atom `A`. The current output stream must be a text stream.

`put_code(+N) [ISO]`

  Outputs to the current output stream the character whose ASCII code is N. The current output stream must be a text stream. The character N must be a legal ASCII character code, an expression yielding such a code, or a list in which case only the first element is used.

`get(-C)`

  The next non-blank character from the current input stream is unified with C. Blank characters are the ones whose ASCII codes are not greater than 32. If there are no more non-blank characters in the stream, C is unified with -1. If `end_of_stream` has already been reached in the previous reading, this call will give an error message.

`get0(-C)`

  The next character from the current input stream is consumed, and then unified with C. There are no restrictions on the possible values of the ASCII code for the character, but the character will be internally converted by YAP.

`get_byte(-C) [ISO]`

  If C is unbound, or is a character code, and the current stream is a binary stream, read the next byte from the current stream and unify its code with C.

`get_char(-C) [ISO]`

  If C is unbound, or is an atom representation of a character, and the current stream is a text stream, read the next character from the current stream and unify its atom representation with C.

`get_code(-C) [ISO]`

  If C is unbound, or is the code for a character, and the current stream is a text stream, read the next character from the current stream and unify its code with C.

`peek_byte(-C) [ISO]`

  If C is unbound, or is a character code, and the current stream is a binary stream, read the next byte from the current stream and unify its code with C, while leaving the current stream position unaltered.

`peek_char(-C) [ISO]`

  If C is unbound, or is an atom representation of a character, and the current stream is a text stream, read the next character from the current stream and unify its atom representation with C, while leaving the current stream position unaltered.

`peek_code(-C) [ISO]`

  If C is unbound, or is the code for a character, and the current stream is a text stream, read the next character from the current stream and unify its code with C, while leaving the current stream position unaltered.

`skip(+N)`

  Skips input characters until the next occurrence of the character with ASCII code N. The argument to this predicate can take the same forms as those for `put` (see 6.11).

`tab(+N)`

  Outputs N spaces to the current output stream.

`nl [ISO]`

  Outputs a new line to the current output stream.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.9.5 Input/Output Predicates applied to Streams

`read(+S,-T) [ISO]`

  Reads term T from the stream S instead of from the current input stream.

`read_term(+S,-T,+Options) [ISO]`

  Reads term T from stream S with execution controlled by the same options as `read_term/2`.

`write(+S,T) [ISO]`

  Writes term T to stream S instead of to the current output stream.

`write_canonical(+S,+T) [ISO]`

  Displays term T on the stream S. Atoms are quoted when necessary, and operators are ignored.

`write_canonical(+T) [ISO]`

  Displays term T. Atoms are quoted when necessary, and operators are ignored.

`write_term(+S, +T, +Opts) [ISO]`

  Displays term T on the current output stream, according to the same options used by `write_term/3`.

`writeq(+S,T) [ISO]`

  As `writeq/1`, but the output is sent to the stream S.

`display(+S,T)`

  Like `display/1`, but using stream S to display the term.

`print(+S,T)`

  Prints term T to the stream S instead of to the current output stream.

`put(+S,+N)`

  As `put(N)`, but to stream S.

`put_byte(+S,+N) [ISO]`

  As `put_byte(N)`, but to binary stream S.

`put_char(+S,+A) [ISO]`

  As `put_char(A)`, but to text stream S.

`put_code(+S,+N) [ISO]`

  As `put_code(N)`, but to text stream S.

`get(+S,-C)`

  The same as `get(C)`, but from stream S.

`get0(+S,-C)`

  The same as `get0(C)`, but from stream S.

`get_byte(+S,-C) [ISO]`

  If C is unbound, or is a character code, and the stream S is a binary stream, read the next byte from that stream and unify its code with C.

`get_char(+S,-C) [ISO]`

  If C is unbound, or is an atom representation of a character, and the stream S is a text stream, read the next character from that stream and unify its representation as an atom with C.

`get_code(+S,-C) [ISO]`

  If C is unbound, or is a character code, and the stream S is a text stream, read the next character from that stream and unify its code with C.

`peek_byte(+S,-C) [ISO]`

  If C is unbound, or is a character code, and S is a binary stream, read the next byte from the current stream and unify its code with C, while leaving the current stream position unaltered.

`peek_char(+S,-C) [ISO]`

  If C is unbound, or is an atom representation of a character, and the stream S is a text stream, read the next character from that stream and unify its representation as an atom with C, while leaving the current stream position unaltered.

`peek_code(+S,-C) [ISO]`

  If C is unbound, or is an atom representation of a character, and the stream S is a text stream, read the next character from that stream and unify its representation as an atom with C, while leaving the current stream position unaltered.

`skip(+S,-C)`

  Like `skip/1`, but using stream S instead of the current input stream.

`tab(+S,+N)`

  The same as `tab/1`, but using stream S.

`nl(+S) [ISO]`

  Outputs a new line to stream S.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.9.6 Compatible C-Prolog predicates for Terminal I/O

`ttyput(+N)`

  As `put(N)` but always to `user_output`.

`ttyget(-C)`

  The same as `get(C)`, but from stream `user_input`.

`ttyget0(-C)`

  The same as `get0(C)`, but from stream `user_input`.

`ttyskip(-C)`

  Like `skip/1`, but always using stream `user_input`. stream.

`ttytab(+N)`

  The same as `tab/1`, but using stream `user_output`.

`ttynl`

  Outputs a new line to stream `user_output`.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.9.7 Controlling Input/Output

`exists(+F)`

  Checks if file F exists in the current directory.

`nofileerrors`

  Switches off the file_errors flag, so that the predicates `see/1`, `tell/1`, `open/3` and `close/1` just fail, instead of producing an error message and aborting whenever the specified file cannot be opened or closed.

`fileerrors`

  Switches on the file_errors flag so that in certain error conditions I/O predicates will produce an appropriated message and abort.

`write_depth(T,L,A)`

  Unifies T with the value of the maximum depth of a term to be written, L with the maximum length of a list to write, and A with the maximum number of arguments of a compound term to write. The setting will be used by `write/1` or `write/2`. The default value for all arguments is 0, meaning unlimited depth and length.

      ?- write_depth(3,5,5).
      yes
      ?- write(a(b(c(d(e(f(g))))))).
      a(b(c(....)))
      yes
      ?- write([1,2,3,4,5,6,7,8]).
      [1,2,3,4,5,...]
      yes
      ?- write(a(1,2,3,4,5,6,7,8)).
      a(1,2,3,4,5,...)
      yes

`write_depth(T,L)`

  Same as `write_depth(T,L,_)`. Unifies T with the value of the maximum depth of a term to be written, and L with the maximum length of a list to write. The setting will be used by `write/1` or `write/2`. The default value for all arguments is 0, meaning unlimited depth and length.

      ?- write_depth(3,5,5).
      yes
      ?- write(a(b(c(d(e(f(g))))))).
      a(b(c(....)))
      yes
      ?- write([1,2,3,4,5,6,7,8]).
      [1,2,3,4,5,...]
      yes

`always_prompt_user`

  Force the system to prompt the user even if the `user_input` stream is not a terminal. This command is useful if you want to obtain interactive control from a pipe or a socket.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.9.8 Using Sockets From YAP

YAP includes a SICStus Prolog compatible socket interface. This is a low level interface that provides direct access to the major socket system calls. These calls can be used both to open a new connection in the network or connect to a networked server. Socket connections are described as read/write streams, and standard I/O built-ins can be used to write on or read from sockets. The following calls are available:

`socket(+DOMAIN,+TYPE,+PROTOCOL,-SOCKET)`

  Corresponds to the BSD system call `socket`. Create a socket for domain DOMAIN of type TYPE and protocol PROTOCOL. Both DOMAIN and TYPE should be atoms, whereas PROTOCOL must be an integer. The new socket object is accessible through a descriptor bound to the variable SOCKET.

  The current implementation of YAP only accepts two socket domains: `'AF_INET'` and `'AF_UNIX'`. Socket types depend on the underlying operating system, but at least the following types are supported: `'SOCK_STREAM'` and `'SOCK_DGRAM'`.

`socket(+DOMAIN,-SOCKET)`

  Call `socket/4` with TYPE bound to `'SOCK_STREAM'` and PROTOCOL bound to `0`.

`socket_close(+SOCKET)`

  Close socket SOCKET. Note that sockets used in `socket_connect` (that is, client sockets) should not be closed with `socket_close`, as they will be automatically closed when the corresponding stream is closed with `close/1` or `close/2`.

`socket_bind(+SOCKET, ?PORT)`

  Interface to system call `bind`, as used for servers: bind socket to a port. Port information depends on the domain:

  `'AF_UNIX'(+FILENAME)`
  `'AF_FILE'(+FILENAME)`

    use file name FILENAME for UNIX or local sockets.

  `'AF_INET'(?HOST,?PORT)`

    If HOST is bound to an atom, bind to host HOST, otherwise if unbound bind to local host (HOST remains unbound). If port PORT is bound to an integer, try to bind to the corresponding port. If variable PORT is unbound allow operating systems to choose a port number, which is unified with PORT.

`socket_connect(+SOCKET, +PORT, -STREAM)`

  Interface to system call `connect`, used for clients: connect socket SOCKET to PORT. The connection results in the read/write stream STREAM.

  Port information depends on the domain:

  `'AF_UNIX'(+FILENAME)`
  `'AF_FILE'(+FILENAME)`

    connect to socket at file FILENAME.

  `'AF_INET'(+HOST,+PORT)`

    Connect to socket at host HOST and port PORT.

`socket_listen(+SOCKET, +LENGTH)`

  Interface to system call `listen`, used for servers to indicate willingness to wait for connections at socket SOCKET. The integer LENGTH gives the queue limit for incoming connections, and should be limited to `5` for portable applications. The socket must be of type `SOCK_STREAM` or `SOCK_SEQPACKET`.

`socket_accept(+SOCKET, -STREAM)`
`socket_accept(+SOCKET, -CLIENT, -STREAM)`

  Interface to system call `accept`, used for servers to wait for connections at socket SOCKET. The stream descriptor STREAM represents the resulting connection. If the socket belongs to the domain `'AF_INET'`, CLIENT unifies with an atom containing the IP address for the client in numbers and dots notation.

`socket_accept(+SOCKET, -STREAM)`

  Accept a connection but do not return client information.

`socket_buffering(+SOCKET, -MODE, -OLD, +NEW)`

  Set buffering for SOCKET in `read` or `write` MODE. OLD is unified with the previous status, and NEW receives the new status which may be one of `unbuf` or `fullbuf`.

`socket_select(+SOCKETS, -NEWSTREAMS, +TIMEOUT, +STREAMS, -READSTREAMS)`

  Interface to system call `select`, used for servers to wait for connection requests or for data at sockets. The variable SOCKETS is a list of form KEY-SOCKET, where KEY is an user-defined identifier and SOCKET is a socket descriptor. The variable TIMEOUT is either `off`, indicating execution will wait until something is available, or of the form SEC-USEC, where SEC and USEC give the seconds and microseconds before `socket_select/5` returns. The variable SOCKETS is a list of form KEY-STREAM, where KEY is an user-defined identifier and STREAM is a stream descriptor

  Execution of `socket_select/5` unifies READSTREAMS from STREAMS with readable data, and NEWSTREAMS with a list of the form KEY-STREAM, where KEY was the key for a socket with pending data, and STREAM the stream descriptor resulting from accepting the connection.

`current_host(?HOSTNAME)`

  Unify HOSTNAME with an atom representing the fully qualified hostname for the current host. Also succeeds if HOSTNAME is bound to the unqualified hostname.

`hostname_address(?HOSTNAME,?IP_ADDRESS)`

  HOSTNAME is an host name and IP_ADDRESS its IP address in number and dots notation.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.10 Using the Clausal Data Base

Predicates in YAP may be dynamic or static. By default, when consulting or reconsulting, predicates are assumed to be static: execution is faster and the code will probably use less space. Static predicates impose some restrictions: in general there can be no addition or removal of clauses for a procedure if it is being used in the current execution.

Dynamic predicates allow programmers to change the Clausal Data Base with the same flexibility as in C-Prolog. With dynamic predicates it is always possible to add or remove clauses during execution and the semantics will be the same as for C-Prolog. But the programmer should be aware of the fact that asserting or retracting are still expensive operations, and therefore he should try to avoid them whenever possible.

`dynamic +P`

  Declares predicate P or list of predicates [P1,...,Pn] as a dynamic predicate. P must be written in form: name/arity.

      :- dynamic god/1.

  a more convenient form can be used:

      :- dynamic son/3, father/2, mother/2.

  or, equivalently,

      :- dynamic [son/3, father/2, mother/2].

  Note:

  a predicate is assumed to be dynamic when asserted before being defined.

`dynamic_predicate(+P,+Semantics)`

  Declares predicate P or list of predicates [P1,...,Pn] as a dynamic predicate following either `logical` or `immediate` semantics.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.10.1 Modification of the Data Base

These predicates can be used either for static or for dynamic predicates:

`assert(+C)`

  Same as `assertz/1`. Adds clause C to the program. If the predicate is undefined, declare it as dynamic. New code should use `assertz/1` for better portability.

  Most Prolog systems only allow asserting clauses for dynamic predicates. This is also as specified in the ISO standard. YAP allows asserting clauses for static predicates, as long as the predicate is not in use and the language flag is `cprolog`. Note that this feature is deprecated, if you want to assert clauses for static procedures you should use `assert_static/1`.

`asserta(+C) [ISO]`

  Adds clause C to the beginning of the program. If the predicate is undefined, declare it as dynamic.

`assertz(+C) [ISO]`

  Adds clause C to the end of the program. If the predicate is undefined, declare it as dynamic.

  Most Prolog systems only allow asserting clauses for dynamic predicates. This is also as specified in the ISO standard. YAP allows asserting clauses for static predicates. The current version of YAP supports this feature, but this feature is deprecated and support may go away in future versions.

`abolish(+PredSpec) [ISO]`

  Deletes the predicate given by PredSpec from the database. If PredSpec is an unbound variable, delete all predicates for the current module. The specification must include the name and arity, and it may include module information. Under `iso` language mode this built-in will only abolish dynamic procedures. Under other modes it will abolish any procedures.

`abolish(+P,+N)`

  Deletes the predicate with name P and arity N. It will remove both static and dynamic predicates.

`assert_static(:C)`

  Adds clause C to a static procedure. Asserting a static clause for a predicate while choice-points for the predicate are available has undefined results.

`asserta_static(:C)`

  Adds clause C to the beginning of a static procedure.

`assertz_static(:C)`

  Adds clause C to the end of a static procedure. Asserting a static clause for a predicate while choice-points for the predicate are available has undefined results.

The following predicates can be used for dynamic predicates and for static predicates, if source mode was on when they were compiled:

`clause(+H,B) [ISO]`

  A clause whose head matches H is searched for in the program. Its head and body are respectively unified with H and B. If the clause is a unit clause, B is unified with true.

  This predicate is applicable to static procedures compiled with `source` active, and to all dynamic procedures.

`clause(+H,B,-R)`

  The same as `clause/2`, plus R is unified with the reference to the clause in the database. You can use `instance/2` to access the reference’s value. Note that you may not use `erase/1` on the reference on static procedures.

`nth_clause(+H,I,-R)`

  Find the Ith clause in the predicate defining H, and give a reference to the clause. Alternatively, if the reference R is given the head H is unified with a description of the predicate and I is bound to its position.

The following predicates can only be used for dynamic predicates:

`retract(+C) [ISO]`

  Erases the first clause in the program that matches C. This predicate may also be used for the static predicates that have been compiled when the source mode was `on`. For more information on `source/0` (see section Changing the Compiler’s Behavior).

`retractall(+G)`

  Retract all the clauses whose head matches the goal G. Goal G must be a call to a dynamic predicate.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.10.2 Looking at the Data Base

`listing`

  Lists in the current output stream all the clauses for which source code is available (these include all clauses for dynamic predicates and clauses for static predicates compiled when source mode was `on`).

`listing(+P)`

  Lists predicate P if its source code is available.

`portray_clause(+C)`

  Write clause C as if written by `listing/0`.

`portray_clause(+S,+C)`

  Write clause C on stream S as if written by `listing/0`.

`current_atom(A)`

  Checks whether A is a currently defined atom. It is used to find all currently defined atoms by backtracking.

`current_predicate(F) [ISO]`

  F is the predicate indicator for a currently defined user or library predicate. F is of the form Na/Ar, where the atom Na is the name of the predicate, and Ar its arity.

`current_predicate(A,P)`

  Defines the relation: P is a currently defined predicate whose name is the atom A.

`system_predicate(A,P)`

  Defines the relation: P is a built-in predicate whose name is the atom A.

`predicate_property(P,Prop) [ISO]`

  For the predicates obeying the specification P unify Prop with a property of P. These properties may be:

  `built_in`

    true for built-in predicates,

  `dynamic`

    true if the predicate is dynamic

  `static`

    true if the predicate is static

  `meta_predicate(M)`

    true if the predicate has a meta_predicate declaration M.

  `multifile`

    true if the predicate was declared to be multifile

  `imported_from(Mod)`

    true if the predicate was imported from module Mod.

  `exported`

    true if the predicate is exported in the current module.

  `public`

    true if the predicate is public; note that all dynamic predicates are public.

  `tabled`

    true if the predicate is tabled; note that only static predicates can be tabled in YAP.

  `source`

    true if source for the predicate is available.

  `number_of_clauses(ClauseCount)`

    Number of clauses in the predicate definition. Always one if external or built-in.

`predicate_statistics(P,NCls,Sz,IndexSz)`

  Given predicate P, NCls is the number of clauses for P, Sz is the amount of space taken to store those clauses (in bytes), and IndexSz is the amount of space required to store indices to those clauses (in bytes).

`predicate_erased_statistics(P,NCls,Sz,IndexSz)`

  Given predicate P, NCls is the number of erased clauses for P that could not be discarded yet, Sz is the amount of space taken to store those clauses (in bytes), and IndexSz is the amount of space required to store indices to those clauses (in bytes).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.10.3 Using Data Base References

Data Base references are a fast way of accessing terms. The predicates `erase/1` and `instance/1` also apply to these references and may sometimes be used instead of `retract/1` and `clause/2`.

`assert(+C,-R)`

  The same as `assert(C)` (see section Modification of the Data Base) but unifies R with the database reference that identifies the new clause, in a one-to-one way. Note that `asserta/2` only works for dynamic predicates. If the predicate is undefined, it will automatically be declared dynamic.

`asserta(+C,-R)`

  The same as `asserta(C)` but unifying R with the database reference that identifies the new clause, in a one-to-one way. Note that `asserta/2` only works for dynamic predicates. If the predicate is undefined, it will automatically be declared dynamic.

`assertz(+C,-R)`

  The same as `assertz(C)` but unifying R with the database reference that identifies the new clause, in a one-to-one way. Note that `asserta/2` only works for dynamic predicates. If the predicate is undefined, it will automatically be declared dynamic.

`retract(+C,-R)`

  Erases from the program the clause C whose database reference is R. The predicate must be dynamic.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.11 Internal Data Base

Some programs need global information for, e.g. counting or collecting data obtained by backtracking. As a rule, to keep this information, the internal data base should be used instead of asserting and retracting clauses (as most novice programmers do), . In YAP (as in some other Prolog systems) the internal data base (i.d.b. for short) is faster, needs less space and provides a better insulation of program and data than using asserted/retracted clauses. The i.d.b. is implemented as a set of terms, accessed by keys that unlikely what happens in (non-Prolog) data bases are not part of the term. Under each key a list of terms is kept. References are provided so that terms can be identified: each term in the i.d.b. has a unique reference (references are also available for clauses of dynamic predicates).

`recorda(+K,T,-R)`

  Makes term T the first record under key K and unifies R with its reference.

`recordz(+K,T,-R)`

  Makes term T the last record under key K and unifies R with its reference.

`recorda_at(+R0,T,-R)`

  Makes term T the record preceding record with reference R0, and unifies R with its reference.

`recordz_at(+R0,T,-R)`

  Makes term T the record following record with reference R0, and unifies R with its reference.

`recordaifnot(+K,T,-R)`

  If a term equal to T up to variable renaming is stored under key K fail. Otherwise, make term T the first record under key K and unify R with its reference.

`recordzifnot(+K,T,-R)`

  If a term equal to T up to variable renaming is stored under key K fail. Otherwise, make term T the first record under key K and unify R with its reference.

`recorded(+K,T,R)`

  Searches in the internal database under the key K, a term that unifies with T and whose reference matches R. This built-in may be used in one of two ways:

  - K may be given, in this case the built-in will return all elements of the internal data-base that match the key.
  - R may be given, if so returning the key and element that match the reference.
`erase(+R)`

  The term referred to by R is erased from the internal database. If reference R does not exist in the database, `erase` just fails.

`erased(+R)`

  Succeeds if the object whose database reference is R has been erased.

`instance(+R,-T)`

  If R refers to a clause or a recorded term, T is unified with its most general instance. If R refers to an unit clause C, then T is unified with `C :- true`. When R is not a reference to an existing clause or to a recorded term, this goal fails.

`eraseall(+K)`

  All terms belonging to the key `K` are erased from the internal database. The predicate always succeeds.

`current_key(?A,?K)`

  Defines the relation: K is a currently defined database key whose name is the atom A. It can be used to generate all the keys for the internal data-base.

`nth_instance(?Key,?Index,?R)`

  Fetches the Indexnth entry in the internal database under the key Key. Entries are numbered from one. If the key Key or the Index are bound, a reference is unified with R. Otherwise, the reference R must be given, and YAP will find the matching key and index.

`nth_instance(?Key,?Index,T,?R)`

  Fetches the Indexnth entry in the internal database under the key Key. Entries are numbered from one. If the key Key or the Index are bound, a reference is unified with R. Otherwise, the reference R must be given, and YAP will find the matching key and index.

`key_statistics(+K,-Entries,-Size,-IndexSize)`

  Returns several statistics for a key K. Currently, it says how many entries we have for that key, Entries, what is the total size spent on entries, Size, and what is the amount of space spent in indices.

`key_statistics(+K,-Entries,-TotalSize)`

  Returns several statistics for a key K. Currently, it says how many entries we have for that key, Entries, what is the total size spent on this key.

`get_value(+A,-V)`

  In YAP, atoms can be associated with constants. If one such association exists for atom A, unify the second argument with the constant. Otherwise, unify V with `[]`.

  This predicate is YAP specific.

`set_value(+A,+C)`

  Associate atom A with constant C.

  The `set_value` and `get_value` built-ins give a fast alternative to the internal data-base. This is a simple form of implementing a global counter.

             read_and_increment_counter(Value) :-
                      get_value(counter, Value),
                      Value1 is Value+1,
                      set_value(counter, Value1).

  This predicate is YAP specific.

`recordzifnot(+K,T,-R)`

  If a variant of T is stored under key K fail. Otherwise, make term T the last record under key K and unify R with its reference.

  This predicate is YAP specific.

`recordaifnot(+K,T,-R)`

  If a variant of T is stored under key K fail. Otherwise, make term T the first record under key K and unify R with its reference.

  This predicate is YAP specific.

There is a strong analogy between the i.d.b. and the way dynamic predicates are stored. In fact, the main i.d.b. predicates might be implemented using dynamic predicates:

    recorda(X,T,R) :- asserta(idb(X,T),R).
    recordz(X,T,R) :- assertz(idb(X,T),R).
    recorded(X,T,R) :- clause(idb(X,T),R).

We can take advantage of this, the other way around, as it is quite easy to write a simple Prolog interpreter, using the i.d.b.:

    asserta(G) :- recorda(interpreter,G,_).
    assertz(G) :- recordz(interpreter,G,_).
    retract(G) :- recorded(interpreter,G,R), !, erase(R).
    call(V) :- var(V), !, fail.
    call((H :- B)) :- !, recorded(interpreter,(H :- B),_), call(B).
    call(G) :- recorded(interpreter,G,_).

In YAP, much attention has been given to the implementation of the i.d.b., especially to the problem of accelerating the access to terms kept in a large list under the same key. Besides using the key, YAP uses an internal lookup function, transparent to the user, to find only the terms that might unify. For instance, in a data base containing the terms

    b
    b(a)
    c(d)
    e(g)
    b(X)
    e(h)

stored under the key k/1, when executing the query

    :- recorded(k(_),c(_),R).

`recorded` would proceed directly to the third term, spending almost the time as if `a(X)` or `b(X)` was being searched. The lookup function uses the functor of the term, and its first three arguments (when they exist). So, `recorded(k(_),e(h),_)` would go directly to the last term, while `recorded(k(_),e(_),_)` would find first the fourth term, and then, after backtracking, the last one.

This mechanism may be useful to implement a sort of hierarchy, where the functors of the terms (and eventually the first arguments) work as secondary keys.

In the YAP’s i.d.b. an optimized representation is used for terms without free variables. This results in a faster retrieval of terms and better space usage. Whenever possible, avoid variables in terms in terms stored in the i.d.b.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.12 The Blackboard

YAP implements a blackboard in the style of the SICStus Prolog blackboard. The blackboard uses the same underlying mechanism as the internal data-base but has several important differences:

- It is module aware, in contrast to the internal data-base.
- Keys can only be atoms or integers, and not compound terms.
- A single term can be stored per key.
- An atomic update operation is provided; this is useful for parallelism.

`bb_put(+Key,?Term)`

  Store term table Term in the blackboard under key Key. If a previous term was stored under key Key it is simply forgotten.

`bb_get(+Key,?Term)`

  Unify Term with a term stored in the blackboard under key Key, or fail silently if no such term exists.

`bb_delete(+Key,?Term)`

  Delete any term stored in the blackboard under key Key and unify it with Term. Fail silently if no such term exists.

`bb_update(+Key,?Term,?New)`

  Atomically unify a term stored in the blackboard under key Key with Term, and if the unification succeeds replace it by New. Fail silently if no such term exists or if unification fails.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.13 Collecting Solutions to a Goal

When there are several solutions to a goal, if the user wants to collect all the solutions he may be led to use the data base, because backtracking will forget previous solutions.

YAP allows the programmer to choose from several system predicates instead of writing his own routines. `findall/3` gives you the fastest, but crudest solution. The other built-in predicates post-process the result of the query in several different ways:

`findall(T,+G,-L) [ISO]`

  Unifies L with a list that contains all the instantiations of the term T satisfying the goal G.

  With the following program:

      a(2,1).
      a(1,1).
      a(2,2).

  the answer to the query

      findall(X,a(X,Y),L).

  would be:

      X = _32
      Y = _33
      L = [2,1,2];
      no

`findall(T,+G,+L,-L0)`

  Similar to `findall/3`, but appends all answers to list L0.

`all(T,+G,-L)`

  Similar to `findall(T,G,L)` but eliminate repeated elements. Thus, assuming the same clauses as in the above example, the reply to the query

      all(X,a(X,Y),L).

  would be:

      X = _32
      Y = _33
      L = [2,1];
      no

  Note that `all/3` will fail if no answers are found.

`bagof(T,+G,-L) [ISO]`

  For each set of possible instances of the free variables occurring in G but not in T, generates the list L of the instances of T satisfying G. Again, assuming the same clauses as in the examples above, the reply to the query

      bagof(X,a(X,Y),L).

      would be:
      X = _32
      Y = 1
      L = [2,1];
      X = _32
      Y = 2
      L = [2];
      no

`setof(X,+P,-B) [ISO]`

  Similar to `bagof(T,G,L)` but sorting list L and keeping only one copy of each element. Again, assuming the same clauses as in the examples above, the reply to the query

      setof(X,a(X,Y),L).

  would be:

      X = _32
      Y = 1
      L = [1,2];
      X = _32
      Y = 2
      L = [2];
      no

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.14 Grammar Rules

Grammar rules in Prolog are both a convenient way to express definite clause grammars and an extension of the well known context-free grammars.

A grammar rule is of the form:

     head --> body

where both head and body are sequences of one or more items linked by the standard conjunction operator ’,’.

Items can be:

- a non-terminal symbol may be either a complex term or an atom.
- a terminal symbol may be any Prolog symbol. Terminals are written as Prolog lists.
- an empty body is written as the empty list ’[ ]’.
- extra conditions may be inserted as Prolog procedure calls, by being written inside curly brackets ’{’ and ’}’.
- the left side of a rule consists of a nonterminal and an optional list of terminals.
- alternatives may be stated in the right-hand side of the rule by using the disjunction operator ’;’.
- the cut and conditional symbol (’->’) may be inserted in the right hand side of a grammar rule

Grammar related built-in predicates:

`expand_term(T,-X)`

  This predicate is used by YAP for preprocessing each top level term read when consulting a file and before asserting or executing it. It rewrites a term T to a term X according to the following rules: first try `term_expansion/2` in the current module, and then try to use the user defined predicate `user:term_expansion/2`. If this call fails then the translating process for DCG rules is applied, together with the arithmetic optimizer whenever the compilation of arithmetic expressions is in progress.

`CurrentModule:term_expansion(T,-X)`
`user:term_expansion(T,-X)`

  This user-defined predicate is called by `expand_term/3` to preprocess all terms read when consulting a file. If it succeeds:

  - If X is of the form `:- G` or `?- G`, it is processed as a directive.
  - If X is a list, all terms of the list are asserted or processed as directives.
  - The term X is asserted instead of T.
`CurrentModule:goal_expansion(+G,+M,-NG)`
`user:goal_expansion(+G,+M,-NG)`

  YAP now supports `goal_expansion/3`. This is an user-defined procedure that is called after term expansion when compiling or asserting goals for each sub-goal in a clause. The first argument is bound to the goal and the second to the module under which the goal G will execute. If `goal_expansion/3` succeeds the new sub-goal NG will replace G and will be processed in the same way. If `goal_expansion/3` fails the system will use the default rules.

`phrase(+P,L,R)`

  This predicate succeeds when the difference list `L-R` is a phrase of type P.

`phrase(+P,L)`

  This predicate succeeds when L is a phrase of type P. The same as `phrase(P,L,[])`.

  Both this predicate and the previous are used as a convenient way to start execution of grammar rules.

`'C'(S1,T,S2)`

  This predicate is used by the grammar rules compiler and is defined as `'C'([H|T],H,T)`.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.15 Access to Operating System Functionality

The following built-in predicates allow access to underlying Operating System functionality:

`cd(+D)`

  Changes the current directory (on UNIX environments).

`cd`

  Changes the current directory (on UNIX environments) to the user’s home directory.

`environ(+E,-S)`

  Given an environment variable E this predicate unifies the second argument S with its value.

`getcwd(-D)`

  Unify the current directory, represented as an atom, with the argument D.

`pwd`

  Prints the current directory.

`ls`

  Prints a list of all files in the current directory.

`putenv(+E,+S)`

  Set environment variable E to the value S. If the environment variable E does not exist, create a new one. Both the environment variable and the value must be atoms.

`rename(+F,+G)`

  Renames file F to G.

`sh`

  Creates a new shell interaction.

`system(+S)`

  Passes command S to the Bourne shell (on UNIX environments) or the current command interpreter in WIN32 environments.

`unix(+S)`

  Access to Unix-like functionality:

  `argv/1`

    Return a list of arguments to the program. These are the arguments that follow a `--`, as in the usual Unix convention.

  `cd/0`

    Change to home directory.

  `cd/1`

    Change to given directory. Acceptable directory names are strings or atoms.

  `environ/2`

    If the first argument is an atom, unify the second argument with the value of the corresponding environment variable.

  `getcwd/1`

    Unify the first argument with an atom representing the current directory.

  `putenv/2`

    Set environment variable E to the value S. If the environment variable E does not exist, create a new one. Both the environment variable and the value must be atoms.

  `shell/1`

    Execute command under current shell. Acceptable commands are strings or atoms.

  `system/1`

    Execute command with `/bin/sh`. Acceptable commands are strings or atoms.

  `shell/0`

    Execute a new shell.

`alarm(+Seconds,+Callable,+OldAlarm)`

  Arranges for YAP to be interrupted in Seconds seconds, or in [Seconds|MicroSeconds]. When interrupted, YAP will execute Callable and then return to the previous execution. If Seconds is `0`, no new alarm is scheduled. In any event, any previously set alarm is canceled.

  The variable OldAlarm unifies with the number of seconds remaining until any previously scheduled alarm was due to be delivered, or with `0` if there was no previously scheduled alarm.

  Note that execution of Callable will wait if YAP is executing built-in predicates, such as Input/Output operations.

  The next example shows how alarm/3 can be used to implement a simple clock:

      loop :- loop.

      ticker :- write('.'), flush_output,
                get_value(tick, yes),
                alarm(1,ticker,_).

      :- set_value(tick, yes), alarm(1,ticker,_), loop.

  The clock, `ticker`, writes a dot and then checks the flag `tick` to see whether it can continue ticking. If so, it calls itself again. Note that there is no guarantee that the each dot corresponds a second: for instance, if the YAP is waiting for user input, `ticker` will wait until the user types the entry in.

  The next example shows how `alarm/3` can be used to guarantee that a certain procedure does not take longer than a certain amount of time:

      loop :- loop.

      :-   catch((alarm(10, throw(ball), _),loop),
              ball,
              format('Quota exhausted.~n',[])).

  In this case after `10` seconds our `loop` is interrupted, `ball` is thrown, and the handler writes `Quota exhausted`. Execution then continues from the handler.

  Note that in this case `loop/0` always executes until the alarm is sent. Often, the code you are executing succeeds or fails before the alarm is actually delivered. In this case, you probably want to disable the alarm when you leave the procedure. The next procedure does exactly so:

      once_with_alarm(Time,Goal,DoOnAlarm) :-
         catch(execute_once_with_alarm(Time, Goal), alarm, DoOnAlarm).

      execute_once_with_alarm(Time, Goal) :-
              alarm(Time, alarm, _),
              ( call(Goal) -> alarm(0, alarm, _) ; alarm(0, alarm, _), fail).

  The procedure `once_with_alarm/3` has three arguments: the Time to wait before the alarm is sent; the Goal to execute; and the goal DoOnAlarm to execute if the alarm is sent. It uses `catch/3` to handle the case the `alarm` is sent. Then it starts the alarm, calls the goal Goal, and disables the alarm on success or failure.

`on_signal(+Signal,?OldAction,+Callable)`

  Set the interrupt handler for soft interrupt Signal to be Callable. OldAction is unified with the previous handler.

  Only a subset of the software interrupts (signals) can have their handlers manipulated through `on_signal/3`. Their POSIX names, YAP names and default behavior is given below. The "YAP name" of the signal is the atom that is associated with each signal, and should be used as the first argument to `on_signal/3`. It is chosen so that it matches the signal’s POSIX name.

  `on_signal/3` succeeds, unless when called with an invalid signal name or one that is not supported on this platform. No checks are made on the handler provided by the user.

  `sig_up (Hangup)`

    SIGHUP in Unix/Linux; Reconsult the initialization files ~/.yaprc, ~/.prologrc and ~/prolog.ini.

  `sig_usr1 and sig_usr2 (User signals)`

    SIGUSR1 and SIGUSR2 in Unix/Linux; Print a message and halt.

  A special case is made, where if Callable is bound to `default`, then the default handler is restored for that signal.

  A call in the form `on_signal(S,H,H)` can be used to retrieve a signal’s current handler without changing it.

  It must be noted that although a signal can be received at all times, the handler is not executed while YAP is waiting for a query at the prompt. The signal will be, however, registered and dealt with as soon as the user makes a query.

  Please also note, that neither POSIX Operating Systems nor YAP guarantee that the order of delivery and handling is going to correspond with the order of dispatch.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.16 Term Modification

It is sometimes useful to change the value of instantiated variables. Although, this is against the spirit of logic programming, it is sometimes useful. As in other Prolog systems, YAP has several primitives that allow updating Prolog terms. Note that these primitives are also backtrackable.

The `setarg/3` primitive allows updating any argument of a Prolog compound terms. The `mutable` family of predicates provides mutable variables. They should be used instead of `setarg/3`, as they allow the encapsulation of accesses to updatable variables. Their implementation can also be more efficient for long deterministic computations.

`setarg(+I,+S,?T)`

  Set the value of the Ith argument of term S to term T.

`create_mutable(+D,-M)`

  Create new mutable variable M with initial value D.

`get_mutable(?D,+M)`

  Unify the current value of mutable term M with term D.

`is_mutable(?D)`

  Holds if D is a mutable term.

`get_mutable(?D,+M)`

  Unify the current value of mutable term M with term D.

`update_mutable(+D,+M)`

  Set the current value of mutable term M to term D.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.17 Global Variables

Global variables are associations between names (atoms) and terms. They differ in various ways from storing information using `assert/1` or `recorda/3`.

- The value lives on the Prolog (global) stack. This implies that lookup time is independent from the size of the term. This is particularly interesting for large data structures such as parsed XML documents or the CHR global constraint store.
- They support both global assignment using `nb_setval/2` and backtrackable assignment using `b_setval/2`.
- Only one value (which can be an arbitrary complex Prolog term) can be associated to a variable at a time.
- Their value cannot be shared among threads. Each thread has its own namespace and values for global variables.

Currently global variables are scoped globally. We may consider module scoping in future versions. Both `b_setval/2` and `nb_setval/2` implicitly create a variable if the referenced name does not already refer to a variable.

Global variables may be initialised from directives to make them available during the program lifetime, but some considerations are necessary for saved-states and threads. Saved-states to not store global variables, which implies they have to be declared with `initialization/1` to recreate them after loading the saved state. Each thread has its own set of global variables, starting with an empty set. Using `thread_initialization/1` to define a global variable it will be defined, restored after reloading a saved state and created in all threads that are created after the registration. Finally, global variables can be initialised using the exception hook called `exception/3`. The latter technique is used by CHR.

`b_setval(+Name, +Value)`

  Associate the term Value with the atom Name or replaces the currently associated value with Value. If Name does not refer to an existing global variable a variable with initial value [] is created (the empty list). On backtracking the assignment is reversed.

`b_getval(+Name, -Value)`

  Get the value associated with the global variable Name and unify it with Value. Note that this unification may further instantiate the value of the global variable. If this is undesirable the normal precautions (double negation or `copy_term/2`) must be taken. The `b_getval/2` predicate generates errors if Name is not an atom or the requested variable does not exist.

  Notice that for compatibility with other systems Name must be already associated with a term: otherwise the system will generate an error.

`nb_setval(+Name, +Value)`

  Associates a copy of Value created with `duplicate_term/2` with the atom Name. Note that this can be used to set an initial value other than `[]` prior to backtrackable assignment.

`nb_getval(+Name, -Value)`

  The `nb_getval/2` predicate is a synonym for `b_getval/2`, introduced for compatibility and symmetry. As most scenarios will use a particular global variable either using non-backtrackable or backtrackable assignment, using `nb_getval/2` can be used to document that the variable is used non-backtrackable.

`nb_linkval(+Name, +Value)`

  Associates the term Value with the atom Name without copying it. This is a fast special-purpose variation of `nb_setval/2` intended for expert users only because the semantics on backtracking to a point before creating the link are poorly defined for compound terms. The principal term is always left untouched, but backtracking behaviour on arguments is undone if the original assignment was trailed and left alone otherwise, which implies that the history that created the term affects the behaviour on backtracking. Please consider the following example:

      demo_nb_linkval :-
              T = nice(N),
              (   N = world,
                  nb_linkval(myvar, T),
                  fail
              ;   nb_getval(myvar, V),
                  writeln(V)
              ).

`nb_set_shared_val(+Name, +Value)`

  Associates the term Value with the atom Name, but sharing non-backtrackable terms. This may be useful if you want to rewrite a global variable so that the new copy will survive backtracking, but you want to share structure with the previous term.

  The next example shows the differences between the three built-ins:

      ?- nb_setval(a,a(_)),nb_getval(a,A),nb_setval(b,t(C,A)),nb_getval(b,B).
      A = a(_A),
      B = t(_B,a(_C)) ?

      ?- nb_setval(a,a(_)),nb_getval(a,A),nb_set_shared_val(b,t(C,A)),nb_getval(b,B).

      ?- nb_setval(a,a(_)),nb_getval(a,A),nb_linkval(b,t(C,A)),nb_getval(b,B).
      A = a(_A),
      B = t(C,a(_A)) ?

`nb_setarg(+{Arg], +Term, +Value)`

  Assigns the Arg-th argument of the compound term Term with the given Value as setarg/3, but on backtracking the assignment is not reversed. If Term is not atomic, it is duplicated using duplicate_term/2. This predicate uses the same technique as `nb_setval/2`. We therefore refer to the description of `nb_setval/2` for details on non-backtrackable assignment of terms. This predicate is compatible to GNU-Prolog `setarg(A,T,V,false)`, removing the type-restriction on Value. See also `nb_linkarg/3`. Below is an example for counting the number of solutions of a goal. Note that this implementation is thread-safe, reentrant and capable of handling exceptions. Realising these features with a traditional implementation based on assert/retract or flag/3 is much more complicated.

          succeeds_n_times(Goal, Times) :-
                  Counter = counter(0),
                  (   Goal,
                      arg(1, Counter, N0),
                      N is N0 + 1,
                      nb_setarg(1, Counter, N),
                      fail
                  ;   arg(1, Counter, Times)
                  ).

`nb_set_shared_arg(+Arg, +Term, +Value)`

  As `nb_setarg/3`, but like `nb_linkval/2` it does not duplicate the global sub-terms in Value. Use with extreme care and consult the documentation of `nb_linkval/2` before use.

`nb_linkarg(+Arg, +Term, +Value)`

  As `nb_setarg/3`, but like `nb_linkval/2` it does not duplicate Value. Use with extreme care and consult the documentation of `nb_linkval/2` before use.

`nb_current(?Name, ?Value)`

  Enumerate all defined variables with their value. The order of enumeration is undefined.

`nb_delete(+Name)`

  Delete the named global variable.

Global variables have been introduced by various Prolog implementations recently. We follow the implementation of them in SWI-Prolog, itself based on hProlog by Bart Demoen.

GNU-Prolog provides a rich set of global variables, including arrays. Arrays can be implemented easily in YAP and SWI-Prolog using `functor/3` and `setarg/3` due to the unrestricted arity of compound terms.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.18 Profiling Prolog Programs

YAP includes two profilers. The count profiler keeps information on the number of times a predicate was called. This information can be used to detect what are the most commonly called predicates in the program. The count profiler can be compiled by setting YAP’s flag `profiling` to `on`. The time-profiler is a `gprof` profiler, and counts how many ticks are being spent on specific predicates, or on other system functions such as internal data-base accesses or garbage collects.

The YAP profiling sub-system is currently under development. Functionality for this sub-system will increase with newer implementation.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.18.1 The Count Profiler

Notes:

The count profiler works by incrementing counters at procedure entry or backtracking. It provides exact information:

- Profiling works for both static and dynamic predicates.
- Currently only information on entries and retries to a predicate are maintained. This may change in the future.
- As an example, the following user-level program gives a list of the most often called procedures in a program. The procedure `list_profile` shows all procedures, irrespective of module, and the procedure `list_profile/1` shows the procedures being used in a specific module.

      list_profile :-
              % get number of calls for each profiled procedure
              setof(D-[M:P|D1],(current_module(M),profile_data(M:P,calls,D),profile_data(M:P,retries,D1)),LP),
              % output so that the most often called
              % predicates will come last:
              write_profile_data(LP).

      list_profile(Module) :-
              % get number of calls for each profiled procedure
              setof(D-[Module:P|D1],(profile_data(Module:P,calls,D),profile_data(Module:P,retries,D1)),LP),
              % output so that the most often called
              % predicates will come last:
              write_profile_data(LP).

      write_profile_data([]).
      write_profile_data([D-[M:P|R]|SLP]) :-
              % swap the two calls if you want the most often
              %  called predicates first.
              format('~a:~w: ~32+~t~d~12+~t~d~12+~n', [M,P,D,R]),
              write_profile_data(SLP).

These are the current predicates to access and clear profiling data:

`profile_data(?Na/Ar, ?Parameter, -Data)`

  Give current profile data on Parameter for a predicate described by the predicate indicator Na/Ar. If any of Na/Ar or Parameter are unbound, backtrack through all profiled predicates or stored parameters. Current parameters are:

  `calls`

    Number of times a procedure was called.

  `retries`

    Number of times a call to the procedure was backtracked to and retried.

`profile_reset`

  Reset all profiling information.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 6.18.2 Tick Profiler

The tick profiler works by interrupting the Prolog code every so often and checking at each point the code was. The profiler must be able to retrace the state of the abstract machine at every moment. The major advantage of this approach is that it gives the actual amount of time being spent per procedure, or whether garbage collection dominates execution time. The major drawback is that tracking down the state of the abstract machine may take significant time, and in the worst case may slow down the whole execution.

The following procedures are available:

`profinit`

  Initialise the data-structures for the profiler. Unnecessary for dynamic profiler.

`profon`

  Start profiling.

`profoff`

  Stop profiling.

`showprofres`

  Show profiling info.

`showprofres(N)`

  Show profiling info for the top-most N predicates.

The `showprofres/0` and `showprofres/1` predicates call a user-defined multifile hook predicate, `user:prolog_predicate_name/2`, that can be used for converting a possibly explicitly-qualified callable term into an atom that will used when printing the profiling information.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.19 Counting Calls

Predicates compiled with YAP’s flag `call_counting` set to `on` update counters on the numbers of calls and of retries. Counters are actually decreasing counters, so that they can be used as timers. Three counters are available:

- `calls`: number of predicate calls since execution started or since system was reset;
- `retries`: number of retries for predicates called since execution started or since counters were reset;
- `calls_and_retries`: count both on predicate calls and retries.

These counters can be used to find out how many calls a certain goal takes to execute. They can also be used as timers.

The code for the call counters piggybacks on the profiling code. Therefore, activating the call counters also activates the profiling counters.

These are the predicates that access and manipulate the call counters:

`call_count_data(-Calls, -Retries, -CallsAndRetries)`

  Give current call count data. The first argument gives the current value for the Calls counter, next the Retries counter, and last the CallsAndRetries counter.

`call_count_reset`

  Reset call count counters. All timers are also reset.

`call_count(?CallsMax, ?RetriesMax, ?CallsAndRetriesMax)`

  Set call count counter as timers. YAP will generate an exception if one of the instantiated call counters decreases to 0. YAP will ignore unbound arguments:

  - CallsMax: throw the exception `call_counter` when the counter `calls` reaches 0;
  - RetriesMax: throw the exception `retry_counter` when the counter `retries` reaches 0;
  - CallsAndRetriesMax: throw the exception `call_and_retry_counter` when the counter `calls_and_retries` reaches 0.

Next, we show a simple example of how to use call counters:

       ?- yap_flag(call_counting,on), [-user]. l :- l. end_of_file. yap_flag(call_counting,off).

    yes

    yes
       ?- catch((call_count(10000,_,_),l),call_counter,format("limit_exceeded.~n",[])).

    limit_exceeded.

    yes

Notice that we first compile the looping predicate `l/0` with `call_counting` `on`. Next, we `catch/3` to handle an exception when `l/0` performs more than 10000 reductions.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.20 Arrays

The YAP system includes experimental support for arrays. The support is enabled with the option `YAP_ARRAYS`.

There are two very distinct forms of arrays in YAP. The dynamic arrays are a different way to access compound terms created during the execution. Like any other terms, any bindings to these terms and eventually the terms themselves will be destroyed during backtracking. Our goal in supporting dynamic arrays is twofold. First, they provide an alternative to the standard `arg/3` built-in. Second, because dynamic arrays may have name that are globally visible, a dynamic array can be visible from any point in the program. In more detail, the clause

    g(X) :- array_element(a,2,X).

will succeed as long as the programmer has used the built-in `array/2` to create an array term with at least 3 elements in the current environment, and the array was associated with the name `a`. The element `X` is a Prolog term, so one can bind it and any such bindings will be undone when backtracking. Note that dynamic arrays do not have a type: each element may be any Prolog term.

The static arrays are an extension of the database. They provide a compact way for manipulating data-structures formed by characters, integers, or floats imperatively. They can also be used to provide two-way communication between YAP and external programs through shared memory.

In order to efficiently manage space elements in a static array must have a type. Currently, elements of static arrays in YAP should have one of the following predefined types:

- `byte`: an 8-bit signed character.
- `unsigned_byte`: an 8-bit unsigned character.
- `int`: Prolog integers. Size would be the natural size for the machine’s architecture.
- `float`: Prolog floating point number. Size would be equivalent to a double in `C`.
- `atom`: a Prolog atom.
- `dbref`: an internal database reference.
- `term`: a generic Prolog term. Note that this will term will not be stored in the array itself, but instead will be stored in the Prolog internal database.

Arrays may be named or anonymous. Most arrays will be named, that is associated with an atom that will be used to find the array. Anonymous arrays do not have a name, and they are only of interest if the `TERM_EXTENSIONS` compilation flag is enabled. In this case, the unification and parser are extended to replace occurrences of Prolog terms of the form `X[I]` by run-time calls to `array_element/3`, so that one can use array references instead of extra calls to `arg/3`. As an example:

    g(X,Y,Z,I,J) :- X[I] is Y[J]+Z[I].

should give the same results as:

    G(X,Y,Z,I,J) :-
            array_element(X,I,E1),
            array_element(Y,J,E2),
            array_element(Z,I,E3),
            E1 is E2+E3.

Note that the only limitation on array size are the stack size for dynamic arrays; and, the heap size for static (not memory mapped) arrays. Memory mapped arrays are limited by available space in the file system and in the virtual memory space.

The following predicates manipulate arrays:

`array(+Name, +Size)`

  Creates a new dynamic array. The Size must evaluate to an integer. The Name may be either an atom (named array) or an unbound variable (anonymous array).

  Dynamic arrays work as standard compound terms, hence space for the array is recovered automatically on backtracking.

`static_array(+Name, +Size, +Type)`

  Create a new static array with name Name. Note that the Name must be an atom (named array). The Size must evaluate to an integer. The Type must be bound to one of types mentioned previously.

`reset_static_array(+Name)`

  Reset static array with name Name to its initial value.

`static_array_location(+Name, -Ptr)`

  Give the location for a static array with name Name.

`static_array_properties(?Name, ?Size, ?Type)`

  Show the properties size and type of a static array with name Name. Can also be used to enumerate all current static arrays.

  This built-in will silently fail if the there is no static array with that name.

`static_array_to_term(?Name, ?Term)`

  Convert a static array with name Name to a compound term of name Name.

  This built-in will silently fail if the there is no static array with that name.

`mmapped_array(+Name, +Size, +Type, +File)`

  Similar to `static_array/3`, but the array is memory mapped to file File. This means that the array is initialized from the file, and that any changes to the array will also be stored in the file.

  This built-in is only available in operating systems that support the system call `mmap`. Moreover, mmapped arrays do not store generic terms (type `term`).

`close_static_array(+Name)`

  Close an existing static array of name Name. The Name must be an atom (named array). Space for the array will be recovered and further accesses to the array will return an error.

`resize_static_array(+Name, -OldSize, +NewSize)`

  Expand or reduce a static array, The Size must evaluate to an integer. The Name must be an atom (named array). The Type must be bound to one of `int`, `dbref`, `float` or `atom`.

  Note that if the array is a mmapped array the size of the mmapped file will be actually adjusted to correspond to the size of the array.

`array_element(+Name, +Index, ?Element)`

  Unify Element with Name[Index]. It works for both static and dynamic arrays, but it is read-only for static arrays, while it can be used to unify with an element of a dynamic array.

`update_array(+Name, +Index, ?Value)`

  Attribute value Value to Name[Index]. Type restrictions must be respected for static arrays. This operation is available for dynamic arrays if `MULTI_ASSIGNMENT_VARIABLES` is enabled (true by default). Backtracking undoes update_array/3 for dynamic arrays, but not for static arrays.

  Note that `update_array/3` actually uses `setarg/3` to update elements of dynamic arrays, and `setarg/3` spends an extra cell for every update. For intensive operations we suggest it may be less expensive to unify each element of the array with a mutable terms and to use the operations on mutable terms.

`add_to_array_element(+Name, +Index, , +Number, ?NewValue)`

  Add Number Name[Index] and unify NewValue with the incremented value. Observe that Name[Index] must be an number. If Name is a static array the type of the array must be `int` or `float`. If the type of the array is `int` you only may add integers, if it is `float` you may add integers or floats. If Name corresponds to a dynamic array the array element must have been previously bound to a number and `Number` can be any kind of number.

  The `add_to_array_element/3` built-in actually uses `setarg/3` to update elements of dynamic arrays. For intensive operations we suggest it may be less expensive to unify each element of the array with a mutable terms and to use the operations on mutable terms.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.21 Predicate Information

Built-ins that return information on the current predicates and modules:

`current_module(M)`

  Succeeds if M are defined modules. A module is defined as soon as some predicate defined in the module is loaded, as soon as a goal in the module is called, or as soon as it becomes the current type-in module.

`current_module(M,F)`

  Succeeds if M are current modules associated to the file F.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 6.22 Miscellaneous

`statistics/0`

  Send to the current user error stream general information on space used and time spent by the system.

      ?- statistics.
      memory (total)        4784124 bytes
         program space      3055616 bytes:    1392224 in use,      1663392 free
                                                                   2228132  max
         stack space        1531904 bytes:        464 in use,      1531440 free
           global stack:                           96 in use,       616684  max
            local stack:                          368 in use,       546208  max
         trail stack         196604 bytes:          8 in use,       196596 free

             0.010 sec. for 5 code, 2 stack, and 1 trail space overflows
             0.130 sec. for 3 garbage collections which collected 421000 bytes
             0.000 sec. for 0 atom garbage collections which collected 0 bytes
             0.880 sec. runtime
             1.020 sec. cputime
            25.055 sec. elapsed time

  The example shows how much memory the system spends. Memory is divided into Program Space, Stack Space and Trail. In the example we have 3MB allocated for program spaces, with less than half being actually used. YAP also shows the maximum amount of heap space having been used which was over 2MB.

  The stack space is divided into two stacks which grow against each other. We are in the top level so very little stack is being used. On the other hand, the system did use a lot of global and local stack during the previous execution (we refer the reader to a WAM tutorial in order to understand what are the global and local stacks).

  YAP also shows information on how many memory overflows and garbage collections the system executed, and statistics on total execution time. Cputime includes all running time, runtime excludes garbage collection and stack overflow time.

`statistics(?Param,-Info)`

  Gives statistical information on the system parameter given by first argument:

  `atoms`

    `[NumberOfAtoms,SpaceUsedBy Atoms]`
    This gives the total number of atoms `NumberOfAtoms` and how much space they require in bytes, SpaceUsedBy Atoms.

  `cputime`

    `[Time since Boot,Time From Last Call to Cputime]`
    This gives the total cputime in milliseconds spent executing Prolog code, garbage collection and stack shifts time included.

  `dynamic_code`

    `[Clause Size,Index Size,Tree Index Size,Choice Point Instructions Size,Expansion Nodes Size,Index Switch Size]`
    Size of static code in YAP in bytes: Clause Size, the number of bytes allocated for clauses, plus Index Size, the number of bytes spent in the indexing code. The indexing code is divided into main tree, Tree Index Size, tables that implement choice-point manipulation, Choice Point Instructions Size, tables that cache clauses for future expansion of the index tree, Expansion Nodes Size, and tables such as hash tables that select according to value, Index Switch Size.

  `garbage_collection`

    `[Number of GCs,Total Global Recovered,Total Time Spent]`
    Number of garbage collections, amount of space recovered in kbytes, and total time spent doing garbage collection in milliseconds. More detailed information is available using `yap_flag(gc_trace,verbose)`.

  `global_stack`

    `[Global Stack Used,Execution Stack Free]`
    Space in kbytes currently used in the global stack, and space available for expansion by the local and global stacks.

  `local_stack`

    `[Local Stack Used,Execution Stack Free]`
    Space in kbytes currently used in the local stack, and space available for expansion by the local and global stacks.

  `heap`

    `[Heap Used,Heap Free]`
    Total space in kbytes not recoverable in backtracking. It includes the program code, internal data base, and, atom symbol table.

  `program`

    `[Program Space Used,Program Space Free]`
    Equivalent to `heap`.

  `runtime`

    `[Time since Boot,Time From Last Call to Runtime]`
    This gives the total cputime in milliseconds spent executing Prolog code, not including garbage collections and stack shifts. Note that until YAP4.1.2 the `runtime` statistics would return time spent on garbage collection and stack shifting.

  `stack_shifts`

    `[Number of Heap Shifts,Number of Stack Shifts,Number of Trail Shifts]`
    Number of times YAP had to expand the heap, the stacks, or the trail. More detailed information is available using `yap_flag(gc_trace,verbose)`.

  `static_code`

    `[Clause Size,Index Size,Tree Index Size,Expansion Nodes Size,Index Switch Size]`
    Size of static code in YAP in bytes: Clause Size, the number of bytes allocated for clauses, plus Index Size, the number of bytes spent in the indexing code. The indexing code is divided into a main tree, Tree Index Size, table that cache clauses for future expansion of the index tree, Expansion Nodes Size, and and tables such as hash tables that select according to value, Index Switch Size.

  `trail`

    `[Trail Used,Trail Free]`
    Space in kbytes currently being used and still available for the trail.

  `walltime`

    `[Time since Boot,Time From Last Call to Walltime]`
    This gives the clock time in milliseconds since starting Prolog.

`time(:Goal)`

  Prints the CPU time and the wall time for the execution of Goal. Possible choice-points of Goal are removed. Based on the SWI-Prolog definition (minus reporting the number of inferences, which YAP currently does not support).

`yap_flag(?Param,?Value)`

  Set or read system properties for Param:

  `argv`

    Read-only flag. It unifies with a list of atoms that gives the arguments to YAP after `--`.

  `agc_margin`

    An integer: if this amount of atoms has been created since the last atom-garbage collection, perform atom garbage collection at the first opportunity. Initial value is 10,000. May be changed. A value of 0 (zero) disables atom garbage collection.

  `bounded [ISO]`

    Read-only flag telling whether integers are bounded. The value depends on whether YAP uses the GMP library or not.

  `profiling`

    If `off` (default) do not compile call counting information for procedures. If `on` compile predicates so that they calls and retries to the predicate may be counted. Profiling data can be read through the `call_count_data/3` built-in.

  `char_conversion [ISO]`

    Writable flag telling whether a character conversion table is used when reading terms. The default value for this flag is `off` except in `sicstus` and `iso` language modes, where it is `on`.

  `character_escapes [ISO]`

    Writable flag telling whether a character escapes are enables, `on`, or disabled, `off`. The default value for this flag is `on`.

  `debug [ISO]`

    If Value is unbound, tell whether debugging is `on` or `off`. If Value is bound to `on` enable debugging, and if it is bound to `off` disable debugging.

    +

  `debugger_print_options`

    If bound, set the argument to the `write_term/3` options the debugger uses to write terms. If unbound, show the current options.

  `dialect`

    Read-only flag that always returns `yap`.

  `discontiguous_warnings`

    If Value is unbound, tell whether warnings for discontiguous predicates are `on` or `off`. If Value is bound to `on` enable these warnings, and if it is bound to `off` disable them. The default for YAP is `off`, unless we are in `sicstus` or `iso` mode.

  `dollar_as_lower_case`

    If `off` (default) consider the character ’$’ a control character, if `on` consider ’$’ a lower case character.

  `double_quotes [ISO]`

    If Value is unbound, tell whether a double quoted list of characters token is converted to a list of atoms, `chars`, to a list of integers, `codes`, or to a single atom, `atom`. If Value is bound, set to the corresponding behavior. The default value is `codes`.

  `executable`

    Read-only flag. It unifies with an atom that gives the original program path.

  `fast`

    If `on` allow fast machine code, if `off` (default) disable it. Only available in experimental implementations.

  `fileerrors`

    If `on` `fileerrors` is `on`, if `off` (default) `fileerrors` is disabled.

  `float_format`

    C-library `printf()` format specification used by `write/1` and friends to determine how floating point numbers are printed. The default is `%.15g`. The specified value is passed to `printf()` without further checking. For example, if you want less digits printed, `%g` will print all floats using 6 digits instead of the default 15.

  `gc`

    If `on` allow garbage collection (default), if `off` disable it.

  `gc_margin`

    Set or show the minimum free stack before starting garbage collection. The default depends on total stack size.

  `gc_trace`

    If `off` (default) do not show information on garbage collection and stack shifts, if `on` inform when a garbage collection or stack shift happened, if `verbose` give detailed information on garbage collection and stack shifts. Last, if `very_verbose` give detailed information on data-structures found during the garbage collection process, namely, on choice-points.

  `generate_debugging_info`

    If `true` (default) generate debugging information for procedures, including source mode. If `false` predicates no information is generated, although debugging is still possible, and source mode is disabled.

  `host_type`

    Return `configure` system information, including the machine-id for which YAP was compiled and Operating System information.

  `index`

    If `on` allow indexing (default), if `off` disable it.

  `informational_messages`

    If `on` allow printing of informational messages, such as the ones that are printed when consulting. If `off` disable printing these messages. It is `on` by default except if YAP is booted with the `-L` flag.

  `integer_rounding_function [ISO]`

    Read-only flag telling the rounding function used for integers. Takes the value `down` for the current version of YAP.

  `language`

    Choose whether YAP is closer to C-Prolog, `cprolog`, iso-prolog, `iso` or SICStus Prolog, `sicstus`. The current default is `cprolog`. This flag affects update semantics, leashing mode, style checking, handling calls to undefined procedures, how directives are interpreted, when to use dynamic, character escapes, and how files are consulted.

  `max_arity [ISO]`

    Read-only flag telling the maximum arity of a functor. Takes the value `unbounded` for the current version of YAP.

  `max_integer [ISO]`

    Read-only flag telling the maximum integer in the implementation. Depends on machine and Operating System architecture, and on whether YAP uses the `GMP` multi-precision library. If `bounded` is false, requests for `max_integer` will fail.

  `max_tagged_integer`

    Read-only flag telling the maximum integer we can store as a single word. Depends on machine and Operating System architecture. It can be used to find the word size of the current machine.

  `min_integer [ISO]`

    Read-only flag telling the minimum integer in the implementation. Depends on machine and Operating System architecture, and on whether YAP uses the `GMP` multi-precision library. If `bounded` is false, requests for `min_integer` will fail.

  `min_tagged_integer`

    Read-only flag telling the minimum integer we can store as a single word. Depends on machine and Operating System architecture.

  `n_of_integer_keys_in_bb`

    Read or set the size of the hash table that is used for looking up the blackboard when the key is an integer.

  `n_of_integer_keys_in_db`

    Read or set the size of the hash table that is used for looking up the internal data-base when the key is an integer.

  `open_expands_filename`

    If `true` the `open/3` builtin performs filename-expansion before opening a file (SICStus Prolog like). If `false` it does not (SWI-Prolog like).

  `open_shared_object`

    If true, `open_shared_object/2` and friends are implemented, providing access to shared libraries (`.so` files) or to dynamic link libraries (`.DLL` files).

  `profiling`

    If `off` (default) do not compile profiling information for procedures. If `on` compile predicates so that they will output profiling information. Profiling data can be read through the `profile_data/3` built-in.

  `prompt_alternatives_on(atom, changeable)`

    SWI-Compatible option, determines prompting for alternatives in the Prolog toplevel. Default is `groundness`, YAP prompts for alternatives if and only if the query contains variables. The alternative, default in SWI-Prolog is `determinism` which implies the system prompts for alternatives if the goal succeeded while leaving choicepoints.

  `redefine_warnings`

    If Value is unbound, tell whether warnings for procedures defined in several different files are `on` or `off`. If Value is bound to `on` enable these warnings, and if it is bound to `off` disable them. The default for YAP is `off`, unless we are in `sicstus` or `iso` mode.

  `shared_object_search_path`

    Name of the environment variable used by the system to search for shared objects.

  `single_var_warnings`

    If Value is unbound, tell whether warnings for singleton variables are `on` or `off`. If Value is bound to `on` enable these warnings, and if it is bound to `off` disable them. The default for YAP is `off`, unless we are in `sicstus` or `iso` mode.

  `strict_iso`

    If Value is unbound, tell whether strict ISO compatibility mode is `on` or `off`. If Value is bound to `on` set language mode to `iso` and enable strict mode. If Value is bound to `off` disable strict mode, and keep the current language mode. The default for YAP is `off`.

    Under strict ISO Prolog mode all calls to non-ISO built-ins generate an error. Compilation of clauses that would call non-ISO built-ins will also generate errors. Pre-processing for grammar rules is also disabled. Module expansion is still performed.

    Arguably, ISO Prolog does not provide all the functionality required from a modern Prolog system. Moreover, because most Prolog implementations do not fully implement the standard and because the standard itself gives the implementor latitude in a few important questions, such as the unification algorithm and maximum size for numbers there is no guarantee that programs compliant with this mode will work the same way in every Prolog and in every platform. We thus believe this mode is mostly useful when investigating how a program depends on a Prolog’s platform specific features.

  `stack_dump_on_error`

    If `on` show a stack dump when YAP finds an error. The default is `off`.

  `syntax_errors`

    Control action to be taken after syntax errors while executing `read/1`, `read/2`, or `read_term/3`:

    `dec10`

      Report the syntax error and retry reading the term.

    `fail`

      Report the syntax error and fail (default).

    `error`

      Report the syntax error and generate an error.

    `quiet`

      Just fail

  `system_options`

    This read only flag tells which options were used to compile YAP. Currently it informs whether the system supports `big_numbers`, `coroutining`, `depth_limit`, `low_level_tracer`, `or-parallelism`, `rational_trees`, `readline`, `tabling`, `threads`, or the `wam_profiler`.

  `tabling_mode`

    Sets or reads the tabling mode for all tabled predicates. Please see section Tabling for the list of options.

  `to_chars_mode`

    Define whether YAP should follow `quintus`-like semantics for the `atom_chars/1` or `number_chars/1` built-in, or whether it should follow the ISO standard (`iso` option).

    +

  `toplevel_hook`

    +If bound, set the argument to a goal to be executed before entering the top-level. If unbound show the current goal or `true` if none is presented. Only the first solution is considered and the goal is not backtracked into.

    +

  `toplevel_print_options`

    +If bound, set the argument to the `write_term/3` options used to write terms from the top-level. If unbound, show the current options.

  `typein_module`

    If bound, set the current working or type-in module to the argument, which must be an atom. If unbound, unify the argument with the current working module.

  `unix`

    Read-only Boolean flag that unifies with `true` if YAP is running on an Unix system. Defined if the C-compiler used to compile this version of YAP either defines `__unix__` or `unix`.

  `unknown [ISO]`

    Corresponds to calling the `unknown/2` built-in. Possible values are `error`, `fail`, and `warning`.

  `update_semantics`

    Define whether YAP should follow `immediate` update semantics, as in C-Prolog (default), `logical` update semantics, as in Quintus Prolog, SICStus Prolog, or in the ISO standard. There is also an intermediate mode, `logical_assert`, where dynamic procedures follow logical semantics but the internal data base still follows immediate semantics.

  `user_error`

    If the second argument is bound to a stream, set `user_error` to this stream. If the second argument is unbound, unify the argument with the current `user_error` stream.

    By default, the `user_error` stream is set to a stream corresponding to the Unix `stderr` stream.

    The next example shows how to use this flag:

           ?- open( '/dev/null', append, Error,
                   [alias(mauri_tripa)] ).

        Error = '$stream'(3) ? ;

        no
           ?- set_prolog_flag(user_error, mauri_tripa).

        close(mauri_tripa).

        yes
           ?-

    We execute three commands. First, we open a stream in write mode and give it an alias, in this case `mauri_tripa`. Next, we set `user_error` to the stream via the alias. Note that after we did so prompts from the system were redirected to the stream `mauri_tripa`. Last, we close the stream. At this point, YAP automatically redirects the `user_error` alias to the original `stderr`.

  `user_flags`

    Define the behaviour of `set_prolog_flag/2` if the flag is not known. Values are `silent`, `warning` and `error`. The first two create the flag on-the-fly, with `warning` printing a message. The value `error` is consistent with ISO: it raises an existence error and does not create the flag. See also `create_prolog_flag/3`. The default is`error`, and developers are encouraged to use `create_prolog_flag/3` to create flags for their library.

  `user_input`

    If the second argument is bound to a stream, set `user_input` to this stream. If the second argument is unbound, unify the argument with the current `user_input` stream.

    By default, the `user_input` stream is set to a stream corresponding to the Unix `stdin` stream.

  `user_output`

    If the second argument is bound to a stream, set `user_output` to this stream. If the second argument is unbound, unify the argument with the current `user_output` stream.

    By default, the `user_output` stream is set to a stream corresponding to the Unix `stdout` stream.

  `verbose`

    If `normal` allow printing of informational and banner messages, such as the ones that are printed when consulting. If `silent` disable printing these messages. It is `normal` by default except if YAP is booted with the `-q` or `-L` flag.

  `verbose_load`

    If `true` allow printing of informational messages when consulting files. If `false` disable printing these messages. It is `normal` by default except if YAP is booted with the `-L` flag.

  `version`

    Read-only flag that returns an atom with the current version of YAP.

  `version_data`

    Read-only flag that reads a term of the form `yap`(Major,Minor,Patch,Undefined), where Major is the major version, Minor is the minor version, and Patch is the patch number.

  `windows`

    Read-only boolean flag that unifies with tr `true` if YAP is running on an Windows machine.

  `write_strings`

    Writable flag telling whether the system should write lists of integers that are writable character codes using the list notation. It is `on` if enables or `off` if disabled. The default value for this flag is `off`.

  `max_workers`

    Read-only flag telling the maximum number of parallel processes.

  `max_threads`

    Read-only flag telling the maximum number of Prolog threads that can be created.

`current_prolog_flag(?Flag,-Value) [ISO]`

  Obtain the value for a YAP Prolog flag. Equivalent to calling `yap_flag/2` with the second argument unbound, and unifying the returned second argument with Value.

`prolog_flag(?Flag,-OldValue,+NewValue)`

  Obtain the value for a YAP Prolog flag and then set it to a new value. Equivalent to first calling `current_prolog_flag/2` with the second argument OldValue unbound and then calling `set_prolog_flag/2` with the third argument NewValue.

`set_prolog_flag(+Flag,+Value) [ISO]`

  Set the value for YAP Prolog flag `Flag`. Equivalent to calling `yap_flag/2` with both arguments bound.

`create_prolog_flag(+Flag,+Value,+Options)`

  Create a new YAP Prolog flag. Options include `type(+Type)` and `access(+Access)` with Access one of `read_only` or `read_write` and Type one of `boolean`, `integer`, `float`, `atom` and `term` (that is, no type).

`op(+P,+T,+A) [ISO]`

  Defines the operator A or the list of operators A with type T (which must be one of `xfx`, `xfy`,`yfx`, `xf`, `yf`, `fx` or `fy`) and precedence P (see appendix iv for a list of predefined operators).

  Note that if there is a preexisting operator with the same name and type, this operator will be discarded. Also, `','` may not be defined as an operator, and it is not allowed to have the same for an infix and a postfix operator.

`current_op(P,T,F) [ISO]`

  Defines the relation: P is a currently defined operator of type T and precedence P.

`prompt(-A,+B)`

  Changes YAP input prompt from A to B.

`initialization`

  Execute the goals defined by initialization/1. Only the first answer is considered.

`prolog_initialization(G)`

  Add a goal to be executed on system initialization. This is compatible with SICStus Prolog’s `initialization/1`.

`version`

  Write YAP’s boot message.

`version(-Message)`

  Add a message to be written when yap boots or after aborting. It is not possible to remove messages.

`prolog_load_context(?Key, ?Value)`

  Obtain information on what is going on in the compilation process. The following keys are available:

  `directory`

    Full name for the directory where YAP is currently consulting the file.

  `file`

    Full name for the file currently being consulted. Notice that included filed are ignored.

  `module`

    Current source module.

  `source`

    Full name for the file currently being read in, which may be consulted, reconsulted, or included.

  `stream`

    Stream currently being read in.

  `term_position`

    Stream position at the stream currently being read in.

`source_location(?FileName, ?Line)`

  SWI-compatible predicate. If the last term has been read from a physical file (i.e., not from the file user or a string), unify File with an absolute path to the file and Line with the line-number in the file. Please use `prolog_load_context/2`.

`source_file(?File)`

  SWI-compatible predicate. True if File is a loaded Prolog source file.

`source_file(?ModuleAndPred,?File)`

  SWI-compatible predicate. True if the predicate specified by ModuleAndPred was loaded from file File, where File is an absolute path name (see `absolute_file_name/2`).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 7 Library Predicates

Library files reside in the library_directory path (set by the `LIBDIR` variable in the Makefile for YAP). Currently, most files in the library are from the Edinburgh Prolog library.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.1 Aggregate

This is the SWI-Prolog library based on the Quintus and SICStus 4 library. Notice that `forall/2` is a SWI-Prolog built-in and `term_variables/3` is a SWI-Prolog with a different definition.

This library provides aggregating operators over the solutions of a predicate. The operations are a generalisation of the `bagof/3`, `setof/3` and `findall/3` built-in predicates. The defined aggregation operations are counting, computing the sum, minimum, maximum, a bag of solutions and a set of solutions. We first give a simple example, computing the country with the smallest area:

    smallest_country(Name, Area) :-
            aggregate(min(A, N), country(N, A), min(Area, Name)).

There are four aggregation predicates, distinguished on two properties.

`aggregate vs. aggregate_all`

  The aggregate predicates use setof/3 (aggregate/4) or bagof/3 (aggregate/3), dealing with existential qualified variables (Var/\Goal) and providing multiple solutions for the remaining free variables in Goal. The aggregate_all/3 predicate uses findall/3, implicitly qualifying all free variables and providing exactly one solution, while aggregate_all/4 uses sort/2 over solutions and Distinguish (see below) generated using findall/3.

`The Distinguish argument`

  The versions with 4 arguments provide a Distinguish argument that allow for keeping duplicate bindings of a variable in the result. For example, if we wish to compute the total population of all countries we do not want to lose results because two countries have the same population. Therefore we use:

              aggregate(sum(P), Name, country(Name, P), Total)

All aggregation predicates support the following operator below in Template. In addition, they allow for an arbitrary named compound term where each of the arguments is a term from the list below. I.e. the term `r(min(X), max(X))` computes both the minimum and maximum binding for X.

`count`

  Count number of solutions. Same as `sum(1)`.

`sum(Expr)`

  Sum of Expr for all solutions.

`min(Expr)`

  Minimum of Expr for all solutions.

`min(Expr, Witness)`

  A term min(Min, Witness), where Min is the minimal version of Expr over all Solution and Witness is any other template applied to Solution that produced Min. If multiple solutions provide the same minimum, Witness corresponds to the first solution.

`max(Expr)`

  Maximum of Expr for all solutions.

`max(Expr, Witness)`

  As min(Expr, Witness), but producing the maximum result.

`set(X)`

  An ordered set with all solutions for X.

`bag(X)`

  A list of all solutions for X.

The predicates are:

`[nondet]aggregate(+Template, :Goal, -Result)`

  Aggregate bindings in Goal according to Template. The aggregate/3 version performs bagof/3 on Goal.

`[nondet]aggregate(+Template, +Discriminator, :Goal, -Result)`

  Aggregate bindings in Goal according to Template. The aggregate/3 version performs setof/3 on Goal.

`[semidet]aggregate_all(+Template, :Goal, -Result)`

  Aggregate bindings in Goal according to Template. The aggregate_all/3 version performs findall/3 on Goal.

`[semidet]aggregate_all(+Template, +Discriminator, :Goal, -Result)`

  Aggregate bindings in Goal according to Template. The aggregate_all/3 version performs findall/3 followed by sort/2 on Goal.

`foreach(:Generator, :Goal)`

  True if the conjunction of instances of Goal using the bindings from Generator is true. Unlike forall/2, which runs a failure-driven loop that proves Goal for each solution of Generator, foreach creates a conjunction. Each member of the conjunction is a copy of Goal, where the variables it shares with Generator are filled with the values from the corresponding solution.

  The implementation executes forall/2 if Goal does not contain any variables that are not shared with Generator.

  Here is an example:

          ?- foreach(between(1,4,X), dif(X,Y)), Y = 5.
          Y = 5
          ?- foreach(between(1,4,X), dif(X,Y)), Y = 3.
          No

  Notice that Goal is copied repeatedly, which may cause problems if attributed variables are involved.

`[det]free_variables(:Generator, +Template, +VarList0, -VarList)`

  In order to handle variables properly, we have to find all the universally quantified variables in the Generator. All variables as yet unbound are universally quantified, unless

  1. they occur in the template
  2. they are bound by X/\P, setof, or bagof

  `free_variables(Generator, Template, OldList, NewList)` finds this set, using OldList as an accumulator.

The original author of this code was Richard O’Keefe. Jan Wielemaker made some SWI-Prolog enhancements, sponsored by SecuritEase, http://www.securitease.com. The code is public domain (from DEC10 library).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.2 Apply Macros

This library provides a SWI-compatible set of utilities for applying a predicate to all elements of a list. The library just forwards definitions from the `maplist` library.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.3 Association Lists

The following association list manipulation predicates are available once included with the `use_module(library(assoc))` command. The original library used Richard O’Keefe’s implementation, on top of unbalanced binary trees. The current code utilises code from the red-black trees library and emulates the SICStus Prolog interface.

`assoc_to_list(+Assoc,?List)`

  Given an association list Assoc unify List with a list of the form Key-Val, where the elements Key are in ascending order.

`del_assoc(+Key, +Assoc, ?Val, ?NewAssoc)`

  Succeeds if NewAssoc is an association list, obtained by removing the element with Key and Val from the list Assoc.

`del_max_assoc(+Assoc, ?Key, ?Val, ?NewAssoc)`

  Succeeds if NewAssoc is an association list, obtained by removing the largest element of the list, with Key and Val from the list Assoc.

`del_min_assoc(+Assoc, ?Key, ?Val, ?NewAssoc)`

  Succeeds if NewAssoc is an association list, obtained by removing the smallest element of the list, with Key and Val from the list Assoc.

`empty_assoc(+Assoc)`

  Succeeds if association list Assoc is empty.

`gen_assoc(+Assoc,?Key,?Value)`

  Given the association list Assoc, unify Key and Value with two associated elements. It can be used to enumerate all elements in the association list.

`get_assoc(+Key,+Assoc,?Value)`

  If Key is one of the elements in the association list Assoc, return the associated value.

`get_assoc(+Key,+Assoc,?Value,+NAssoc,?NValue)`

  If Key is one of the elements in the association list Assoc, return the associated value Value and a new association list NAssoc where Key is associated with NValue.

`get_prev_assoc(+Key,+Assoc,?Next,?Value)`

  If Key is one of the elements in the association list Assoc, return the previous key, Next, and its value, Value.

`get_next_assoc(+Key,+Assoc,?Next,?Value)`

  If Key is one of the elements in the association list Assoc, return the next key, Next, and its value, Value.

`is_assoc(+Assoc)`

  Succeeds if Assoc is an association list, that is, if it is a red-black tree.

`list_to_assoc(+List,?Assoc)`

  Given a list List such that each element of List is of the form Key-Val, and all the Keys are unique, Assoc is the corresponding association list.

`map_assoc(+Pred,+Assoc)`

  Succeeds if the unary predicate name Pred(Val) holds for every element in the association list.

`map_assoc(+Pred,+Assoc,?New)`

  Given the binary predicate name Pred and the association list Assoc, New in an association list with keys in Assoc, and such that if Key-Val is in Assoc, and Key-Ans is in New, then Pred(Val,Ans) holds.

`max_assoc(+Assoc,-Key,?Value)`

  Given the association list Assoc, Key in the largest key in the list, and Value the associated value.

`min_assoc(+Assoc,-Key,?Value)`

  Given the association list Assoc, Key in the smallest key in the list, and Value the associated value.

`ord_list_to_assoc(+List,?Assoc)`

  Given an ordered list List such that each element of List is of the form Key-Val, and all the Keys are unique, Assoc is the corresponding association list.

`put_assoc(+Key,+Assoc,+Val,+New)`

  The association list New includes and element of association key with Val, and all elements of Assoc that did not have key Key.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.4 AVL Trees

AVL trees are balanced search binary trees. They are named after their inventors, Adelson-Velskii and Landis, and they were the first dynamically balanced trees to be proposed. The YAP AVL tree manipulation predicates library uses code originally written by Martin van Emdem and published in the Logic Programming Newsletter, Autumn 1981. A bug in this code was fixed by Philip Vasey, in the Logic Programming Newsletter, Summer 1982. The library currently only includes routines to insert and lookup elements in the tree. Please try red-black trees if you need deletion.

`avl_new(+T)`

  Create a new tree.

`avl_insert(+Key,?Value,+T0,-TF)`

  Add an element with key Key and Value to the AVL tree T0 creating a new AVL tree TF. Duplicated elements are allowed.

`avl_lookup(+Key,-Value,+T)`

  Lookup an element with key Key in the AVL tree T, returning the value Value.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.5 Heaps

A heap is a labelled binary tree where the key of each node is less than or equal to the keys of its sons. The point of a heap is that we can keep on adding new elements to the heap and we can keep on taking out the minimum element. If there are N elements total, the total time is O(NlgN). If you know all the elements in advance, you are better off doing a merge-sort, but this file is for when you want to do say a best-first search, and have no idea when you start how many elements there will be, let alone what they are.

The following heap manipulation routines are available once included with the `use_module(library(heaps))` command.

`add_to_heap(+Heap,+key,+Datum,-NewHeap)`

  Inserts the new Key-Datum pair into the heap. The insertion is not stable, that is, if you insert several pairs with the same Key it is not defined which of them will come out first, and it is possible for any of them to come out first depending on the history of the heap.

`empty_heap(?Heap)`

  Succeeds if Heap is an empty heap.

`get_from_heap(+Heap,-key,-Datum,-Heap)`

  Returns the Key-Datum pair in OldHeap with the smallest Key, and also a Heap which is the OldHeap with that pair deleted.

`heap_size(+Heap, -Size)`

  Reports the number of elements currently in the heap.

`heap_to_list(+Heap, -List)`

  Returns the current set of Key-Datum pairs in the Heap as a List, sorted into ascending order of Keys.

`list_to_heap(+List, -Heap)`

  Takes a list of Key-Datum pairs (such as keysort could be used to sort) and forms them into a heap.

`min_of_heap(+Heap, -Key, -Datum)`

  Returns the Key-Datum pair at the top of the heap (which is of course the pair with the smallest Key), but does not remove it from the heap.

`min_of_heap(+Heap, -Key1, -Datum1,`

  -Key2, -Datum2) Returns the smallest (Key1) and second smallest (Key2) pairs in the heap, without deleting them.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.6 List Manipulation

The following list manipulation routines are available once included with the `use_module(library(lists))` command.

`append(?Prefix,?Suffix,?Combined)`

  True when all three arguments are lists, and the members of Combined are the members of Prefix followed by the members of Suffix. It may be used to form Combined from a given Prefix, Suffix or to take a given Combined apart.

`append(?Lists,?Combined)`

  Holds if the lists of Lists can be concatenated as a Combined list.

`delete(+List, ?Element, ?Residue)`

  True when List is a list, in which Element may or may not occur, and Residue is a copy of List with all elements identical to Element deleted.

`flatten(+List, ?FlattenedList)`

  Flatten a list of lists List into a single list FlattenedList.

      ?- flatten([[1],[2,3],[4,[5,6],7,8]],L).

      L = [1,2,3,4,5,6,7,8] ? ;

      no

`last(+List,?Last)`

  True when List is a list and Last is identical to its last element.

`list_concat(+Lists,?List)`

  True when Lists is a list of lists and List is the concatenation of Lists.

`member(?Element, ?Set)`

  True when Set is a list, and Element occurs in it. It may be used to test for an element or to enumerate all the elements by backtracking.

`memberchk(+Element, +Set)`

  As `member/2`, but may only be used to test whether a known Element occurs in a known Set. In return for this limited use, it is more efficient when it is applicable.

`nth0(?N, ?List, ?Elem)`

  True when Elem is the Nth member of List, counting the first as element 0. (That is, throw away the first N elements and unify Elem with the next.) It can only be used to select a particular element given the list and index. For that task it is more efficient than `member/2`

`nth1(?N, ?List, ?Elem)`

  The same as `nth0/3`, except that it counts from 1, that is `nth(1, [H|_], H)`.

`nth(?N, ?List, ?Elem)`

  The same as `nth1/3`.

`nth0(?N, ?List, ?Elem, ?Rest)`

  Unifies Elem with the Nth element of List, counting from 0, and Rest with the other elements. It can be used to select the Nth element of List (yielding Elem and Rest), or to insert Elem before the Nth (counting from 1) element of Rest, when it yields List, e.g. `nth0(2, List, c, [a,b,d,e])` unifies List with `[a,b,c,d,e]`. `nth/4` is the same except that it counts from 1. `nth0/4` can be used to insert Elem after the Nth element of Rest.

`nth1(?N, ?List, ?Elem, ?Rest)`

  Unifies Elem with the Nth element of List, counting from 1, and Rest with the other elements. It can be used to select the Nth element of List (yielding Elem and Rest), or to insert Elem before the Nth (counting from 1) element of Rest, when it yields List, e.g. `nth(3, List, c, [a,b,d,e])` unifies List with `[a,b,c,d,e]`. `nth/4` can be used to insert Elem after the Nth element of Rest.

`nth(?N, ?List, ?Elem, ?Rest)`

  Same as `nth1/4`.

`permutation(+List,?Perm)`

  True when List and Perm are permutations of each other.

`remove_duplicates(+List, ?Pruned)`

  Removes duplicated elements from List. Beware: if the List has non-ground elements, the result may surprise you.

`reverse(+List, ?Reversed)`

  True when List and Reversed are lists with the same elements but in opposite orders.

`same_length(?List1, ?List2)`

  True when List1 and List2 are both lists and have the same number of elements. No relation between the values of their elements is implied. Modes `same_length(-,+)` and `same_length(+,-)` generate either list given the other; mode `same_length(-,-)` generates two lists of the same length, in which case the arguments will be bound to lists of length 0, 1, 2, ...

`select(?Element, ?List, ?Residue)`

  True when Set is a list, Element occurs in List, and Residue is everything in List except Element (things stay in the same order).

`selectchk(?Element, ?List, ?Residue)`

  Semi-deterministic selection from a list. Steadfast: defines as

      selectchk(Elem, List, Residue) :-
              select(Elem, List, Rest0), !,
              Rest = Rest0.

`sublist(?Sublist, ?List)`

  True when both `append(_,Sublist,S)` and `append(S,_,List)` hold.

`suffix(?Suffix, ?List)`

  Holds when `append(_,Suffix,List)` holds.

`sum_list(?Numbers, ?Total)`

  True when Numbers is a list of numbers, and Total is their sum.

`sum_list(?Numbers, +SoFar, ?Total)`

  True when Numbers is a list of numbers, and Total is the sum of their total plus SoFar.

`sumlist(?Numbers, ?Total)`

  True when Numbers is a list of integers, and Total is their sum. The same as `sum_list/2`, please do use `sum_list/2` instead.

`max_list(?Numbers, ?Max)`

  True when Numbers is a list of numbers, and Max is the maximum.

`min_list(?Numbers, ?Min)`

  True when Numbers is a list of numbers, and Min is the minimum.

`numlist(+Low, +High, +List)`

  If Low and High are integers with Low =< High, unify List to a list `[Low, Low+1, ...High]`. See also `between/3`.

`intersection(+Set1, +Set2, +Set3)`

  Succeeds if Set3 unifies with the intersection of Set1 and Set2. Set1 and Set2 are lists without duplicates. They need not be ordered.

`subtract(+Set, +Delete, ?Result)`

  Delete all elements from Set that occur in Delete (a set) and unify the result with Result. Deletion is based on unification using `memberchk/2`. The complexity is `|Delete|*|Set|`.

  See `ord_subtract/3`.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.7 Line Manipulation Utilities

This package provides a set of useful predicates to manipulate sequences of characters codes, usually first read in as a line. It is available by loading the library `library(lineutils)`.

`search_for(+Char,+Line)`

  Search for a character Char in the list of codes Line.

`search_for(+Char,+Line)`

  Search for a character Char in the list of codes Line.

`search_for(+Char,+Line,-RestOfine)`

  Search for a character Char in the list of codes Line, RestOfLine has the line to the right.

`scan_natural(?Nat,+Line,+RestOfLine)`

  Scan the list of codes Line for a natural number Nat, zero or a positive integer, and unify RestOfLine with the remainder of the line.

`scan_integer(?Int,+Line,+RestOfLine)`

  Scan the list of codes Line for an integer Nat, either a positive, zero, or negative integer, and unify RestOfLine with the remainder of the line.

`split(+Line,+Separators,-Split)`

  Unify Words with a set of strings obtained from Line by using the character codes in Separators as separators. As an example, consider:

      ?- split("Hello * I am free"," *",S).

      S = ["Hello","I","am","free"] ?

      no

`split(+Line,-Split)`

  Unify Words with a set of strings obtained from Line by using the blank characters as separators.

`fields(+Line,+Separators,-Split)`

  Unify Words with a set of strings obtained from Line by using the character codes in Separators as separators for fields. If two separators occur in a row, the field is considered empty. As an example, consider:

      ?- fields("Hello  I am  free"," *",S).

      S = ["Hello","","I","am","","free"] ?

`fields(+Line,-Split)`

  Unify Words with a set of strings obtained from Line by using the blank characters as field separators.

`glue(+Words,+Separator,-Line)`

  Unify Line with string obtained by glueing Words with the character code Separator.

`copy_line(+StreamInput,+StreamOutput)`

  Copy a line from StreamInput to StreamOutput.

`copy_line(+StreamInput,+StreamOutput)`

  Copy a line from StreamInput to StreamOutput.

`process(+StreamInp, +Goal)`

  For every line LineIn in stream StreamInp, call `call(Goal,LineIn)`.

`filter(+StreamInp, +StreamOut, +Goal)`

  For every line LineIn in stream StreamInp, execute `call(Goal,LineIn,LineOut)`, and output LineOut to stream StreamOut.

`file_filter(+FileIn, +FileOut, +Goal)`

  For every line LineIn in file FileIn, execute `call(Goal,LineIn,LineOut)`, and output LineOut to file FileOut.

`file_filter(+FileIn, +FileOut, +Goal,`

  +FormatCommand, +Arguments)

  Same as `file_filter/3`, but before starting the filter execute `format/3` on the output stream, using FormatCommand and Arguments.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.8 Maplist

This library provides a set of utilities for applying a predicate to all elements of a list or to all sub-terms of a term. They allow to easily perform the most common do-loop constructs in Prolog. To avoid performance degradation due to `apply/2`, each call creates an equivalent Prolog program, without meta-calls, which is executed by the Prolog engine instead. Note that if the equivalent Prolog program already exists, it will be simply used. The library is based on code by Joachim Schimpf and on code from SWI-Prolog.

The following routines are available once included with the `use_module(library(apply_macros))` command.

`maplist(+Pred, ?ListIn, ?ListOut)`

  Creates ListOut by applying the predicate Pred to all elements of ListIn.

`maplist(+Pred, ?ListIn)`

  Creates ListOut by applying the predicate Pred to all elements of ListIn.

`maplist(+Pred, ?L1, ?L2, ?L3)`

  L1, L2, and L3 are such that `call(Pred,A1,A2,A3)` holds for every corresponding element in lists L1, L2, and L3.

`maplist(+Pred, ?L1, ?L2, ?L3, ?L4)`

  L1, L2, L3, and L4 are such that `call(Pred,A1,A2,A3,A4)` holds for every corresponding element in lists L1, L2, L3, and L4.

`checklist(+Pred, +List)`

  Succeeds if the predicate Pred succeeds on all elements of List.

`selectlist(+Pred, +ListIn, ?ListOut)`

  Creates ListOut of all list elements of ListIn that pass a given test

`convlist(+Pred, +ListIn, ?ListOut)`

  A combination of `maplist` and `selectlist`: creates ListOut by applying the predicate Pred to all list elements on which Pred succeeds

`sumlist(+Pred, +List, ?AccIn, ?AccOut)`

  Calls Pred on all elements of List and collects a result in Accumulator.

`mapargs(+Pred, ?TermIn, ?TermOut)`

  Creates TermOut by applying the predicate Pred to all arguments of TermIn

`sumargs(+Pred, +Term, ?AccIn, ?AccOut)`

  Calls the predicate Pred on all arguments of Term and collects a result in Accumulator

`mapnodes(+Pred, +TermIn, ?TermOut)`

  Creates TermOut by applying the predicate Pred to all sub-terms of TermIn (depth-first and left-to-right order)

`checknodes(+Pred, +Term)`

  Succeeds if the predicate Pred succeeds on all sub-terms of Term (depth-first and left-to-right order)

`sumnodes(+Pred, +Term, ?AccIn, ?AccOut)`

  Calls the predicate Pred on all sub-terms of Term and collect a result in Accumulator (depth-first and left-to-right order)

`include(+Pred, +ListIn, ?ListOut)`

  Same as `selectlist/3`.

`exclude(+Goal, +List1, ?List2)`

  Filter elements for which Goal fails. True if List2 contains those elements Xi of List1 for which `call(Goal, Xi)` fails.

`partition(+Pred, +List1, ?Included, ?Excluded)`

  Filter elements of List according to Pred. True if Included contains all elements for which `call(Pred, X)` succeeds and Excluded contains the remaining elements.

`partition(+Pred, +List1, ?Lesser, ?Equal, ?Greater)`

  Filter list according to Pred in three sets. For each element Xi of List, its destination is determined by `call(Pred, Xi, Place)`, where Place must be unified to one of `<`, `=` or `>`. `Pred` must be deterministic.

Examples:

    %given
    plus(X,Y,Z) :- Z is X + Y.
    plus_if_pos(X,Y,Z) :- Y > 0, Z is X + Y.
    vars(X, Y, [X|Y]) :- var(X), !.
    vars(_, Y, Y).
    trans(TermIn, TermOut) :-
      nonvar(TermIn),
      TermIn =.. [p|Args],
      TermOut =..[q|Args], !.
    trans(X,X).

    %success

    maplist(plus(1), [1,2,3,4], [2,3,4,5]).
    checklist(var, [X,Y,Z]).
    selectlist(<(0), [-1,0,1], [1]).
    convlist(plus_if_pos(1), [-1,0,1], [2]).
    sumlist(plus, [1,2,3,4], 1, 11).
    mapargs(number_atom,s(1,2,3), s('1','2','3')).
    sumargs(vars, s(1,X,2,Y), [], [Y,X]).m
    apnodes(trans, p(a,p(b,a),c), q(a,q(b,a),c)).
    checknodes(\==(T), p(X,p(Y,X),Z)).
    sumnodes(vars, [c(X), p(X,Y), q(Y)], [], [Y,Y,X,X]).
    % another one
    maplist(mapargs(number_atom),[c(1),s(1,2,3)],[c('1'),s('1','2','3')]).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.9 Matrix Library

This package provides a fast implementation of multi-dimensional matrices of integers and floats. In contrast to dynamic arrays, these matrices are multi-dimensional and compact. In contrast to static arrays. these arrays are allocated in the stack. Matrices are available by loading the library `library(matrix)`.

Notice that the functionality in this library is only partial. Please contact the YAP maintainers if you require extra functionality.

`matrix_new(+Type,+Dims,-Matrix)`

  Create a new matrix Matrix of type Type, which may be one of `ints` or `floats`, and with a list of dimensions Dims. The matrix will be initialised to zeros.

      ?- matrix_new(ints,[2,3],Matrix).

      Matrix = 0

  Notice that currently YAP will always write a matrix as `0`.

`matrix_new(+Type,+Dims,+List,-Matrix)`

  Create a new matrix Matrix of type Type, which may be one of `ints` or `floats`, with dimensions Dims, and initialised from list List.

`matrix_new_set(?Dims,+OldMatrix,+Value,-NewMatrix)`

  Create a new matrix NewMatrix of type Type, with dimensions Dims. The elements of NewMatrix are set to Value.

`matrix_dims(+Matrix,-Dims)`

  Unify Dims with a list of dimensions for Matrix.

`matrix_ndims(+Matrix,-Dims)`

  Unify NDims with the number of dimensions for Matrix.

`matrix_size(+Matrix,-NElems)`

  Unify NElems with the number of elements for Matrix.

`matrix_type(+Matrix,-Type)`

  Unify NElems with the type of the elements in Matrix.

`matrix_to_list(+Matrix,-Elems)`

  Unify Elems with the list including all the elements in Matrix.

`matrix_get(+Matrix,+Position,-Elem)`

  Unify Elem with the element of Matrix at position Position.

`matrix_set(+Matrix,+Position,+Elem)`

  Set the element of Matrix at position Position to Elem.

`matrix_set_all(+Matrix,+Elem)`

  Set all element of Matrix to Elem.

`matrix_add(+Matrix,+Position,+Operand)`

  Add Operand to the element of Matrix at position Position.

`matrix_inc(+Matrix,+Position)`

  Increment the element of Matrix at position Position.

`matrix_inc(+Matrix,+Position,-Element)`

  Increment the element of Matrix at position Position and unify with Element.

`matrix_dec(+Matrix,+Position)`

  Decrement the element of Matrix at position Position.

`matrix_dec(+Matrix,+Position,-Element)`

  Decrement the element of Matrix at position Position and unify with Element.

`matrix_arg_to_offset(+Matrix,+Position,-Offset)`

  Given matrix Matrix return what is the numerical Offset of the element at Position.

`matrix_offset_to_arg(+Matrix,-Offset,+Position)`

  Given a position Position for matrix Matrix return the corresponding numerical Offset from the beginning of the matrix.

`matrix_max(+Matrix,+Max)`

  Unify Max with the maximum in matrix Matrix.

`matrix_maxarg(+Matrix,+Maxarg)`

  Unify Max with the position of the maximum in matrix Matrix.

`matrix_min(+Matrix,+Min)`

  Unify Min with the minimum in matrix Matrix.

`matrix_minarg(+Matrix,+Minarg)`

  Unify Min with the position of the minimum in matrix Matrix.

`matrix_sum(+Matrix,+Sum)`

  Unify Sum with the sum of all elements in matrix Matrix.

`matrix_agg_lines(+Matrix,+Aggregate)`

  If Matrix is a n-dimensional matrix, unify Aggregate with the n-1 dimensional matrix where each element is obtained by adding all Matrix elements with same last n-1 index.

`matrix_agg_cols(+Matrix,+Aggregate)`

  If Matrix is a n-dimensional matrix, unify Aggregate with the one dimensional matrix where each element is obtained by adding all Matrix elements with same first index.

`matrix_op(+Matrix1,+Matrix2,+Op,-Result)`

  Result is the result of applying Op to matrix Matrix1 and Matrix2. Currently, only addition (`+`) is supported.

`matrix_op_to_all(+Matrix1,+Op,+Operand,-Result)`

  Result is the result of applying Op to all elements of Matrix1, with Operand as the second argument. Currently, only addition (`+`), multiplication (`+`), and division (`/`) are supported.

`matrix_op_to_lines(+Matrix1,+Lines,+Op,-Result)`

  Result is the result of applying Op to all elements of Matrix1, with the corresponding element in Lines as the second argument. Currently, only division (`/`) is supported.

`matrix_op_to_cols(+Matrix1,+Cols,+Op,-Result)`

  Result is the result of applying Op to all elements of Matrix1, with the corresponding element in Cols as the second argument. Currently, only addition (`+`) is supported. Notice that Cols will have n-1 dimensions.

`matrix_shuffle(+Matrix,+NewOrder,-Shuffle)`

  Shuffle the dimensions of matrix Matrix according to NewOrder. The list NewOrder must have all the dimensions of Matrix, starting from 0.

`matrix_transpose(+Matrix,-Transpose)`

  Transpose matrix Matrix to Transpose. Equivalent to:

      matrix_transpose(Matrix,Transpose) :-
              matrix_shuffle(Matrix,[1,0],Transpose).

`matrix_expand(+Matrix,+NewDimensions,-New)`

  Expand Matrix to occupy new dimensions. The elements in NewDimensions are either 0, for an existing dimension, or a positive integer with the size of the new dimension.

`matrix_select(+Matrix,+Dimension,+Index,-New)`

  Select from Matrix the elements who have Index at Dimension.

`matrix_column(+Matrix,+Column,-NewMatrix)`

  Select from Matrix the row matching Column as new matrix NewMatrix. Column must have one less dimension than the original matrix. Dimension.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.10 MATLAB Package Interface

The MathWorks MATLAB is a widely used package for array processing. YAP now includes a straightforward interface to MATLAB. To actually use it, you need to install YAP calling `configure` with the `--with-matlab=DIR` option, and you need to call `use_module(library(lists))` command.

Accessing the matlab dynamic libraries can be complicated. In Linux machines, to use this interface, you may have to set the environment variable `LD_LIBRARY_PATH`. Next, follows an example using bash in a 64-bit Linux PC:

    export LD_LIBRARY_PATH=''$MATLAB_HOME"/sys/os/glnxa64:''$MATLAB_HOME"/bin/glnxa64:''$LD_LIBRARY_PATH"

where `MATLAB_HOME` is the directory where matlab is installed at. Please replace `ax64` for `x86` on a 32-bit PC.

`start_matlab(+Options)`

  Start a matlab session. The argument Options may either be the empty string/atom or the command to call matlab. The command may fail.

`close_matlab`

  Stop the current matlab session.

`matlab_on`

  Holds if a matlab session is on.

`matlab_eval_string(+Command)`

  Holds if matlab evaluated successfully the command Command.

`matlab_eval_string(+Command, -Answer)`

  MATLAB will evaluate the command Command and unify Answer with a string reporting the result.

`matlab_cells(+Size, ?Array)`

  MATLAB will create an empty vector of cells of size Size, and if Array is bound to an atom, store the array in the matlab variable with name Array. Corresponds to the MATLAB command `cells`.

`matlab_cells(+SizeX, +SizeY, ?Array)`

  MATLAB will create an empty array of cells of size SizeX and SizeY, and if Array is bound to an atom, store the array in the matlab variable with name Array. Corresponds to the MATLAB command `cells`.

`matlab_initialized_cells(+SizeX, +SizeY, +List, ?Array)`

  MATLAB will create an array of cells of size SizeX and SizeY, initialized from the list List, and if Array is bound to an atom, store the array in the matlab variable with name Array.

`matlab_matrix(+SizeX, +SizeY, +List, ?Array)`

  MATLAB will create an array of floats of size SizeX and SizeY, initialized from the list List, and if Array is bound to an atom, store the array in the matlab variable with name Array.

`matlab_set(+MatVar, +X, +Y, +Value)`

  Call MATLAB to set element MatVar(X, Y) to Value. Notice that this command uses the MATLAB array access convention.

`matlab_get_variable(+MatVar, -List)`

  Unify MATLAB variable MatVar with the List List.

`matlab_item(+MatVar, +X, ?Val)`

  Read or set MATLAB MatVar(X) from/to Val. Use `C` notation for matrix access (ie, starting from 0).

`matlab_item(+MatVar, +X, +Y, ?Val)`

  Read or set MATLAB MatVar(X,Y) from/to Val. Use `C` notation for matrix access (ie, starting from 0).

`matlab_item1(+MatVar, +X, ?Val)`

  Read or set MATLAB MatVar(X) from/to Val. Use MATLAB notation for matrix access (ie, starting from 1).

`matlab_item1(+MatVar, +X, +Y, ?Val)`

  Read or set MATLAB MatVar(X,Y) from/to Val. Use MATLAB notation for matrix access (ie, starting from 1).

`matlab_sequence(+Min, +Max, ?Array)`

  MATLAB will create a sequence going from Min to Max, and if Array is bound to an atom, store the sequence in the matlab variable with name Array.

`matlab_vector(+Size, +List, ?Array)`

  MATLAB will create a vector of floats of size Size, initialized from the list List, and if Array is bound to an atom, store the array in the matlab variable with name Array.

`matlab_zeros(+Size, ?Array)`

  MATLAB will create a vector of zeros of size Size, and if Array is bound to an atom, store the array in the matlab variable with name Array. Corresponds to the MATLAB command `zeros`.

`matlab_zeros(+SizeX, +SizeY, ?Array)`

  MATLAB will create an array of zeros of size SizeX and SizeY, and if Array is bound to an atom, store the array in the matlab variable with name Array. Corresponds to the MATLAB command `zeros`.

`matlab_zeros(+SizeX, +SizeY, +SizeZ, ?Array)`

  MATLAB will create an array of zeros of size SizeX, SizeY, and SizeZ. If Array is bound to an atom, store the array in the matlab variable with name Array. Corresponds to the MATLAB command `zeros`.

`matlab_zeros(+SizeX, +SizeY, +SizeZ, ?Array)`

  MATLAB will create an array of zeros of size SizeX, SizeY, and SizeZ. If Array is bound to an atom, store the array in the matlab variable with name Array. Corresponds to the MATLAB command `zeros`.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.11 Non-Backtrackable Data Structures

The following routines implement well-known data-structures using global non-backtrackable variables (implemented on the Prolog stack). The data-structures currently supported are Queues, Heaps, and Beam for Beam search. They are allowed through `library(nb)`.

`nb_queue(-Queue)`

  Create a Queue.

`nb_queue_close(+Queue, -Head, ?Tail)`

  Unify the queue Queue with a difference list Head-Tail. The queue will now be empty and no further elements can be added.

`nb_queue_enqueue(+Queue, +Element)`

  Add Element to the front of the queue Queue.

`nb_queue_dequeue(+Queue, -Element)`

  Remove Element from the front of the queue Queue. Fail if the queue is empty.

`nb_queue_peek(+Queue, -Element)`

  Element is the front of the queue Queue. Fail if the queue is empty.

`nb_queue_size(+Queue, -Size)`

  Unify Size with the number of elements in the queue Queue.

`nb_queue_empty(+Queue)`

  Succeeds if Queue is empty.

`nb_heap(+DefaultSize,-Heap)`

  Create a Heap with default size DefaultSize. Note that size will expand as needed.

`nb_heap_close(+Heap)`

  Close the heap Heap: no further elements can be added.

`nb_heap_add(+Heap, +Key, +Value)`

  Add Key-Value to the heap Heap. The key is sorted on Key only.

`nb_heap_del(+Heap, -Key, -Value)`

  Remove element Key-Value with smallest Value in heap Heap. Fail if the heap is empty.

`nb_heap_peek(+Heap, -Key, -Value))`

  Key-Value is the element with smallest Key in the heap Heap. Fail if the heap is empty.

`nb_heap_size(+Heap, -Size)`

  Unify Size with the number of elements in the heap Heap.

`nb_heap_empty(+Heap)`

  Succeeds if Heap is empty.

`nb_beam(+DefaultSize,-Beam)`

  Create a Beam with default size DefaultSize. Note that size is fixed throughout.

`nb_beam_close(+Beam)`

  Close the beam Beam: no further elements can be added.

`nb_beam_add(+Beam, +Key, +Value)`

  Add Key-Value to the beam Beam. The key is sorted on Key only.

`nb_beam_del(+Beam, -Key, -Value)`

  Remove element Key-Value with smallest Value in beam Beam. Fail if the beam is empty.

`nb_beam_peek(+Beam, -Key, -Value))`

  Key-Value is the element with smallest Key in the beam Beam. Fail if the beam is empty.

`nb_beam_size(+Beam, -Size)`

  Unify Size with the number of elements in the beam Beam.

`nb_beam_empty(+Beam)`

  Succeeds if Beam is empty.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.12 Ordered Sets

The following ordered set manipulation routines are available once included with the `use_module(library(ordsets))` command. An ordered set is represented by a list having unique and ordered elements. Output arguments are guaranteed to be ordered sets, if the relevant inputs are. This is a slightly patched version of Richard O’Keefe’s original library.

`list_to_ord_set(+List, ?Set)`

  Holds when Set is the ordered representation of the set represented by the unordered representation List.

`merge(+List1, +List2, -Merged)`

  Holds when Merged is the stable merge of the two given lists.

  Notice that `merge/3` will not remove duplicates, so merging ordered sets will not necessarily result in an ordered set. Use `ord_union/3` instead.

`ord_add_element(+Set1, +Element, ?Set2)`

  Inserting Element in Set1 returns Set2. It should give exactly the same result as `merge(Set1, [Element], Set2)`, but a bit faster, and certainly more clearly. The same as `ord_insert/3`.

`ord_del_element(+Set1, +Element, ?Set2)`

  Removing Element from Set1 returns Set2.

`ord_disjoint(+Set1, +Set2)`

  Holds when the two ordered sets have no element in common.

`ord_member(+Element, +Set)`

  Holds when Element is a member of Set.

`ord_insert(+Set1, +Element, ?Set2)`

  Inserting Element in Set1 returns Set2. It should give exactly the same result as `merge(Set1, [Element], Set2)`, but a bit faster, and certainly more clearly. The same as `ord_add_element/3`.

`ord_intersect(+Set1, +Set2)`

  Holds when the two ordered sets have at least one element in common.

`ord_intersection(+Set1, +Set2, ?Intersection)`

  Holds when Intersection is the ordered representation of Set1 and Set2.

`ord_intersection(+Set1, +Set2, ?Intersection, ?Diff)`

  Holds when Intersection is the ordered representation of Set1 and Set2. Diff is the difference between Set2 and Set1.

`ord_seteq(+Set1, +Set2)`

  Holds when the two arguments represent the same set.

`ord_setproduct(+Set1, +Set2, -Set)`

  If Set1 and Set2 are ordered sets, Product will be an ordered set of x1-x2 pairs.

`ord_subset(+Set1, +Set2)`

  Holds when every element of the ordered set Set1 appears in the ordered set Set2.

`ord_subtract(+Set1, +Set2, ?Difference)`

  Holds when Difference contains all and only the elements of Set1 which are not also in Set2.

`ord_symdiff(+Set1, +Set2, ?Difference)`

  Holds when Difference is the symmetric difference of Set1 and Set2.

`ord_union(+Sets, ?Union)`

  Holds when Union is the union of the lists Sets.

`ord_union(+Set1, +Set2, ?Union)`

  Holds when Union is the union of Set1 and Set2.

`ord_union(+Set1, +Set2, ?Union, ?Diff)`

  Holds when Union is the union of Set1 and Set2 and Diff is the difference.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.13 Pseudo Random Number Integer Generator

The following routines produce random non-negative integers in the range 0 .. 2^(w-1) -1, where w is the word size available for integers, e.g. 32 for Intel machines and 64 for Alpha machines. Note that the numbers generated by this random number generator are repeatable. This generator was originally written by Allen Van Gelder and is based on Knuth Vol 2.

`rannum(-I)`

  Produces a random non-negative integer I whose low bits are not all that random, so it should be scaled to a smaller range in general. The integer I is in the range 0 .. 2^(w-1) - 1. You can use:

      rannum(X) :- yap_flag(max_integer,MI), rannum(R), X is R/MI.

  to obtain a floating point number uniformly distributed between 0 and 1.

`ranstart`

  Initialize the random number generator using a built-in seed. The `ranstart/0` built-in is always called by the system when loading the package.

`ranstart(+Seed)`

  Initialize the random number generator with user-defined Seed. The same Seed always produces the same sequence of numbers.

`ranunif(+Range,-I)`

  `ranunif/2` produces a uniformly distributed non-negative random integer I over a caller-specified range R. If range is R, the result is in 0 .. R-1.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.14 Queues

The following queue manipulation routines are available once included with the `use_module(library(queues))` command. Queues are implemented with difference lists.

`make_queue(+Queue)`

  Creates a new empty queue. It should only be used to create a new queue.

`join_queue(+Element, +OldQueue, -NewQueue)`

  Adds the new element at the end of the queue.

`list_join_queue(+List, +OldQueue, -NewQueue)`

  Ads the new elements at the end of the queue.

`jump_queue(+Element, +OldQueue, -NewQueue)`

  Adds the new element at the front of the list.

`list_jump_queue(+List, +OldQueue, +NewQueue)`

  Adds all the elements of List at the front of the queue.

`head_queue(+Queue, ?Head)`

  Unifies Head with the first element of the queue.

`serve_queue(+OldQueue, +Head, -NewQueue)`

  Removes the first element of the queue for service.

`empty_queue(+Queue)`

  Tests whether the queue is empty.

`length_queue(+Queue, -Length)`

  Counts the number of elements currently in the queue.

`list_to_queue(+List, -Queue)`

  Creates a new queue with the same elements as List.

`queue_to_list(+Queue, -List)`

  Creates a new list with the same elements as Queue.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.15 Random Number Generator

The following random number operations are included with the `use_module(library(random))` command. Since YAP-4.3.19 YAP uses the O’Keefe public-domain algorithm, based on the "Applied Statistics" algorithm AS183.

`getrand(-Key)`

  Unify Key with a term of the form `rand(X,Y,Z)` describing the current state of the random number generator.

`random(-Number)`

  Unify Number with a floating-point number in the range `[0...1)`.

`random(+LOW, +HIGH, -NUMBER)`

  Unify Number with a number in the range `[LOW...HIGH)`. If both LOW and HIGH are integers then NUMBER will also be an integer, otherwise NUMBER will be a floating-point number.

`randseq(+LENGTH, +MAX, -Numbers)`

  Unify Numbers with a list of LENGTH unique random integers in the range `[1�...MAX)`.

`randset(+LENGTH, +MAX, -Numbers)`

  Unify Numbers with an ordered list of LENGTH unique random integers in the range `[1�...MAX)`.

`setrand(+Key)`

  Use a term of the form `rand(X,Y,Z)` to set a new state for the random number generator. The integer `X` must be in the range `[1...30269)`, the integer `Y` must be in the range `[1...30307)`, and the integer `Z` must be in the range `[1...30323)`.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.16 Read Utilities

The `readutil` library contains primitives to read lines, files, multiple terms, etc.

`read_line_to_codes(+Stream, -Codes)`

  Read the next line of input from Stream and unify the result with Codes after the line has been read. A line is ended by a newline character or end-of-file. Unlike `read_line_to_codes/3`, this predicate removes trailing newline character.

  On end-of-file the atom `end_of_file` is returned. See also `at_end_of_stream/[0,1]`.

`read_line_to_codes(+Stream, -Codes, ?Tail)`

  Difference-list version to read an input line to a list of character codes. Reading stops at the newline or end-of-file character, but unlike `read_line_to_codes/2`, the newline is retained in the output. This predicate is especially useful for reading a block of lines upto some delimiter. The following example reads an HTTP header ended by a blank line:

      read_header_data(Stream, Header) :-
      	read_line_to_codes(Stream, Header, Tail),
      	read_header_data(Header, Stream, Tail).

      read_header_data("\r\n", _, _) :- !.
      read_header_data("\n", _, _) :- !.
      read_header_data("", _, _) :- !.
      read_header_data(_, Stream, Tail) :-
      	read_line_to_codes(Stream, Tail, NewTail),
      	read_header_data(Tail, Stream, NewTail).

`read_stream_to_codes(+Stream, -Codes)`

  Read all input until end-of-file and unify the result to Codes.

`read_stream_to_codes(+Stream, -Codes, ?Tail)`

  Difference-list version of `read_stream_to_codes/2`.

`read_file_to_codes(+Spec, -Codes, +Options)`

  Read a file to a list of character codes. Currently ignores Options.

`read_file_to_terms(+Spec, -Terms, +Options)`

  Read a file to a list of Prolog terms (see read/1).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.17 Red-Black Trees

Red-Black trees are balanced search binary trees. They are named because nodes can be classified as either red or black. The code we include is based on "Introduction to Algorithms", second edition, by Cormen, Leiserson, Rivest and Stein. The library includes routines to insert, lookup and delete elements in the tree.

`rb_new(?T)`

  Create a new tree.

`rb_empty(?T)`

  Succeeds if tree T is empty.

`is_rbtree(+T)`

  Check whether T is a valid red-black tree.

`rb_insert(+T0,+Key,?Value,+TF)`

  Add an element with key Key and Value to the tree T0 creating a new red-black tree TF. Duplicated elements are not allowed.

  Add a new element with key Key and Value to the tree T0 creating a new red-black tree TF. Fails is an element with Key exists in the tree.

`rb_lookup(+Key,-Value,+T)`

  Backtrack through all elements with key Key in the red-black tree T, returning for each the value Value.

`rb_lookupall(+Key,-Value,+T)`

  Lookup all elements with key Key in the red-black tree T, returning the value Value.

`rb_delete(+T,+Key,-TN)`

  Delete element with key Key from the tree T, returning a new tree TN.

`rb_delete(+T,+Key,-Val,-TN)`

  Delete element with key Key from the tree T, returning the value Val associated with the key and a new tree TN.

`rb_del_min(+T,-Key,-Val,-TN)`

  Delete the least element from the tree T, returning the key Key, the value Val associated with the key and a new tree TN.

`rb_del_max(+T,-Key,-Val,-TN)`

  Delete the largest element from the tree T, returning the key Key, the value Val associated with the key and a new tree TN.

`rb_update(+T,+Key,+NewVal,-TN)`

  Tree TN is tree T, but with value for Key associated with NewVal. Fails if it cannot find Key in T.

`rb_apply(+T,+Key,+G,-TN)`

  If the value associated with key Key is Val0 in T, and if `call(G,Val0,ValF)` holds, then TN differs from T only in that Key is associated with value ValF in tree TN. Fails if it cannot find Key in T, or if `call(G,Val0,ValF)` is not satisfiable.

`rb_visit(+T,-Pairs)`

  Pairs is an infix visit of tree T, where each element of Pairs is of the form K-Val.

`rb_size(+T,-Size)`

  Size is the number of elements in T.

`rb_keys(+T,+Keys)`

  Keys is an infix visit with all keys in tree T. Keys will be sorted, but may be duplicate.

`rb_map(+T,+G,-TN)`

  For all nodes Key in the tree T, if the value associated with key Key is Val0 in tree T, and if `call(G,Val0,ValF)` holds, then the value associated with Key in TN is ValF. Fails if or if `call(G,Val0,ValF)` is not satisfiable for all Var0.

`rb_partial_map(+T,+Keys,+G,-TN)`

  For all nodes Key in Keys, if the value associated with key Key is Val0 in tree T, and if `call(G,Val0,ValF)` holds, then the value associated with Key in TN is ValF. Fails if or if `call(G,Val0,ValF)` is not satisfiable for all Var0. Assumes keys are not repeated.

`rb_clone(+T,+NT,+Nodes)`

  “Clone” the red-back tree into a new tree with the same keys as the original but with all values set to unbound values. Nodes is a list containing all new nodes as pairs K-V.

`rb_min(+T,-Key,-Value)`

  Key is the minimum key in T, and is associated with Val.

`rb_max(+T,-Key,-Value)`

  Key is the maximal key in T, and is associated with Val.

`rb_next(+T, +Key,-Next,-Value)`

  Next is the next element after Key in T, and is associated with Val.

`rb_previous(+T, +Key,-Previous,-Value)`

  Previous is the previous element after Key in T, and is associated with Val.

`list_to_rbtree(+L, -T)`

  T is the red-black tree corresponding to the mapping in list L.

`ord_list_to_rbtree(+L, -T)`

  T is the red-black tree corresponding to the mapping in ordered list L.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.18 Regular Expressions

This library includes routines to determine whether a regular expression matches part or all of a string. The routines can also return which parts parts of the string matched the expression or subexpressions of it. This library relies on Henry Spencer’s `C`-package and is only available in operating systems that support dynamic loading. The `C`-code has been obtained from the sources of FreeBSD-4.0 and is protected by copyright from Henry Spencer and from the Regents of the University of California (see the file library/regex/COPYRIGHT for further details).

Much of the description of regular expressions below is copied verbatim from Henry Spencer’s manual page.

A regular expression is zero or more branches, separated by “|”. It matches anything that matches one of the branches.

A branch is zero or more pieces, concatenated. It matches a match for the first, followed by a match for the second, etc.

A piece is an atom possibly followed by “*”, “+”, or “?”. An atom followed by “*” matches a sequence of 0 or more matches of the atom. An atom followed by “+” matches a sequence of 1 or more matches of the atom. An atom followed by “?” matches a match of the atom, or the null string.

An atom is a regular expression in parentheses (matching a match for the regular expression), a range (see below), “.” (matching any single character), “^” (matching the null string at the beginning of the input string), “$” (matching the null string at the end of the input string), a “\” followed by a single character (matching that character), or a single character with no other significance (matching that character).

A range is a sequence of characters enclosed in “[]”. It normally matches any single character from the sequence. If the sequence begins with “^”, it matches any single character not from the rest of the sequence. If two characters in the sequence are separated by “-”, this is shorthand for the full list of ASCII characters between them (e.g. “[0-9]” matches any decimal digit). To include a literal “]” in the sequence, make it the first character (following a possible “^”). To include a literal “-”, make it the first or last character.

`regexp(+RegExp,+String,+Opts)`

  Match regular expression RegExp to input string String according to options Opts. The options may be:

  - `nocase`: Causes upper-case characters in String to be treated as lower case during the matching process.
`regexp(+RegExp,+String,+Opts,?SubMatchVars)`

  Match regular expression RegExp to input string String according to options Opts. The variable SubMatchVars should be originally unbound or a list of unbound variables all will contain a sequence of matches, that is, the head of SubMatchVars will contain the characters in String that matched the leftmost parenthesized subexpression within RegExp, the next head of list will contain the characters that matched the next parenthesized subexpression to the right in RegExp, and so on.

  The options may be:

  - `nocase`: Causes upper-case characters in String to be treated as lower case during the matching process.
  - `indices`: Changes what is stored in SubMatchVars. Instead of storing the matching characters from String, each variable will contain a term of the form IO-IF giving the indices in String of the first and last characters in the matching range of characters.

  In general there may be more than one way to match a regular expression to an input string. For example, consider the command

        regexp("(a*)b*","aabaaabb", [], [X,Y])

  Considering only the rules given so far, X and Y could end up with the values `"aabb"` and `"aa"`, `"aaab"` and `"aaa"`, `"ab"` and `"a"`, or any of several other combinations. To resolve this potential ambiguity `regexp` chooses among alternatives using the rule “first then longest”. In other words, it considers the possible matches in order working from left to right across the input string and the pattern, and it attempts to match longer pieces of the input string before shorter ones. More specifically, the following rules apply in decreasing order of priority:

  1. If a regular expression could match two different parts of an input string then it will match the one that begins earliest.
  2. If a regular expression contains "|" operators then the leftmost matching sub-expression is chosen.
  3. In *, +, and ? constructs, longer matches are chosen in preference to shorter ones.
  4. In sequences of expression components the components are considered from left to right.

  In the example from above, `"(a*)b*"` matches `"aab"`: the `"(a*)"` portion of the pattern is matched first and it consumes the leading `"aa"`; then the `"b*"` portion of the pattern consumes the next `"b"`. Or, consider the following example:

        regexp("(ab|a)(b*)c",  "abc", [], [X,Y,Z])

  After this command X will be `"abc"`, Y will be `"ab"`, and Z will be an empty string. Rule 4 specifies that `"(ab|a)"` gets first shot at the input string and Rule 2 specifies that the `"ab"` sub-expression is checked before the `"a"` sub-expression. Thus the `"b"` has already been claimed before the `"(b*)"` component is checked and `(b*)` must match an empty string.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.19 SWI-Prolog’s shlib library

This section discusses the functionality of the (autoload) `library(shlib)`, providing an interface to manage shared libraries.

One of the files provides a global function `install_mylib()` that initialises the module using calls to `PL_register_foreign()`. Here is a simple example file `mylib.c`, which creates a Windows MessageBox:

    #include <windows.h>
    #include <SWI-Prolog.h>

    static foreign_t
    pl_say_hello(term_t to)
    { char *a;

      if ( PL_get_atom_chars(to, &a) )
      { MessageBox(NULL, a, "DLL test", MB_OK|MB_TASKMODAL);

        PL_succeed;
      }

      PL_fail;
    }

    install_t
    install_mylib()
    { PL_register_foreign("say_hello", 1, pl_say_hello, 0);
    }

Now write a file mylib.pl:

    :- module(mylib, [ say_hello/1 ]).
    :- use_foreign_library(foreign(mylib)).

The file mylib.pl can be loaded as a normal Prolog file and provides the predicate defined in C.

`[det]load_foreign_library(:FileSpec)`
`[det]load_foreign_library(:FileSpec, +Entry:atom)`

  Load a shared object or DLL. After loading the Entry function is called without arguments. The default entry function is composed from `install_`, followed by the file base-name. E.g., the load-call below calls the function `install_mylib()`. If the platform prefixes extern functions with `_`, this prefix is added before calling.

                ...
                load_foreign_library(foreign(mylib)),
                ...

  FileSpec is a specification for `absolute_file_name/3`. If searching the file fails, the plain name is passed to the OS to try the default method of the OS for locating foreign objects. The default definition of `file_search_path/2` searches <prolog home>/lib/Yap.

  See also `use_foreign_library/1,2` are intended for use in directives.

`[det]use_foreign_library(+FileSpec)`
`[det]use_foreign_library(+FileSpec, +Entry:atom)`

  Load and install a foreign library as load_foreign_library/1,2 and register the installation using `initialization/2` with the option now. This is similar to using:

          :- initialization(load_foreign_library(foreign(mylib))).

  but using the `initialization/1` wrapper causes the library to be loaded after loading of the file in which it appears is completed, while `use_foreign_library/1` loads the library immediately. I.e. the difference is only relevant if the remainder of the file uses functionality of the `C`-library.

`[det]unload_foreign_library(+FileSpec)`
`[det]unload_foreign_library(+FileSpec, +Exit:atom)`

  Unload a shared object or DLL. After calling the Exit function, the shared object is removed from the process. The default exit function is composed from `uninstall_`, followed by the file base-name.

`current_foreign_library(?File, ?Public)`

  Query currently loaded shared libraries.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.20 Splay Trees

Splay trees are explained in the paper "Self-adjusting Binary Search Trees", by D.D. Sleator and R.E. Tarjan, JACM, vol. 32, No.3, July 1985, p. 668. They are designed to support fast insertions, deletions and removals in binary search trees without the complexity of traditional balanced trees. The key idea is to allow the tree to become unbalanced. To make up for this, whenever we find a node, we move it up to the top. We use code by Vijay Saraswat originally posted to the Prolog mailing-list.

`splay_access(-Return,+Key,?Val,+Tree,-NewTree)`

  If item Key is in tree Tree, return its Val and unify Return with `true`. Otherwise unify Return with `null`. The variable NewTree unifies with the new tree.

`splay_delete(+Key,?Val,+Tree,-NewTree)`

  Delete item Key from tree Tree, assuming that it is present already. The variable Val unifies with a value for key Key, and the variable NewTree unifies with the new tree. The predicate will fail if Key is not present.

`splay_init(-NewTree)`

  Initialize a new splay tree.

`splay_insert(+Key,?Val,+Tree,-NewTree)`

  Insert item Key in tree Tree, assuming that it is not there already. The variable Val unifies with a value for key Key, and the variable NewTree unifies with the new tree. In our implementation, Key is not inserted if it is already there: rather it is unified with the item already in the tree.

`splay_join(+LeftTree,+RighTree,-NewTree)`

  Combine trees LeftTree and RighTree into a single treeNewTree containing all items from both trees. This operation assumes that all items in LeftTree are less than all those in RighTree and destroys both LeftTree and RighTree.

`splay_split(+Key,?Val,+Tree,-LeftTree,-RightTree)`

  Construct and return two trees LeftTree and RightTree, where LeftTree contains all items in Tree less than Key, and RightTree contains all items in Tree greater than Key. This operations destroys Tree.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.21 Reading From and Writing To Strings

From Version 4.3.2 onwards YAP implements SICStus Prolog compatible String I/O. The library allows users to read from and write to a memory buffer as if it was a file. The memory buffer is built from or converted to a string of character codes by the routines in library. Therefore, if one wants to read from a string the string must be fully instantiated before the library built-in opens the string for reading. These commands are available through the `use_module(library(charsio))` command.

`format_to_chars(+Form, +Args, -Result)`

  Execute the built-in procedure `format/2` with form Form and arguments Args outputting the result to the string of character codes Result.

`format_to_chars(+Form, +Args, -Result, -Result0)`

  Execute the built-in procedure `format/2` with form Form and arguments Args outputting the result to the difference list of character codes Result-Result0.

`write_to_chars(+Term, -Result)`

  Execute the built-in procedure `write/1` with argument Term outputting the result to the string of character codes Result.

`write_to_chars(+Term, -Result0, -Result)`

  Execute the built-in procedure `write/1` with argument Term outputting the result to the difference list of character codes Result-Result0.

`atom_to_chars(+Atom, -Result)`

  Convert the atom Atom to the string of character codes Result.

`atom_to_chars(+Atom, -Result0, -Result)`

  Convert the atom Atom to the difference list of character codes Result-Result0.

`number_to_chars(+Number, -Result)`

  Convert the number Number to the string of character codes Result.

`number_to_chars(+Number, -Result0, -Result)`

  Convert the atom Number to the difference list of character codes Result-Result0.

`atom_to_term(+Atom, -Term, -Bindings)`

  Use Atom as input to `read_term/2` using the option `variable_names` and return the read term in Term and the variable bindings in Bindings. Bindings is a list of `Name = Var` couples, thus providing access to the actual variable names. See also `read_term/2`. If Atom has no valid syntax, a syntax_error exception is raised.

`term_to_atom(?Term, ?Atom)`

  True if Atom describes a term that unifies with Term. When Atom is instantiated Atom is converted and then unified with Term. If Atom has no valid syntax, a syntax_error exception is raised. Otherwise Term is “written” on Atom using `write_term/2` with the option quoted(true).

`read_from_chars(+Chars, -Term)`

  Parse the list of character codes Chars and return the result in the term Term. The character codes to be read must terminate with a dot character such that either (i) the dot character is followed by blank characters; or (ii) the dot character is the last character in the string.

`open_chars_stream(+Chars, -Stream)`

  Open the list of character codes Chars as a stream Stream.

`with_output_to_chars(?Goal, -Chars)`

  Execute goal Goal such that its standard output will be sent to a memory buffer. After successful execution the contents of the memory buffer will be converted to the list of character codes Chars.

`with_output_to_chars(?Goal, ?Chars0, -Chars)`

  Execute goal Goal such that its standard output will be sent to a memory buffer. After successful execution the contents of the memory buffer will be converted to the difference list of character codes Chars-Chars0.

`with_output_to_chars(?Goal, -Stream, ?Chars0, -Chars)`

  Execute goal Goal such that its standard output will be sent to a memory buffer. After successful execution the contents of the memory buffer will be converted to the difference list of character codes Chars-Chars0 and Stream receives the stream corresponding to the memory buffer.

The implementation of the character IO operations relies on three YAP built-ins:

`charsio:open_mem_read_stream(+String, -Stream)`

  Store a string in a memory buffer and output a stream that reads from this memory buffer.

`charsio:open_mem_write_stream(-Stream)`

  Create a new memory buffer and output a stream that writes to it.

`charsio:peek_mem_write_stream(-Stream, L0, L)`

  Convert the memory buffer associated with stream Stream to the difference list of character codes L-L0.

These built-ins are initialized to belong to the module `charsio` in `init.yap`. Novel procedures for manipulating strings by explicitly importing these built-ins.

YAP does not currently support opening a `charsio` stream in `append` mode, or seeking in such a stream.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.22 Calling The Operating System from YAP

YAP now provides a library of system utilities compatible with the SICStus Prolog system library. This library extends and to some point replaces the functionality of Operating System access routines. The library includes Unix/Linux and Win32 `C` code. They are available through the `use_module(library(system))` command.

`datime(datime(-Year, -Month, -DayOfTheMonth,`

  -Hour, -Minute, -Second) The `datime/1` procedure returns the current date and time, with information on Year, Month, DayOfTheMonth, Hour, Minute, and Second. The Hour is returned on local time. This function uses the WIN32 `GetLocalTime` function or the Unix `localtime` function.

         ?- datime(X).

      X = datime(2001,5,28,15,29,46) ?

`mktime(datime(+Year, +Month, +DayOfTheMonth,`

  +Hour, +Minute, +Second), -Seconds) The `mktime/1` procedure returns the number of Seconds elapsed since 00:00:00 on January 1, 1970, Coordinated Universal Time (UTC). The user provides information on Year, Month, DayOfTheMonth, Hour, Minute, and Second. The Hour is given on local time. This function uses the WIN32 `GetLocalTime` function or the Unix `mktime` function.

         ?- mktime(datime(2001,5,28,15,29,46),X).

      X = 991081786 ? ;

`delete_file(+File)`

  The `delete_file/1` procedure removes file File. If File is a directory, remove the directory and all its subdirectories.

         ?- delete_file(x).

`delete_file(+File,+Opts)`

  The `delete_file/2` procedure removes file File according to options Opts. These options are `directory` if one should remove directories, `recursive` if one should remove directories recursively, and `ignore` if errors are not to be reported.

  This example is equivalent to using the `delete_file/1` predicate:

         ?- delete_file(x, [recursive]).

`directory_files(+Dir,+List)`

  Given a directory Dir, `directory_files/2` procedures a listing of all files and directories in the directory:

          ?- directory_files('.',L), writeq(L).
      ['Makefile.~1~','sys.so','Makefile','sys.o',x,..,'.']

  The predicates uses the `dirent` family of routines in Unix environments, and `findfirst` in WIN32.

`file_exists(+File)`

  The atom File corresponds to an existing file.

`file_exists(+File,+Permissions)`

  The atom File corresponds to an existing file with permissions compatible with Permissions. YAP currently only accepts for permissions to be described as a number. The actual meaning of this number is Operating System dependent.

`file_property(+File,?Property)`

  The atom File corresponds to an existing file, and Property will be unified with a property of this file. The properties are of the form `type(Type)`, which gives whether the file is a regular file, a directory, a fifo file, or of unknown type; `size(Size)`, with gives the size for a file, and `mod_time(Time)`, which gives the last time a file was modified according to some Operating System dependent timestamp; `mode(mode)`, gives the permission flags for the file, and `linkto(FileName)`, gives the file pointed to by a symbolic link. Properties can be obtained through backtracking:

         ?- file_property('Makefile',P).

      P = type(regular) ? ;

      P = size(2375) ? ;

      P = mod_time(990826911) ? ;

      no

`make_directory(+Dir)`

  Create a directory Dir. The name of the directory must be an atom.

`rename_file(+OldFile,+NewFile)`

  Create file OldFile to NewFile. This predicate uses the `C` built-in function `rename`.

`environ(?EnvVar,+EnvValue)`

  Unify environment variable EnvVar with its value EnvValue, if there is one. This predicate is backtrackable in Unix systems, but not currently in Win32 configurations.

         ?- environ('HOME',X).

      X = 'C:\\cygwin\\home\\administrator' ?

`host_id(-Id)`

  Unify Id with an identifier of the current host. YAP uses the `hostid` function when available,

`host_name(-Name)`

  Unify Name with a name for the current host. YAP uses the `hostname` function in Unix systems when available, and the `GetComputerName` function in WIN32 systems.

`kill(Id,+SIGNAL)`

  Send signal SIGNAL to process Id. In Unix this predicate is a direct interface to `kill` so one can send signals to groups of processes. In WIN32 the predicate is an interface to `TerminateProcess`, so it kills Id independently of SIGNAL.

`mktemp(Spec,-File)`

  Direct interface to `mktemp`: given a Spec, that is a file name with six X to it, create a file name File. Use `tmpnam/1` instead.

`pid(-Id)`

  Unify Id with the process identifier for the current process. An interface to the `getpid` function.

`tmpnam(-File)`

  Interface with tmpnam: obtain a new, unique file name File.

`tmp_file(-File)`

  Create a name for a temporary file. Base is an user provided identifier for the category of file. The TmpName is guaranteed to be unique. If the system halts, it will automatically remove all created temporary files.

`exec(+Command,[+InputStream,+OutputStream,+ErrorStream],-PID)`

  Execute command Command with its streams connected to InputStream, OutputStream, and ErrorStream. The process that executes the command is returned as PID. The command is executed by the default shell `bin/sh -c` in Unix.

  The following example demonstrates the use of `exec/3` to send a command and process its output:

      exec(ls,[std,pipe(S),null],P),repeat, get0(S,C), (C = -1, close(S) ! ; put(C)).

  The streams may be one of standard stream, `std`, null stream, `null`, or `pipe(S)`, where S is a pipe stream. Note that it is up to the user to close the pipe.

`working_directory(-CurDir,?NextDir)`

  Fetch the current directory at CurDir. If NextDir is bound to an atom, make its value the current working directory.

`popen(+Command, +TYPE, -Stream)`

  Interface to the `popen` function. It opens a process by creating a pipe, forking and invoking Command on the current shell. Since a pipe is by definition unidirectional the Type argument may be `read` or `write`, not both. The stream should be closed using `close/1`, there is no need for a special `pclose` command.

  The following example demonstrates the use of `popen/3` to process the output of a command, as `exec/3` would do:

         ?- popen(ls,read,X),repeat, get0(X,C), (C = -1, ! ; put(C)).

      X = 'C:\\cygwin\\home\\administrator' ?

  The WIN32 implementation of `popen/3` relies on `exec/3`.

`shell`

  Start a new shell and leave YAP in background until the shell completes. YAP uses the shell given by the environment variable `SHELL`. In WIN32 environment YAP will use `COMSPEC` if `SHELL` is undefined.

`shell(+Command)`

  Execute command Command under a new shell. YAP will be in background until the command completes. In Unix environments YAP uses the shell given by the environment variable `SHELL` with the option `" -c "`. In WIN32 environment YAP will use `COMSPEC` if `SHELL` is undefined, in this case with the option `" /c "`.

`shell(+Command,-Status)`

  Execute command Command under a new shell and unify Status with the exit for the command. YAP will be in background until the command completes. In Unix environments YAP uses the shell given by the environment variable `SHELL` with the option `" -c "`. In WIN32 environment YAP will use `COMSPEC` if `SHELL` is undefined, in this case with the option `" /c "`.

`sleep(+Time)`

  Block the current thread for Time seconds. When YAP is compiled without multi-threading support, this predicate blocks the YAP process. The number of seconds must be a positive number, and it may an integer or a float. The Unix implementation uses `usleep` if the number of seconds is below one, and `sleep` if it is over a second. The WIN32 implementation uses `Sleep` for both cases.

`system`

  Start a new default shell and leave YAP in background until the shell completes. YAP uses `/bin/sh` in Unix systems and `COMSPEC` in WIN32.

`system(+Command,-Res)`

  Interface to `system`: execute command Command and unify Res with the result.

`wait(+PID,-Status)`

  Wait until process PID terminates, and return its exits Status.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.23 Utilities On Terms

The next routines provide a set of commonly used utilities to manipulate terms. Most of these utilities have been implemented in `C` for efficiency. They are available through the `use_module(library(terms))` command.

`cyclic_term(?Term)`

  Succeed if the argument Term is a cyclic term.

`term_hash(+Term, ?Hash)`

  If Term is ground unify Hash with a positive integer calculated from the structure of the term. Otherwise the argument Hash is left unbound. The range of the positive integer is from `0` to, but not including, `33554432`.

`term_hash(+Term, +Depth, +Range, ?Hash)`

  Unify Hash with a positive integer calculated from the structure of the term. The range of the positive integer is from `0` to, but not including, Range. If Depth is `-1` the whole term is considered. Otherwise, the term is considered only up to depth `1`, where the constants and the principal functor have depth `1`, and an argument of a term with depth I has depth I+1.

`variables_within_term(+Variables,?Term, -OutputVariables)`

  Unify OutputVariables with the subset of the variables Variables that occurs in Term.

`new_variables_in_term(+Variables,?Term, -OutputVariables)`

  Unify OutputVariables with all variables occurring in Term that are not in the list Variables.

`variant(?Term1, ?Term2)`

  Succeed if Term1 and Term2 are variant terms.

`subsumes(?Term1, ?Term2)`

  Succeed if Term1 subsumes Term2. Variables in term Term1 are bound so that the two terms become equal.

`subsumes_chk(?Term1, ?Term2)`

  Succeed if Term1 subsumes Term2 but does not bind any variable in Term1.

`variable_in_term(?Term,?Var)`

  Succeed if the second argument Var is a variable and occurs in term Term.

`unifiable(?Term1, ?Term2, -Bindings)`

  Succeed if Term1 and Term2 are unifiable with substitution Bindings.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.24 Trie DataStructure

The next routines provide a set of utilities to create and manipulate prefix trees of Prolog terms. Tries were originally proposed to implement tabling in Logic Programming, but can be used for other purposes. The tries will be stored in the Prolog database and can seen as alternative to `assert` and `record` family of primitives. Most of these utilities have been implemented in `C` for efficiency. They are available through the `use_module(library(tries))` command.

`trie_open(-Id)`

  Open a new trie with identifier Id.

`trie_close(+Id)`

  Close trie with identifier Id.

`trie_close_all`

  Close all available tries.

`trie_mode(?Mode)`

  Unify Mode with trie operation mode. Allowed values are either `std` (default) or `rev`.

`trie_put_entry(+Trie,+Term,-Ref)`

  Add term Term to trie Trie. The handle Ref gives a reference to the term.

`trie_check_entry(+Trie,+Term,-Ref)`

  Succeeds if a variant of term Term is in trie Trie. An handle Ref gives a reference to the term.

`trie_get_entry(+Ref,-Term)`

  Unify Term with the entry for handle Ref.

`trie_remove_entry(+Ref)`

  Remove entry for handle Ref.

`trie_remove_subtree(+Ref)`

  Remove subtree rooted at handle Ref.

`trie_save(+Trie,+FileName)`

  Dump trie Trie into file FileName.

`trie_load(+Trie,+FileName)`

  Load trie Trie from the contents of file FileName.

`trie_stats(-Memory,-Tries,-Entries,-Nodes)`

  Give generic statistics on tries, including the amount of memory, Memory, the number of tries, Tries, the number of entries, Entries, and the total number of nodes, Nodes.

`trie_max_stats(-Memory,-Tries,-Entries,-Nodes)`

  Give maximal statistics on tries, including the amount of memory, Memory, the number of tries, Tries, the number of entries, Entries, and the total number of nodes, Nodes.

`trie_usage(+Trie,-Entries,-Nodes,-VirtualNodes)`

  Give statistics on trie Trie, the number of entries, Entries, and the total number of nodes, Nodes, and the number of VirtualNodes.

`trie_print(+Trie)`

  Print trie Trie on standard output.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.25 Call Cleanup

`call_cleanup/1` and `call_cleanup/2` allow predicates to register code for execution after the call is finished. Predicates can be declared to be `fragile` to ensure that `call_cleanup` is called for any Goal which needs it. This library is loaded with the `use_module(library(cleanup))` command.

`:- fragile P,....,Pn`

  Declares the predicate P=`[module:]name/arity` as a fragile predicate, module is optional, default is the current typein_module. Whenever such a fragile predicate is used in a query it will be called through call_cleanup/1.

      :- fragile foo/1,bar:baz/2.

`call_cleanup(:Goal)`

  Execute goal Goal within a cleanup-context. Called predicates might register cleanup Goals which are called right after the end of the call to Goal. Cuts and exceptions inside Goal do not prevent the execution of the cleanup calls. `call_cleanup` might be nested.

`call_cleanup(:Goal, :CleanUpGoal)`

  This is similar to `call_cleanup/1` with an additional CleanUpGoal which gets called after Goal is finished.

`setup_call_cleanup(:Setup,:Goal, :CleanUpGoal)`

  Calls `(Setup, Goal)`. For each sucessful execution of Setup, calling Goal, the cleanup handler Cleanup is guaranteed to be called exactly once. This will happen after Goal completes, either through failure, deterministic success, commit, or an exception. Setup will contain the goals that need to be protected from asynchronous interrupts such as the ones received from `call_with_time_limit/2` or `thread_signal/2`. In most uses, Setup will perform temporary side-effects required by Goal that are finally undone by Cleanup.

  Success or failure of Cleanup is ignored and choice-points it created are destroyed (as `once/1`). If Cleanup throws an exception, this is executed as normal.

  Typically, this predicate is used to cleanup permanent data storage required to execute Goal, close file-descriptors, etc. The example below provides a non-deterministic search for a term in a file, closing the stream as needed.

      term_in_file(Term, File) :-
      	setup_call_cleanup(open(File, read, In),
      			   term_in_stream(Term, In),
      			   close(In) ).

      term_in_stream(Term, In) :-
      	repeat,
      	read(In, T),
      	(   T == end_of_file
      	->  !, fail
      	;   T = Term
      	).

  Note that it is impossible to implement this predicate in Prolog other than by reading all terms into a list, close the file and call `member/2`. Without `setup_call_cleanup/3` there is no way to gain control if the choice-point left by `repeat` is removed by a cut or an exception.

  `setup_call_cleanup/2` can also be used to test determinism of a goal:

      ?- setup_call_cleanup(true,(X=1;X=2), Det=yes).

      X = 1 ;

      X = 2,
      Det = yes ;

  This predicate is under consideration for inclusion into the ISO standard. For compatibility with other Prolog implementations see `call_cleanup/2`.

`setup_call_catcher_cleanup(:Setup,:Goal, +Catcher,:CleanUpGoal)`

  Similar to `setup_call_cleanup(Setup, Goal, Cleanup)` with additional information on the reason of calling Cleanup. Prior to calling Cleanup, Catcher unifies with the termination code. If this unification fails, Cleanup is not called.

`on_cleanup(+CleanUpGoal)`

  Any Predicate might registers a CleanUpGoal. The CleanUpGoal is put onto the current cleanup context. All such CleanUpGoals are executed in reverse order of their registration when the surrounding cleanup-context ends. This call will throw an exception if a predicate tries to register a CleanUpGoal outside of any cleanup-context.

`cleanup_all`

  Calls all pending CleanUpGoals and resets the cleanup-system to an initial state. Should only be used as one of the last calls in the main program.

There are some private predicates which could be used in special cases, such as manually setting up cleanup-contexts and registering CleanUpGoals for other than the current cleanup-context. Read the Source Luke.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.26 Calls With Timeout

The `time_out/3` command relies on the `alarm/3` built-in to implement a call with a maximum time of execution. The command is available with the `use_module(library(timeout))` command.

`time_out(+Goal, +Timeout, -Result)`

  Execute goal Goal with time limited Timeout, where Timeout is measured in milliseconds. If the goal succeeds, unify Result with success. If the timer expires before the goal terminates, unify Result with `time_out`.

  This command is implemented by activating an alarm at procedure entry. If the timer expires before the goal completes, the alarm will throw an exception timeout.

  One should note that `time_out/3` is not reentrant, that is, a goal called from `time_out` should never itself call `time_out/3`. Moreover, `time_out/3` will deactivate any previous alarms set by `alarm/3` and vice-versa, hence only one of these calls should be used in a program.

  Last, even though the timer is set in milliseconds, the current implementation relies on `alarm/3`, and therefore can only offer precision on the scale of seconds.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.27 Updatable Binary Trees

The following queue manipulation routines are available once included with the `use_module(library(trees))` command.

`get_label(+Index, +Tree, ?Label)`

  Treats the tree as an array of N elements and returns the Index-th.

`list_to_tree(+List, -Tree)`

  Takes a given List of N elements and constructs a binary Tree.

`map_tree(+Pred, +OldTree, -NewTree)`

  Holds when OldTree and NewTree are binary trees of the same shape and `Pred(Old,New)` is true for corresponding elements of the two trees.

`put_label(+Index, +OldTree, +Label, -NewTree)`

  constructs a new tree the same shape as the old which moreover has the same elements except that the Index-th one is Label.

`tree_size(+Tree, -Size)`

  Calculates the number of elements in the Tree.

`tree_to_list(+Tree, -List)`

  Is the converse operation to list_to_tree.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.28 Unweighted Graphs

The following graph manipulation routines are based in code originally written by Richard O’Keefe. The code was then extended to be compatible with the SICStus Prolog ugraphs library. The routines assume directed graphs, undirected graphs may be implemented by using two edges. Graphs are represented in one of two ways:

- The P-representation of a graph is a list of (from-to) vertex pairs, where the pairs can be in any old order. This form is convenient for input/output.
- The S-representation of a graph is a list of (vertex-neighbors) pairs, where the pairs are in standard order (as produced by keysort) and the neighbors of each vertex are also in standard order (as produced by sort). This form is convenient for many calculations.

These built-ins are available once included with the `use_module(library(ugraphs))` command.

`vertices_edges_to_ugraph(+Vertices, +Edges, -Graph)`

  Given a graph with a set of vertices Vertices and a set of edges Edges, Graph must unify with the corresponding s-representation. Note that the vertices without edges will appear in Vertices but not in Edges. Moreover, it is sufficient for a vertex to appear in Edges.

      ?- vertices_edges_to_ugraph([],[1-3,2-4,4-5,1-5],L).

      L = [1-[3,5],2-[4],3-[],4-[5],5-[]] ?

  In this case all edges are defined implicitly. The next example shows three unconnected edges:

      ?- vertices_edges_to_ugraph([6,7,8],[1-3,2-4,4-5,1-5],L).

      L = [1-[3,5],2-[4],3-[],4-[5],5-[],6-[],7-[],8-[]] ?

`vertices(+Graph, -Vertices)`

  Unify Vertices with all vertices appearing in graph Graph. In the next example:

      ?- vertices([1-[3,5],2-[4],3-[],4-[5],5-[]], V).

      L = [1,2,3,4,5]

`edges(+Graph, -Edges)`

  Unify Edges with all edges appearing in graph Graph. In the next example:

      ?- vertices([1-[3,5],2-[4],3-[],4-[5],5-[]], V).

      L = [1,2,3,4,5]

`add_vertices(+Graph, +Vertices, -NewGraph)`

  Unify NewGraph with a new graph obtained by adding the list of vertices Vertices to the graph Graph. In the next example:

      ?- add_vertices([1-[3,5],2-[4],3-[],4-[5],
                       5-[],6-[],7-[],8-[]],
                      [0,2,9,10,11],
                         NG).

      NG = [0-[],1-[3,5],2-[4],3-[],4-[5],5-[],
            6-[],7-[],8-[],9-[],10-[],11-[]]

`del_vertices(+Graph, +Vertices, -NewGraph)`

  Unify NewGraph with a new graph obtained by deleting the list of vertices Vertices and all the edges that start from or go to a vertex in Vertices to the graph Graph. In the next example:

      ?- del_vertices([2,1],[1-[3,5],2-[4],3-[],
                       4-[5],5-[],6-[],7-[2,6],8-[]],NL).

      NL = [3-[],4-[5],5-[],6-[],7-[6],8-[]]

`add_edges(+Graph, +Edges, -NewGraph)`

  Unify NewGraph with a new graph obtained by adding the list of edges Edges to the graph Graph. In the next example:

      ?- add_edges([1-[3,5],2-[4],3-[],4-[5],5-[],6-[],
                    7-[],8-[]],[1-6,2-3,3-2,5-7,3-2,4-5],NL).

      NL = [1-[3,5,6],2-[3,4],3-[2],4-[5],5-[7],6-[],7-[],8-[]]

`del_edges(+Graph, +Edges, -NewGraph)`

  Unify NewGraph with a new graph obtained by removing the list of edges Edges from the graph Graph. Notice that no vertices are deleted. In the next example:

      ?- del_edges([1-[3,5],2-[4],3-[],4-[5],5-[],
                    6-[],7-[],8-[]],
                   [1-6,2-3,3-2,5-7,3-2,4-5,1-3],NL).

      NL = [1-[5],2-[4],3-[],4-[],5-[],6-[],7-[],8-[]]

`transpose(+Graph, -NewGraph)`

  Unify NewGraph with a new graph obtained from Graph by replacing all edges of the form V1-V2 by edges of the form V2-V1. The cost is `O(|V|^2)`. In the next example:

      ?- transpose([1-[3,5],2-[4],3-[],
                    4-[5],5-[],6-[],7-[],8-[]], NL).

      NL = [1-[],2-[],3-[1],4-[2],5-[1,4],6-[],7-[],8-[]]

  Notice that an undirected graph is its own transpose.

`neighbors(+Vertex, +Graph, -Vertices)`

  Unify Vertices with the list of neighbors of vertex Vertex in Graph. If the vertice is not in the graph fail. In the next example:

      ?- neighbors(4,[1-[3,5],2-[4],3-[],
                      4-[1,2,7,5],5-[],6-[],7-[],8-[]],
                   NL).

      NL = [1,2,7,5]

`neighbours(+Vertex, +Graph, -Vertices)`

  Unify Vertices with the list of neighbours of vertex Vertex in Graph. In the next example:

      ?- neighbours(4,[1-[3,5],2-[4],3-[],
                       4-[1,2,7,5],5-[],6-[],7-[],8-[]], NL).

      NL = [1,2,7,5]

`complement(+Graph, -NewGraph)`

  Unify NewGraph with the graph complementary to Graph. In the next example:

      ?- complement([1-[3,5],2-[4],3-[],
                     4-[1,2,7,5],5-[],6-[],7-[],8-[]], NL).

      NL = [1-[2,4,6,7,8],2-[1,3,5,6,7,8],3-[1,2,4,5,6,7,8],
            4-[3,5,6,8],5-[1,2,3,4,6,7,8],6-[1,2,3,4,5,7,8],
            7-[1,2,3,4,5,6,8],8-[1,2,3,4,5,6,7]]

`compose(+LeftGraph, +RightGraph, -NewGraph)`

  Compose the graphs LeftGraph and RightGraph to form NewGraph. In the next example:

      ?- compose([1-[2],2-[3]],[2-[4],3-[1,2,4]],L).

      L = [1-[4],2-[1,2,4],3-[]]

`top_sort(+Graph, -Sort)`

  Generate the set of nodes Sort as a topological sorting of graph Graph, if one is possible. In the next example we show how topological sorting works for a linear graph:

      ?- top_sort([_138-[_219],_219-[_139], _139-[]],L).

      L = [_138,_219,_139]

`top_sort(+Graph, -Sort0, -Sort)`

  Generate the difference list Sort-Sort0 as a topological sorting of graph Graph, if one is possible.

`transitive_closure(+Graph, +Closure)`

  Generate the graph Closure as the transitive closure of graph Graph. In the next example:

      ?- transitive_closure([1-[2,3],2-[4,5],4-[6]],L).

      L = [1-[2,3,4,5,6],2-[4,5,6],4-[6]]

`reachable(+Node, +Graph, -Vertices)`

  Unify Vertices with the set of all vertices in graph Graph that are reachable from Node. In the next example:

      ?- reachable(1,[1-[3,5],2-[4],3-[],4-[5],5-[]],V).

      V = [1,3,5]

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.29 Directed Graphs

The following graph manipulation routines use the red-black tree library to try to avoid linear-time scans of the graph for all graph operations. Graphs are represented as a red-black tree, where the key is the vertex, and the associated value is a list of vertices reachable from that vertex through an edge (ie, a list of edges).

`dgraph_new(+Graph)`

  Create a new directed graph. This operation must be performed before trying to use the graph.

`dgraph_vertices(+Graph, -Vertices)`

  Unify Vertices with all vertices appearing in graph Graph.

`dgraph_edge(+N1, +N2, +Graph)`

  Edge N1-N2 is an edge in directed graph Graph.

`dgraph_edges(+Graph, -Edges)`

  Unify Edges with all edges appearing in graph Graph.

`dgraph_add_vertices(+Graph, +Vertex, -NewGraph)`

  Unify NewGraph with a new graph obtained by adding vertex Vertex to the graph Graph.

`dgraph_add_vertices(+Graph, +Vertices, -NewGraph)`

  Unify NewGraph with a new graph obtained by adding the list of vertices Vertices to the graph Graph.

`dgraph_del_vertex(+Graph, +Vertex, -NewGraph)`

  Unify NewGraph with a new graph obtained by deleting vertex Vertex and all the edges that start from or go to Vertex to the graph Graph.

`dgraph_del_vertices(+Graph, +Vertices, -NewGraph)`

  Unify NewGraph with a new graph obtained by deleting the list of vertices Vertices and all the edges that start from or go to a vertex in Vertices to the graph Graph.

`dgraph_add_edge(+Graph, +N1, +N2, -NewGraph)`

  Unify NewGraph with a new graph obtained by adding the edge N1-N2 to the graph Graph.

`dgraph_add_edges(+Graph, +Edges, -NewGraph)`

  Unify NewGraph with a new graph obtained by adding the list of edges Edges to the graph Graph.

`dgraph_del_edge(+Graph, +N1, +N2, -NewGraph)`

  Succeeds if NewGraph unifies with a new graph obtained by removing the edge N1-N2 from the graph Graph. Notice that no vertices are deleted.

`dgraph_del_edges(+Graph, +Edges, -NewGraph)`

  Unify NewGraph with a new graph obtained by removing the list of edges Edges from the graph Graph. Notice that no vertices are deleted.

`dgraph_to_ugraph(+Graph, -UGraph)`

  Unify UGraph with the representation used by the ugraphs unweighted graphs library, that is, a list of the form V-Neighbors, where V is a node and Neighbors the nodes children.

`ugraph_to_dgraph( +UGraph, -Graph)`

  Unify Graph with the directed graph obtain from UGraph, represented in the form used in the ugraphs unweighted graphs library.

`dgraph_neighbors(+Vertex, +Graph, -Vertices)`

  Unify Vertices with the list of neighbors of vertex Vertex in Graph. If the vertice is not in the graph fail.

`dgraph_neighbours(+Vertex, +Graph, -Vertices)`

  Unify Vertices with the list of neighbours of vertex Vertex in Graph.

`dgraph_complement(+Graph, -NewGraph)`

  Unify NewGraph with the graph complementary to Graph.

`dgraph_transpose(+Graph, -Transpose)`

  Unify NewGraph with a new graph obtained from Graph by replacing all edges of the form V1-V2 by edges of the form V2-V1.

`dgraph_compose(+Graph1, +Graph2, -ComposedGraph)`

  Unify ComposedGraph with a new graph obtained by composing Graph1 and Graph2, ie, ComposedGraph has an edge V1-V2 iff there is a V such that V1-V in Graph1 and V-V2 in Graph2.

`dgraph_transitive_closure(+Graph, -Closure)`

  Unify Closure with the transitive closure of graph Graph.

`dgraph_symmetric_closure(+Graph, -Closure)`

  Unify Closure with the symmetric closure of graph Graph, that is, if Closure contains an edge U-V it must also contain the edge V-U.

`dgraph_top_sort(+Graph, -Vertices)`

  Unify Vertices with the topological sort of graph Graph.

`dgraph_top_sort(+Graph, -Vertices, ?Vertices0)`

  Unify the difference list Vertices-Vertices0 with the topological sort of graph Graph.

`dgraph_min_path(+V1, +V1, +Graph, -Path, ?Costt)`

  Unify the list Path with the minimal cost path between nodes N1 and N2 in graph Graph. Path Path has cost Cost.

`dgraph_max_path(+V1, +V1, +Graph, -Path, ?Costt)`

  Unify the list Path with the maximal cost path between nodes N1 and N2 in graph Graph. Path Path has cost Cost.

`dgraph_min_paths(+V1, +Graph, -Paths)`

  Unify the list Paths with the minimal cost paths from node N1 to the nodes in graph Graph.

`dgraph_isomorphic(+Vs, +NewVs, +G0, -GF)`

  Unify the list GF with the graph isomorphic to G0 where vertices in Vs map to vertices in NewVs.

`dgraph_path(+Vertex, +Graph, ?Path)`

  The path Path is a path starting at vertex Vertex in graph Graph.

`dgraph_reachable(+Vertex, +Graph, ?Edges)`

  The path Path is a path starting at vertex Vertex in graph Graph.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.30 Undirected Graphs

The following graph manipulation routines use the red-black tree graph library to implement undirected graphs. Mostly, this is done by having two directed edges per undirected edge.

`undgraph_new(+Graph)`

  Create a new directed graph. This operation must be performed before trying to use the graph.

`undgraph_vertices(+Graph, -Vertices)`

  Unify Vertices with all vertices appearing in graph Graph.

`undgraph_edge(+N1, +N2, +Graph)`

  Edge N1-N2 is an edge in undirected graph Graph.

`undgraph_edges(+Graph, -Edges)`

  Unify Edges with all edges appearing in graph Graph.

`undgraph_add_vertices(+Graph, +Vertices, -NewGraph)`

  Unify NewGraph with a new graph obtained by adding the list of vertices Vertices to the graph Graph.

`undgraph_del_vertices(+Graph, +Vertices, -NewGraph)`

  Unify NewGraph with a new graph obtained by deleting the list of vertices Vertices and all the edges that start from or go to a vertex in Vertices to the graph Graph.

`undgraph_add_edges(+Graph, +Edges, -NewGraph)`

  Unify NewGraph with a new graph obtained by adding the list of edges Edges to the graph Graph.

`undgraph_del_edges(+Graph, +Edges, -NewGraph)`

  Unify NewGraph with a new graph obtained by removing the list of edges Edges from the graph Graph. Notice that no vertices are deleted.

`undgraph_neighbors(+Vertex, +Graph, -Vertices)`

  Unify Vertices with the list of neighbors of vertex Vertex in Graph. If the vertice is not in the graph fail.

`undgraph_neighbours(+Vertex, +Graph, -Vertices)`

  Unify Vertices with the list of neighbours of vertex Vertex in Graph.

`undgraph_complement(+Graph, -NewGraph)`

  Unify NewGraph with the graph complementary to Graph.

`dgraph_to_undgraph( +DGraph, -UndGraph)`

  Unify UndGraph with the undirected graph obtained from the directed graph DGraph.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.31 Lambda Expressions

This library, designed and implemented by Ulrich Neumerkel, provides lambda expressions to simplify higher order programming based on `call/N`.

Lambda expressions are represented by ordinary Prolog terms. There are two kinds of lambda expressions:

        Free+\X1^X2^ ..^XN^Goal

             \X1^X2^ ..^XN^Goal

The second is a shorthand for`t+\X1^X2^..^XN^Goal`, where `Xi` are the parameters.

Goal is a goal or continuation (Syntax note: Operators within Goal require parentheses due to the low precedence of the `^` operator).

Free contains variables that are valid outside the scope of the lambda expression. They are thus free variables within.

All other variables of Goal are considered local variables. They must not appear outside the lambda expression. This restriction is currently not checked. Violations may lead to unexpected bindings.

In the following example the parentheses around `X>3` are necessary.

    ?- use_module(library(lambda)).
    ?- use_module(library(apply)).

    ?- maplist(\X^(X>3),[4,5,9]).
    true.

In the following X is a variable that is shared by both instances of the lambda expression. The second query illustrates the cooperation of continuations and lambdas. The lambda expression is in this case a continuation expecting a further argument.

    ?- Xs = [A,B], maplist(X+\Y^dif(X,Y), Xs).
    Xs = [A, B],
    dif(X, A),
    dif(X, B).

    ?- Xs = [A,B], maplist(X+\dif(X), Xs).
    Xs = [A, B],
    dif(X, A),
    dif(X, B).

The following queries are all equivalent. To see this, use the fact `f(x,y)`.

    ?- call(f,A1,A2).
    ?- call(\X^f(X),A1,A2).
    ?- call(\X^Y^f(X,Y), A1,A2).
    ?- call(\X^(X+\Y^f(X,Y)), A1,A2).
    ?- call(call(f, A1),A2).
    ?- call(f(A1),A2).
    ?- f(A1,A2).
    A1 = x,
    A2 = y.

Further discussions at http://www.complang.tuwien.ac.at/ulrich/Prolog-inedit/ISO-Hiord.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.32 LAM

This library provides a set of utilities for interfacing with LAM MPI. The following routines are available once included with the `use_module(library(lam_mpi))` command. The yap should be invoked using the LAM mpiexec or mpirun commands (see LAM manual for more details).

`mpi_init`

  Sets up the mpi environment. This predicate should be called before any other MPI predicate.

`mpi_finalize`

  Terminates the MPI execution environment. Every process must call this predicate before exiting.

`mpi_comm_size(-Size)`

  Unifies Size with the number of processes in the MPI environment.

`mpi_comm_rank(-Rank)`

  Unifies Rank with the rank of the current process in the MPI environment.

`mpi_version(-Major,-Minor)`

  Unifies Major and Minor with, respectively, the major and minor version of the MPI.

`mpi_send(+Data,+Dest,+Tag)`

  Blocking communication predicate. The message in Data, with tag Tag, is sent immediately to the processor with rank Dest. The predicate succeeds after the message being sent.

`mpi_isend(+Data,+Dest,+Tag,-Handle)`

  Non blocking communication predicate. The message in Data, with tag Tag, is sent whenever possible to the processor with rank Dest. An Handle to the message is returned to be used to check for the status of the message, using the `mpi_wait` or `mpi_test` predicates. Until `mpi_wait` is called, the memory allocated for the buffer containing the message is not released.

`mpi_recv(?Source,?Tag,-Data)`

  Blocking communication predicate. The predicate blocks until a message is received from processor with rank Source and tag Tag. The message is placed in Data.

`mpi_irecv(?Source,?Tag,-Handle)`

  Non-blocking communication predicate. The predicate returns an Handle for a message that will be received from processor with rank Source and tag Tag. Note that the predicate succeeds immediately, even if no message has been received. The predicate `mpi_wait_recv` should be used to obtain the data associated to the handle.

`mpi_wait_recv(?Handle,-Status,-Data)`

  Completes a non-blocking receive operation. The predicate blocks until a message associated with handle Hanlde is buffered. The predicate succeeds unifying Status with the status of the message and Data with the message itself.

`mpi_test_recv(?Handle,-Status,-Data)`

  Provides information regarding a handle. If the message associated with handle Hanlde is buffered then the predicate succeeds unifying Status with the status of the message and Data with the message itself. Otherwise, the predicate fails.

`mpi_wait(?Handle,-Status)`

  Completes a non-blocking operation. If the operation was a `mpi_send`, the predicate blocks until the message is buffered or sent by the runtime system. At this point the send buffer is released. If the operation was a `mpi_recv`, it waits until the message is copied to the receive buffer. Status is unified with the status of the message.

`mpi_test(?Handle,-Status)`

  Provides information regarding the handle Handle, ie., if a communication operation has been completed. If the operation associate with Hanlde has been completed the predicate succeeds with the completion status in Status, otherwise it fails.

`mpi_barrier`

  Collective communication predicate. Performs a barrier synchronization among all processes. Note that a collective communication means that all processes call the same predicate. To be able to use a regular `mpi_recv` to receive the messages, one should use `mpi_bcast2`.

`mpi_bcast2(+Root, +Data)`

  Broadcasts the message Data from the process with rank Root to all other processes.

`mpi_bcast3(+Root, +Data, +Tag)`

  Broadcasts the message Data with tag Tag from the process with rank Root to all other processes.

`mpi_ibcast(+Root, +Data, +Tag)`

  Non-blocking operation. Broadcasts the message Data with tag Tag from the process with rank Root to all other processes.

`mpi_gc`

  Attempts to perform garbage collection with all the open handles associated with send and non-blocking broadcasts. For each handle it tests it and the message has been delivered the handle and the buffer are released.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 7.33 Block Diagram

This library provides a way of visualizing a prolog program using modules with blocks. To use it use: `:-use_module(library(block_diagram))`.

`make_diagram(+inputfilename, +ouputfilename)`

  This will crawl the files following the use_module, ensure_loaded directives withing the inputfilename. The result will be a file in dot format. You can make a pdf at the shell by asking `dot -Tpdf filename > output.pdf`.

`make_diagram(+inputfilename, +ouputfilename, +predicate, +depth, +extension)`

  The same as `make_diagram/2` but you can define how many of the imported/exporeted predicates will be shown with predicate, and how deep the crawler is allowed to go with depth. The extension is used if the file use module directives do not include a file extension.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 8 SWI-Prolog Emulation

This library provides a number of SWI-Prolog builtins that are not by default in YAP. This support is loaded with the `expects_dialect(swi)` command.

`append(?List1,?List2,?List3)`

  Succeeds when List3 unifies with the concatenation of List1 and List2. The predicate can be used with any instantiation pattern (even three variables).

`between(+Low,+High,?Value)`

  Low and High are integers, High less or equal than Low. If Value is an integer, Low less or equal than Value less or equal than High. When Value is a variable it is successively bound to all integers between Low and High. If High is `inf`, `between/3` is true iff Value less or equal than Low, a feature that is particularly interesting for generating integers from a certain value.

`chdir(+Dir)`

  Compatibility predicate. New code should use `working_directory/2`.

`concat_atom(+List,-Atom)`

  List is a list of atoms, integers or floating point numbers. Succeeds if Atom can be unified with the concatenated elements of List. If List has exactly 2 elements it is equivalent to `atom_concat/3`, allowing for variables in the list.

`concat_atom(?List,+Separator,?Atom)`

  Creates an atom just like concat_atom/2, but inserts Separator between each pair of atoms. For example: \

      ?- concat_atom([gnu, gnat], ', ', A).

      A = 'gnu, gnat'

  (Unimplemented) This predicate can also be used to split atoms by instantiating Separator and Atom:

      ?- concat_atom(L, -, 'gnu-gnat').

      L = [gnu, gnat]

`nth1(+Index,?List,?Elem)`

  Succeeds when the Index-th element of List unifies with Elem. Counting starts at 1.

  Set environment variable. Name and Value should be instantiated to atoms or integers. The environment variable will be passed to `shell/[0-2]` and can be requested using `getenv/2`. They also influence `expand_file_name/2`.

`setenv(+Name,+Value)`

  Set environment variable. Name and Value should be instantiated to atoms or integers. The environment variable will be passed to `shell/[0-2]` and can be requested using `getenv/2`. They also influence `expand_file_name/2`.

`term_to_atom(?Term,?Atom)`

  Succeeds if Atom describes a term that unifies with Term. When Atom is instantiated Atom is converted and then unified with Term. If Atom has no valid syntax, a `syntax_error` exception is raised. Otherwise Term is “written” on Atom using `write/1`.

`working_directory(-Old,+New)`

  Unify Old with an absolute path to the current working directory and change working directory to New. Use the pattern `working_directory(CWD, CWD)` to get the current directory. See also `absolute_file_name/2` and `chdir/1`.

`@Term1 =@= @Term2`

  True iff Term1 and Term2 are structurally equivalent. I.e. if Term1 and Term2 are variants of each other.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 8.1 Invoking Predicates on all Members of a List

All the predicates in this section call a predicate on all members of a list or until the predicate called fails. The predicate is called via `call/[2..]`, which implies common arguments can be put in front of the arguments obtained from the list(s). For example:

    ?- maplist(plus(1), [0, 1, 2], X).

    X = [1, 2, 3]

we will phrase this as “Predicate is applied on ...”

`maplist(+Pred,+List)`

  Pred is applied successively on each element of List until the end of the list or Pred fails. In the latter case `maplist/2` fails.

`maplist(+Pred,+List1,+List2)`

  Apply Pred on all successive pairs of elements from List1 and List2. Fails if Pred can not be applied to a pair. See the example above.

`maplist(+Pred,+List1,+List2,+List4)`

  Apply Pred on all successive triples of elements from List1, List2 and List3. Fails if Pred can not be applied to a triple. See the example above.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 8.2 Forall

`forall(+Cond,+Action)`

  For all alternative bindings of Cond Action can be proven. The next example verifies that all arithmetic statements in the list L are correct. It does not say which is wrong if one proves wrong.

      ?- forall(member(Result = Formula, [2 = 1 + 1, 4 = 2 * 2]),
                       Result =:= Formula).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 9 SWI Global variables

SWI-Prolog global variables are associations between names (atoms) and terms. They differ in various ways from storing information using `assert/1` or `recorda/3`.

- The value lives on the Prolog (global) stack. This implies that lookup time is independent from the size of the term. This is particulary interesting for large data structures such as parsed XML documents or the CHR global constraint store.
- They support both global assignment using `nb_setval/2` and backtrackable assignment using `b_setval/2`.
- Only one value (which can be an arbitrary complex Prolog term) can be associated to a variable at a time.
- Their value cannot be shared among threads. Each thread has its own namespace and values for global variables.
- Currently global variables are scoped globally. We may consider module scoping in future versions.

Both `b_setval/2` and `nb_setval/2` implicitly create a variable if the referenced name does not already refer to a variable.

Global variables may be initialised from directives to make them available during the program lifetime, but some considerations are necessary for saved-states and threads. Saved-states to not store global variables, which implies they have to be declared with `initialization/1` to recreate them after loading the saved state. Each thread has its own set of global variables, starting with an empty set. Using `thread_inititialization/1` to define a global variable it will be defined, restored after reloading a saved state and created in all threads that are created after the registration.

`b_setval(+Name,+Value)`

  Associate the term Value with the atom Name or replaces the currently associated value with Value. If Name does not refer to an existing global variable a variable with initial value `[]` is created (the empty list). On backtracking the assignment is reversed.

`b_getval(+Name,-Value)`

  Get the value associated with the global variable Name and unify it with Value. Note that this unification may further instantiate the value of the global variable. If this is undesirable the normal precautions (double negation or `copy_term/2`) must be taken. The `b_getval/2` predicate generates errors if Name is not an atom or the requested variable does not exist.

`nb_setval(+Name,+Value)`

  Associates a copy of Value created with `duplicate_term/2` with the atom Name. Note that this can be used to set an initial value other than `[]` prior to backtrackable assignment.

`nb_getval(+Name,-Value)`

  The `nb_getval/2` predicate is a synonym for b_getval/2, introduced for compatibility and symmetry. As most scenarios will use a particular global variable either using non-backtrackable or backtrackable assignment, using `nb_getval/2` can be used to document that the variable is used non-backtrackable.

`nb_current(?Name,?Value)`

  Enumerate all defined variables with their value. The order of enumeration is undefined.

`nb_delete(?Name)`

  Delete the named global variable.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 9.1 Compatibility of Global Variables

Global variables have been introduced by various Prolog implementations recently. YAP follows their implementation in SWI-Prolog, itself based on hProlog by Bart Demoen. Jan and Bart decided that the semantics if hProlog `nb_setval/2`, which is equivalent to `nb_linkval/2` is not acceptable for normal Prolog users as the behaviour is influenced by how builtin predicates constructing terms (`read/1`, `=../2`, etc.) are implemented.

GNU-Prolog provides a rich set of global variables, including arrays. Arrays can be implemented easily in SWI-Prolog using `functor/3` and `setarg/3` due to the unrestricted arity of compound terms.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 10 Extensions to Prolog

YAP includes several extensions that are not enabled by default, but that can be used to extend the functionality of the system. These options can be set at compilation time by enabling the related compilation flag, as explained in the `Makefile`

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 10.1 Rational Trees

Prolog unification is not a complete implementation. For efficiency considerations, Prolog systems do not perform occur checks while unifying terms. As an example, `X = a(X)` will not fail but instead will create an infinite term of the form `a(a(a(a(a(...)))))`, or rational tree.

Rational trees are now supported by default in YAP. In previous versions, this was not the default and these terms could easily lead to infinite computation. For example, `X = a(X), X = X` would enter an infinite loop.

The `RATIONAL_TREES` flag improves support for these terms. Internal primitives are now aware that these terms can exist, and will not enter infinite loops. Hence, the previous unification will succeed. Another example, `X = a(X), ground(X)` will succeed instead of looping. Other affected built-ins include the term comparison primitives, `numbervars/3`, `copy_term/2`, and the internal data base routines. The support does not extend to Input/Output routines or to `assert/1` YAP does not allow directly reading rational trees, and you need to use `write_depth/2` to avoid entering an infinite cycle when trying to write an infinite term.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 10.2 Co-routining

Prolog uses a simple left-to-right flow of control. It is sometimes convenient to change this control so that goals will only be executed when conditions are fulfilled. This may result in a more "data-driven" execution, or may be necessary to correctly implement extensions such as negation by default.

The `COROUTINING` flag enables this option. Note that the support for coroutining will in general slow down execution.

The following declaration is supported:

`block/1`

  The argument to `block/1` is a condition on a goal or a conjunction of conditions, with each element separated by commas. Each condition is of the form `predname(C1,...,CN)`, where N is the arity of the goal, and each CI is of the form `-`, if the argument must suspend until the first such variable is bound, or `?`, otherwise.

`wait/1`

  The argument to `wait/1` is a predicate descriptor or a conjunction of these predicates. These predicates will suspend until their first argument is bound.

The following primitives are supported:

`dif(X,Y)`

  Succeed if the two arguments do not unify. A call to `dif/2` will suspend if unification may still succeed or fail, and will fail if they always unify.

`freeze(?X,:G)`

  Delay execution of goal G until the variable X is bound.

`frozen(X,G)`

  Unify G with a conjunction of goals suspended on variable X, or `true` if no goal has suspended.

`when(+C,:G)`

  Delay execution of goal G until the conditions C are satisfied. The conditions are of the following form:

  `C1,C2`

    Delay until both conditions C1 and C2 are satisfied.

  `C1;C2`

    Delay until either condition C1 or condition C2 is satisfied.

  `?=(V1,C2)`

    Delay until terms V1 and V1 have been unified.

  `nonvar(V)`

    Delay until variable V is bound.

  `ground(V)`

    Delay until variable V is ground.

  Note that `when/2` will fail if the conditions fail.

`call_residue(:G,L)`

  Call goal G. If subgoals of G are still blocked, return a list containing these goals and the variables they are blocked in. The goals are then considered as unblocked. The next example shows a case where `dif/2` suspends twice, once outside `call_residue/2`, and the other inside:

      ?- dif(X,Y),
             call_residue((dif(X,Y),(X = f(Z) ; Y = f(Z))), L).

      X = f(Z),
      L = [[Y]-dif(f(Z),Y)],
      dif(f(Z),Y) ? ;

      Y = f(Z),
      L = [[X]-dif(X,f(Z))],
      dif(X,f(Z)) ? ;

      no

  The system only reports one invocation of `dif/2` as having suspended.

`call_residue_vars(:G,L)`

  Call goal G and unify L with a list of all constrained variables created during execution of G:

        ?- dif(X,Z), call_residue_vars(dif(X,Y),L).
      dif(X,Z), call_residue_vars(dif(X,Y),L).
      L = [Y],
      dif(X,Z),
      dif(X,Y) ? ;

      no

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 11 Attributed Variables

YAP supports attributed variables, originally developed at OFAI by Christian Holzbaur. Attributes are a means of declaring that an arbitrary term is a property for a variable. These properties can be updated during forward execution. Moreover, the unification algorithm is aware of attributed variables and will call user defined handlers when trying to unify these variables.

Attributed variables provide an elegant abstraction over which one can extend Prolog systems. Their main application so far has been in implementing constraint handlers, such as Holzbaur’s CLPQR, Fruewirth and Holzbaur’s CHR, and CLP(BN).

Different Prolog systems implement attributed variables in different ways. Traditionally, YAP has used the interface designed by SICStus Prolog. This interface is still available in the `atts` library, but from YAP-6.0.3 we recommend using the hProlog, SWI style interface. The main reason to do so is that most packages included in YAP that use attributed variables, such as CHR, CLP(FD), and CLP(QR), rely on the SWI-Prolog interface.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 11.1 hProlog and SWI-Prolog style Attribute Declarations

The following documentation is taken from the SWI-Prolog manual.

Binding an attributed variable schedules a goal to be executed at the first possible opportunity. In the current implementation the hooks are executed immediately after a successful unification of the clause-head or successful completion of a foreign language (built-in) predicate. Each attribute is associated to a module and the hook `attr_unify_hook/2` is executed in this module. The example below realises a very simple and incomplete finite domain reasoner.

    :- module(domain,
    	  [ domain/2			% Var, ?Domain
    	  ]).
    :- use_module(library(ordsets)).

    domain(X, Dom) :-
    	var(Dom), !,
    	get_attr(X, domain, Dom).
    domain(X, List) :-
    	list_to_ord_set(List, Domain),
    	put_attr(Y, domain, Domain),
    	X = Y.

    %	An attributed variable with attribute value Domain has been
    %	assigned the value Y

    attr_unify_hook(Domain, Y) :-
    	(   get_attr(Y, domain, Dom2)
    	->  ord_intersection(Domain, Dom2, NewDomain),
    	    (   NewDomain == []
    	    ->	fail
    	    ;	NewDomain = [Value]
    	    ->	Y = Value
    	    ;	put_attr(Y, domain, NewDomain)
    	    )
    	;   var(Y)
    	->  put_attr( Y, domain, Domain )
    	;   ord_memberchk(Y, Domain)
    	).

    %	Translate attributes from this module to residual goals

    attribute_goals(X) -->
    	{ get_attr(X, domain, List) },
    	[domain(X, List)].

Before explaining the code we give some example queries:

`?- domain(X, [a,b]), X = c` | `fail`
`domain(X, [a,b]), domain(X, [a,c]).` | `X=a`
`domain(X, [a,b,c]), domain(X, [a,c]).` | `domain(X, [a,c]).`

The predicate `domain/2` fetches (first clause) or assigns (second clause) the variable a domain, a set of values it can be unified with. In the second clause first associates the domain with a fresh variable and then unifies X to this variable to deal with the possibility that X already has a domain. The predicate `attr_unify_hook/2` is a hook called after a variable with a domain is assigned a value. In the simple case where the variable is bound to a concrete value we simply check whether this value is in the domain. Otherwise we take the intersection of the domains and either fail if the intersection is empty (first example), simply assign the value if there is only one value in the intersection (second example) or assign the intersection as the new domain of the variable (third example). The nonterminal `attribute_goals/3` is used to translate remaining attributes to user-readable goals that, when executed, reinstate these attributes.

`attvar(?Term)`

  Succeeds if `Term` is an attributed variable. Note that `var/1` also succeeds on attributed variables. Attributed variables are created with `put_attr/3`.

`put_attr(+Var,+Module,+Value)`

  If Var is a variable or attributed variable, set the value for the attribute named Module to Value. If an attribute with this name is already associated with Var, the old value is replaced. Backtracking will restore the old value (i.e., an attribute is a mutable term. See also `setarg/3`). This predicate raises a representation error if Var is not a variable and a type error if Module is not an atom.

`get_attr(+Var,+Module,-Value)`

  Request the current value for the attribute named Module. If Var is not an attributed variable or the named attribute is not associated to Var this predicate fails silently. If Module is not an atom, a type error is raised.

`del_attr(+Var,+Module)`

  Delete the named attribute. If Var loses its last attribute it is transformed back into a traditional Prolog variable. If Module is not an atom, a type error is raised. In all other cases this predicate succeeds regardless whether or not the named attribute is present.

`attr_unify_hook(+AttValue,+VarValue)`

  Hook that must be defined in the module an attributed variable refers to. Is is called after the attributed variable has been unified with a non-var term, possibly another attributed variable. AttValue is the attribute that was associated to the variable in this module and VarValue is the new value of the variable. Normally this predicate fails to veto binding the variable to VarValue, forcing backtracking to undo the binding. If VarValue is another attributed variable the hook often combines the two attribute and associates the combined attribute with VarValue using `put_attr/3`.

`attr_portray_hook(+AttValue,+Var)`

  Called by `write_term/2` and friends for each attribute if the option `attributes(portray)` is in effect. If the hook succeeds the attribute is considered printed. Otherwise `Module = ...` is printed to indicate the existence of a variable.

`attribute_goals(+Var,-Gs,+GsRest)`

  This nonterminal, if it is defined in a module, is used by copy_term/3 to project attributes of that module to residual goals. It is also used by the toplevel to obtain residual goals after executing a query.

Normal user code should deal with `put_attr/3`, `get_attr/3` and `del_attr/2`. The routines in this section fetch or set the entire attribute list of a variables. Use of these predicates is anticipated to be restricted to printing and other special purpose operations.

`get_attrs(+Var,-Attributes)`

  Get all attributes of Var. Attributes is a term of the form `att(Module, Value, MoreAttributes)`, where MoreAttributes is `[]` for the last attribute.

`put_attrs(+Var,+Attributes)`

  Set all attributes of Var. See `get_attrs/2` for a description of Attributes.

`del_attrs(+Var)`

  If Var is an attributed variable, delete all its attributes. In all other cases, this predicate succeeds without side-effects.

`term_attvars(+Term,-AttVars)`

  AttVars is a list of all attributed variables in Term and its attributes. I.e., `term_attvars/2` works recursively through attributes. This predicate is Cycle-safe.

`copy_term(?TI,-TF,-Goals)`

  Term TF is a variant of the original term TI, such that for each variable V in the term TI there is a new variable V’ in term TF without any attributes attached. Attributed variables are thus converted to standard variables. Goals is unified with a list that represents the attributes. The goal `maplist(call,Goals)` can be called to recreate the attributes.

  Before the actual copying, `copy_term/3` calls `attribute_goals/1` in the module where the attribute is defined.

`copy_term_nat(?TI,-TF)`

  As `copy_term/2`. Attributes however, are not copied but replaced by fresh variables.

`term_variables(?Term, -Variables)`

  Unify Variables with the list of all variables of term Term. The variables occur in the order of their first appearance when traversing the term depth-first, left-to-right.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 11.2 SICStus Prolog style Attribute Declarations

Old style attribute declarations are activated through loading the library `atts` . The command

    | ?- use_module(library(atts)).

enables this form of use of attributed variables. The package provides the following functionality:

- Each attribute must be declared first. Attributes are described by a functor and are declared per module. Each Prolog module declares its own sets of attributes. Different modules may have different functors with the same module.
- The built-in `put_atts/2` adds or deletes attributes to a variable. The variable may be unbound or may be an attributed variable. In the latter case, YAP discards previous values for the attributes.
- The built-in `get_atts/2` can be used to check the values of an attribute associated with a variable.
- The unification algorithm calls the user-defined predicate `verify_attributes/3` before trying to bind an attributed variable. Unification will resume after this call.
- The user-defined predicate `attribute_goal/2` converts from an attribute to a goal.
- The user-defined predicate `project_attributes/2` is used from a set of variables into a set of constraints or goals. One application of `project_attributes/2` is in the top-level, where it is used to output the set of floundered constraints at the end of a query.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 11.2.1 Attribute Declarations

Attributes are compound terms associated with a variable. Each attribute has a name which is private to the module in which the attribute was defined. Variables may have at most one attribute with a name. Attribute names are defined with the following declaration:

    :- attribute AttributeSpec, ..., AttributeSpec.

where each AttributeSpec has the form (Name/Arity). One single such declaration is allowed per module Module.

Although the YAP module system is predicate based, attributes are local to modules. This is implemented by rewriting all calls to the built-ins that manipulate attributes so that attribute names are preprocessed depending on the module. The `user:goal_expansion/3` mechanism is used for this purpose.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 11.2.2 Attribute Manipulation

The attribute manipulation predicates always work as follows:

1. The first argument is the unbound variable associated with attributes,
2. The second argument is a list of attributes. Each attribute will be a Prolog term or a constant, prefixed with the `+` and `-` unary operators. The prefix `+` may be dropped for convenience.

The following three procedures are available to the user. Notice that these built-ins are rewritten by the system into internal built-ins, and that the rewriting process depends on the module on which the built-ins have been invoked.

`Module:get_atts(-Var,?ListOfAttributes)`

  Unify the list ?ListOfAttributes with the attributes for the unbound variable Var. Each member of the list must be a bound term of the form `+(Attribute)`, `-(Attribute)` (the `kbd` prefix may be dropped). The meaning of `+` and `-` is:

`+(Attribute)`

  Unifies Attribute with a corresponding attribute associated with Var, fails otherwise.

`-(Attribute)`

  Succeeds if a corresponding attribute is not associated with Var. The arguments of Attribute are ignored.

`Module:put_atts(-Var,?ListOfAttributes)`

  Associate with or remove attributes from a variable Var. The attributes are given in ?ListOfAttributes, and the action depends on how they are prefixed:

`+(Attribute)`

  Associate Var with Attribute. A previous value for the attribute is simply replace (like with `set_mutable/2`).

`-(Attribute)`

  Remove the attribute with the same name. If no such attribute existed, simply succeed.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 11.2.3 Attributed Unification

The user-predicate predicate `verify_attributes/3` is called when attempting to unify an attributed variable which might have attributes in some Module.

`Module:verify_attributes(-Var, +Value, -Goals)`

  The predicate is called when trying to unify the attributed variable Var with the Prolog term Value. Note that Value may be itself an attributed variable, or may contain attributed variables. The goal `verify_attributes/3` is actually called before Var is unified with Value.

  It is up to the user to define which actions may be performed by `verify_attributes/3` but the procedure is expected to return in Goals a list of goals to be called after Var is unified with Value. If `verify_attributes/3` fails, the unification will fail.

  Notice that the `verify_attributes/3` may be called even if Var has no attributes in module `Module`. In this case the routine should simply succeed with Goals unified with the empty list.

`attvar(-Var)`

  Succeed if Var is an attributed variable.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 11.2.4 Displaying Attributes

Attributes are usually presented as goals. The following routines are used by built-in predicates such as `call_residue/2` and by the Prolog top-level to display attributes:

`Module:attribute_goal(-Var, -Goal)`

  User-defined procedure, called to convert the attributes in Var to a Goal. Should fail when no interpretation is available.

`Module:project_attributes(-QueryVars, +AttrVars)`

  User-defined procedure, called to project the attributes in the query, AttrVars, given that the set of variables in the query is QueryVars.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 11.2.5 Projecting Attributes

Constraint solvers must be able to project a set of constraints to a set of variables. This is useful when displaying the solution to a goal, but may also be used to manipulate computations. The user-defined `project_attributes/2` is responsible for implementing this projection.

`Module:project_attributes(+QueryVars, +AttrVars)`

  Given a list of variables QueryVars and list of attributed variables AttrVars, project all attributes in AttrVars to QueryVars. Although projection is constraint system dependent, typically this will involve expressing all constraints in terms of QueryVars and considering all remaining variables as existentially quantified.

Projection interacts with `attribute_goal/2` at the Prolog top level. When the query succeeds, the system first calls `project_attributes/2`. The system then calls `attribute_goal/2` to get a user-level representation of the constraints. Typically, `attribute_goal/2` will convert from the original constraints into a set of new constraints on the projection, and these constraints are the ones that will have an `attribute_goal/2` handler.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 11.2.6 Attribute Examples

The following two examples example is taken from the SICStus Prolog manual. It sketches the implementation of a simple finite domain “solver”. Note that an industrial strength solver would have to provide a wider range of functionality and that it quite likely would utilize a more efficient representation for the domains proper. The module exports a single predicate `domain(-Var,?Domain)` which associates Domain (a list of terms) with Var. A variable can be queried for its domain by leaving Domain unbound.

We do not present here a definition for `project_attributes/2`. Projecting finite domain constraints happens to be difficult.

    :- module(domain, [domain/2]).

    :- use_module(library(atts)).
    :- use_module(library(ordsets), [
            ord_intersection/3,
            ord_intersect/2,
            list_to_ord_set/2
       ]).

    :- attribute dom/1.

    verify_attributes(Var, Other, Goals) :-
            get_atts(Var, dom(Da)), !,          % are we involved?
            (   var(Other) ->                   % must be attributed then
                (   get_atts(Other, dom(Db)) -> %   has a domain?
                    ord_intersection(Da, Db, Dc),
                    Dc = [El|Els],              % at least one element
                    (   Els = [] ->             % exactly one element
                        Goals = [Other=El]      % implied binding
                    ;   Goals = [],
                        put_atts(Other, dom(Dc))% rescue intersection
                    )
                ;   Goals = [],
                    put_atts(Other, dom(Da))    % rescue the domain
                )
            ;   Goals = [],
                ord_intersect([Other], Da)      % value in domain?
            ).
    verify_attributes(_, _, []).                % unification triggered
                                                % because of attributes
                                                % in other modules

    attribute_goal(Var, domain(Var,Dom)) :-     % interpretation as goal
            get_atts(Var, dom(Dom)).

    domain(X, Dom) :-
            var(Dom), !,
            get_atts(X, dom(Dom)).
    domain(X, List) :-
            list_to_ord_set(List, Set),
            Set = [El|Els],                     % at least one element
            (   Els = [] ->                     % exactly one element
                X = El                          % implied binding
            ;   put_atts(Fresh, dom(Set)),
                X = Fresh                       % may call
                                                % verify_attributes/3
            ).

Note that the “implied binding” `Other=El` was deferred until after the completion of `verify_attribute/3`. Otherwise, there might be a danger of recursively invoking `verify_attribute/3`, which might bind `Var`, which is not allowed inside the scope of `verify_attribute/3`. Deferring unifications into the third argument of `verify_attribute/3` effectively serializes the calls to `verify_attribute/3`.

Assuming that the code resides in the file ‘`domain.yap`’, we can use it via:

    | ?- use_module(domain).

Let’s test it:

    | ?- domain(X,[5,6,7,1]), domain(Y,[3,4,5,6]), domain(Z,[1,6,7,8]).

    domain(X,[1,5,6,7]),
    domain(Y,[3,4,5,6]),
    domain(Z,[1,6,7,8]) ?

    yes
    | ?- domain(X,[5,6,7,1]), domain(Y,[3,4,5,6]), domain(Z,[1,6,7,8]),
         X=Y.

    Y = X,
    domain(X,[5,6]),
    domain(Z,[1,6,7,8]) ?

    yes
    | ?- domain(X,[5,6,7,1]), domain(Y,[3,4,5,6]), domain(Z,[1,6,7,8]),
         X=Y, Y=Z.

    X = 6,
    Y = 6,
    Z = 6

To demonstrate the use of the Goals argument of `verify_attributes/3`, we give an implementation of `freeze/2`. We have to name it `myfreeze/2` in order to avoid a name clash with the built-in predicate of the same name.

    :- module(myfreeze, [myfreeze/2]).

    :- use_module(library(atts)).

    :- attribute frozen/1.

    verify_attributes(Var, Other, Goals) :-
            get_atts(Var, frozen(Fa)), !,       % are we involved?
            (   var(Other) ->                   % must be attributed then
                (   get_atts(Other, frozen(Fb)) % has a pending goal?
                ->  put_atts(Other, frozen((Fa,Fb))) % rescue conjunction
                ;   put_atts(Other, frozen(Fa)) % rescue the pending goal
                ),
                Goals = []
            ;   Goals = [Fa]
            ).
    verify_attributes(_, _, []).

    attribute_goal(Var, Goal) :-                % interpretation as goal
            get_atts(Var, frozen(Goal)).

    myfreeze(X, Goal) :-
            put_atts(Fresh, frozen(Goal)),
            Fresh = X.

Assuming that this code lives in file ‘`myfreeze.yap`’, we would use it via:

    | ?- use_module(myfreeze).
    | ?- myfreeze(X,print(bound(x,X))), X=2.

    bound(x,2)                      % side effect
    X = 2                           % bindings

The two solvers even work together:

    | ?- myfreeze(X,print(bound(x,X))), domain(X,[1,2,3]),
         domain(Y,[2,10]), X=Y.

    bound(x,2)                      % side effect
    X = 2,                          % bindings
    Y = 2

The two example solvers interact via bindings to shared attributed variables only. More complicated interactions are likely to be found in more sophisticated solvers. The corresponding `verify_attributes/3` predicates would typically refer to the attributes from other known solvers/modules via the module prefix in `Module:get_atts/2`.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 12 Constraint Logic Programming over Reals

YAP now uses the CLP(R) package developed by Leslie De Koninck, K.U. Leuven as part of a thesis with supervisor Bart Demoen and daily advisor Tom Schrijvers, and distributed with SWI-Prolog.

This CLP(R) system is a port of the CLP(Q,R) system of Sicstus Prolog and YAP by Christian Holzbaur: Holzbaur C.: OFAI clp(q,r) Manual, Edition 1.3.3, Austrian Research Institute for Artificial Intelligence, Vienna, TR-95-09, 1995, http://www.ai.univie.ac.at/cgi-bin/tr-online?number+95-09 This port only contains the part concerning real arithmetics. This manual is roughly based on the manual of the above mentioned CLP(QR) implementation.

Please note that the ‘`clpr`’ library is not an `autoload` library and therefore this library must be loaded explicitely before using it:

    :- use_module(library(clpr)).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 12.1 Solver Predicates

The following predicates are provided to work with constraints:

`{+Constraints}`

  Adds the constraints given by Constraints to the constraint store.

`entailed(+Constraint)`

  Succeeds if Constraint is necessarily true within the current constraint store. This means that adding the negation of the constraint to the store results in failure.

`inf(+Expression,-Inf)`

  Computes the infimum of Expression within the current state of the constraint store and returns that infimum in Inf. This predicate does not change the constraint store.

`inf(+Expression,-Sup)`

  Computes the supremum of Expression within the current state of the constraint store and returns that supremum in Sup. This predicate does not change the constraint store.

`min(+Expression)`

  Minimizes Expression within the current constraint store. This is the same as computing the infimum and equation the expression to that infimum.

`max(+Expression)`

  Maximizes Expression within the current constraint store. This is the same as computing the supremum and equating the expression to that supremum.

`bb_inf(+Ints,+Expression,-Inf,-Vertext,+Eps)`

  Computes the infimum of Expression within the current constraint store, with the additional constraint that in that infimum, all variables in Ints have integral values. Vertex will contain the values of Ints in the infimum. Eps denotes how much a value may differ from an integer to be considered an integer. E.g. when Eps = 0.001, then X = 4.999 will be considered as an integer (5 in this case). Eps should be between 0 and 0.5.

`bb_inf(+Ints,+Expression,-Inf)`

  The same as bb_inf/5 but without returning the values of the integers and with an eps of 0.001.

`dump(+Target,+Newvars,-CodedAnswer)`

  Returns the constraints on Target in the list CodedAnswer where all variables of Target have veen replaced by NewVars. This operation does not change the constraint store. E.g. in

      dump([X,Y,Z],[x,y,z],Cons)

  Cons will contain the constraints on X, Y and Z where these variables have been replaced by atoms `x`, `y` and `z`.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 12.2 Syntax of the predicate arguments

The arguments of the predicates defined in the subsection above are defined in the following table. Failing to meet the syntax rules will result in an exception.

    <Constraints> ---> <Constraint>				\\ single constraint \\
    	      | <Constraint> , <Constraints>		\\ conjunction \\
    	      | <Constraint> ; <Constraints>		\\ disjunction \\

    <Constraint> ---> <Expression> {<} <Expression>		\\ less than \\
    	     | <Expression> {>} <Expression>		\\ greater than \\
    	     | <Expression> {=<} <Expression>	\\ less or equal \\
    	     | {<=}(<Expression>, <Expression>)	\\ less or equal \\
    	     | <Expression> {>=} <Expression>	\\ greater or equal \\
    	     | <Expression> {=\=} <Expression>	\\ not equal \\
    	     | <Expression> =:= <Expression>		\\ equal \\
    	     | <Expression> = <Expression>		\\ equal \\

    <Expression> --->  <Variable>				\\ Prolog variable \\
    	     | <Number>				\\ Prolog number (float, integer) \\
    	     | +<Expression>				\\ unary plus \\
    	     | -<Expression>				\\ unary minus \\
    	     | <Expression> + <Expression>		\\ addition \\
    	     | <Expression> - <Expression>		\\ substraction \\
    	     | <Expression> * <Expression>		\\ multiplication \\
    	     | <Expression> / <Expression>		\\ division \\
    	     | abs(<Expression>)			\\ absolute value \\
    	     | sin(<Expression>)			\\ sine \\
    	     | cos(<Expression>)			\\ cosine \\
    	     | tan(<Expression>)			\\ tangent \\
    	     | exp(<Expression>)			\\ exponent \\
    	     | pow(<Expression>)			\\ exponent \\
    	     | <Expression> {^} <Expression>		\\ exponent \\
    	     | min(<Expression>, <Expression>)	\\ minimum \\
    	     | max(<Expression>, <Expression>)	\\ maximum \\

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 12.3 Use of unification

Instead of using the `{}/1` predicate, you can also use the standard unification mechanism to store constraints. The following code samples are equivalent:

‘`Unification with a variable`’

      {X =:= Y}
      {X = Y}
      X = Y

‘`Unification with a number`’

      {X =:= 5.0}
      {X = 5.0}
      X = 5.0

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 12.4 Non-Linear Constraints

In this version, non-linear constraints do not get solved until certain conditions are satisfied. We call these conditions the isolation axioms. They are given in the following table.

    A = B * C         when B or C is ground	or		 // A = 5 * C or A = B * 4 \\
    	                      A and (B or C) are ground	 // 20 = 5 * C or 20 = B * 4 \\

    A = B / C      when C is ground or			// A = B / 3
    	                      A and B are ground		// 4 = 12 / C

    X = min(Y,Z)     when Y and Z are ground or	// X = min(4,3)
    X = max(Y,Z)         Y and Z are ground		// X = max(4,3)
    X = abs(Y)                Y is ground			// X = abs(-7)

    X = pow(Y,Z)   when X and Y are ground or		// 8 = 2 ^ Z
    X = exp(Y,Z)           X and Z are ground		// 8 = Y ^ 3
    X = Y ^ Z            Y and Z are ground		// X = 2 ^ 3

    X = sin(Y)	    when X is ground or			// 1 = sin(Y)
    X = cos(Y)	               Y is ground			// X = sin(1.5707)
    X = tan(Y)

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 13 CHR: Constraint Handling Rules

This chapter is written by Tom Schrijvers, K.U. Leuven for the hProlog system. Adjusted by Jan Wielemaker to fit the SWI-Prolog documentation infrastructure and remove hProlog specific references.

The CHR system of SWI-Prolog is the K.U.Leuven CHR system. The runtime environment is written by Christian Holzbaur and Tom Schrijvers while the compiler is written by Tom Schrijvers. Both are integrated with SWI-Prolog and licenced under compatible conditions with permission from the authors.

The main reference for SWI-Prolog’s CHR system is:

- T. Schrijvers, and B. Demoen, The K.U.Leuven CHR System: Implementation and Application, First Workshop on Constraint Handling Rules: Selected Contributions (Fruwirth, T. and Meister, M., eds.), pp. 1–5, 2004.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 13.1 Introduction

Constraint Handling Rules (CHR) is a committed-choice bottom-up language embedded in Prolog. It is designed for writing constraint solvers and is particularily useful for providing application-specific constraints. It has been used in many kinds of applications, like scheduling, model checking, abduction, type checking among many others.

CHR has previously been implemented in other Prolog systems (SICStus, Eclipse, Yap), Haskell and Java. This CHR system is based on the compilation scheme and runtime environment of CHR in SICStus.

In this documentation we restrict ourselves to giving a short overview of CHR in general and mainly focus on elements specific to this implementation. For a more thorough review of CHR we refer the reader to [Freuhwirth:98]. More background on CHR can be found at the CHR web site.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 13.2 Syntax and Semantics

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 13.2.1 Syntax

The syntax of CHR rules in hProlog is the following:

    rules --> rule, rules.
    rules --> [].

    rule --> name, actual_rule, pragma, [atom('.')].

    name --> atom, [atom(')'].
    name --> [].

    actual_rule --> simplification_rule.
    actual_rule --> propagation_rule.
    actual_rule --> simpagation_rule.

    simplification_rule --> constraints, [atom('<=>')], guard, body.
    propagation_rule --> constraints, [atom('==>')], guard, body.
    simpagation_rule --> constraints, [atom('\')], constraints, [atom('<=>')],
                         guard, body.

    constraints --> constraint, constraint_id.
    constraints --> constraint, [atom(',')], constraints.

    constraint --> compound_term.

    constraint_id --> [].
    constraint_id --> [atom('#')], variable.

    guard --> [].
    guard --> goal, [atom('|')].

    body --> goal.

    pragma --> [].
    pragma --> [atom('pragma')], actual_pragmas.

    actual_pragmas --> actual_pragma.
    actual_pragmas --> actual_pragma, [atom(',')], actual_pragmas.

    actual_pragma --> [atom('passive(')], variable, [atom(')')].

Additional syntax-related terminology:

- head: the constraints in an `actual_rule` before the arrow (either `<=>` or `==>`)

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 13.2.2 Semantics

In this subsection the operational semantics of CHR in Prolog are presented informally. They do not differ essentially from other CHR systems.

When a constraint is called, it is considered an active constraint and the system will try to apply the rules to it. Rules are tried and executed sequentially in the order they are written.

A rule is conceptually tried for an active constraint in the following way. The active constraint is matched with a constraint in the head of the rule. If more constraints appear in the head they are looked for among the suspended constraints, which are called passive constraints in this context. If the necessary passive constraints can be found and all match with the head of the rule and the guard of the rule succeeds, then the rule is committed and the body of the rule executed. If not all the necessary passive constraint can be found, the matching fails or the guard fails, then the body is not executed and the process of trying and executing simply continues with the following rules. If for a rule, there are multiple constraints in the head, the active constraint will try the rule sequentially multiple times, each time trying to match with another constraint.

This process ends either when the active constraint disappears, i.e. it is removed by some rule, or after the last rule has been processed. In the latter case the active constraint becomes suspended.

A suspended constraint is eligible as a passive constraint for an active constraint. The other way it may interact again with the rules, is when a variable appearing in the constraint becomes bound to either a nonvariable or another variable involved in one or more constraints. In that case the constraint is triggered, i.e. it becomes an active constraint and all the rules are tried.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

#### Rule Types

There are three different kinds of rules, each with their specific semantics:

`simplification`

  The simplification rule removes the constraints in its head and calls its body.

`propagation`

  The propagation rule calls its body exactly once for the constraints in its head.

`simpagation`

  The simpagation rule removes the constraints in its head after the `\` and then calls its body. It is an optimization of simplification rules of the form: \[constraints_1, constraints_2 <=> constraints_1, body \] Namely, in the simpagation form:

      constraints1 \ constraints2 <=> body

  constraints1 constraints are not called in the body.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

#### Rule Names

Naming a rule is optional and has no semantical meaning. It only functions as documentation for the programmer.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

#### Pragmas

The semantics of the pragmas are:

‘`passive(Identifier)`’

  The constraint in the head of a rule Identifier can only act as a passive constraint in that rule.

Additional pragmas may be released in the future.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

#### Options

It is possible to specify options that apply to all the CHR rules in the module. Options are specified with the `option/2` declaration:

                    option(Option,Value).

Available options are:

`check_guard_bindings`

  This option controls whether guards should be checked for illegal variable bindings or not. Possible values for this option are `on`, to enable the checks, and `off`, to disable the checks.

`optimize`

  This is an experimental option controlling the degree of optimization. Possible values are `full`, to enable all available optimizations, and `off` (default), to disable all optimizations. The default is derived from the SWI-Prolog flag `optimise`, where `true` is mapped to `full`. Therefore the commandline option ‘`-O`’ provides full CHR optimization. If optimization is enabled, debugging should be disabled.

`debug`

  This options enables or disables the possibility to debug the CHR code. Possible values are `on` (default) and `off`. See ‘`debugging`’ for more details on debugging. The default is derived from the prolog flag `generate_debug_info`, which is `true` by default. See ‘`-nodebug`’. If debugging is enabled, optimization should be disabled.

`mode`

  This option specifies the mode for a particular constraint. The value is a term with functor and arity equal to that of a constraint. The arguments can be one of `-`, `+` or `?`. The latter is the default. The meaning is the following:

  `-`

    The corresponding argument of every occurrence of the constraint is always unbound.

  `+`

    The corresponding argument of every occurrence of the constraint is always ground.

  `?`

    The corresponding argument of every occurrence of the constraint can have any instantiation, which may change over time. This is the default value.

  The declaration is used by the compiler for various optimizations. Note that it is up to the user the ensure that the mode declaration is correct with respect to the use of the constraint. This option may occur once for each constraint.

`type_declaration`

  This option specifies the argument types for a particular constraint. The value is a term with functor and arity equal to that of a constraint. The arguments can be a user-defined type or one of the built-in types:

  `int`

    The corresponding argument of every occurrence of the constraint is an integer number.

  `float`

    … a floating point number.

  `number`

    … a number.

  `natural`

    … a positive integer.

  `any`

    The corresponding argument of every occurrence of the constraint can have any type. This is the default value.

  Currently, type declarations are only used to improve certain optimizations (guard simplification, occurrence subsumption, …).

`type_definition`

  This option defines a new user-defined type which can be used in type declarations. The value is a term of the form `type(`name`,`list`)`, where name is a term and list is a list of alternatives. Variables can be used to define generic types. Recursive definitions are allowed. Examples are

      type(bool,[true,false]).
      type(complex_number,[float + float * i]).
      type(binary_tree(T),[ leaf(T) | node(binary_tree(T),binary_tree(T)) ]).
      type(list(T),[ [] | [T | list(T)]).

The mode, type_declaration and type_definition options are provided for backward compatibility. The new syntax is described below.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 13.3 CHR in YAP Programs

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 13.3.1 Embedding in Prolog Programs

The CHR constraints defined in a particulary ‘`chr`’ file are associated with a module. The default module is `user`. One should never load different ‘`chr`’ files with the same CHR module name.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 13.3.2 Constraint declaration

Every constraint used in CHR rules has to be declared. There are two ways to do this. The old style is as follows:

    option(type_definition,type(list(T),[ [] , [T|list(T)] ]).
    option(mode,foo(+,?)).
    option(type_declaration,foo(list(int),float)).
    :- constraints foo/2, bar/0.

The new style is as follows:

    :- chr_type list(T) ---> [] ; [T|list(T)].
    :- constraints foo(+list(int),?float), bar.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 13.3.3 Compilation

The SWI-Prolog CHR compiler exploits term_expansion/2 rules to translate the constraint handling rules to plain Prolog. These rules are loaded from the library ‘`chr`’. They are activated if the compiled file has the ‘`chr`’ extension or after finding a declaration of the format below.

    :- constraints ...

It is adviced to define CHR rules in a module file, where the module declaration is immediately followed by including the ‘`chr`’ library as examplified below:

    :- module(zebra, [ zebra/0 ]).
    :- use_module(library(chr)).

    :- constraints ...

Using this style CHR rules can be defined in ordinary Prolog ‘`pl`’ files and the operator definitions required by CHR do not leak into modules where they might cause conflicts.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 13.4 Debugging

The CHR debugging facilities are currently rather limited. Only tracing is currently available. To use the CHR debugging facilities for a CHR file it must be compiled for debugging. Generating debug info is controlled by the CHR option `debug`, whose default is derived from the SWI-Prolog flag `generate_debug_info`. Therefore debug info is provided unless the ‘`-nodebug`’ is used.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 13.4.1 Ports

For CHR constraints the four standard ports are defined:

`call`

  A new constraint is called and becomes active.

`exit`

  An active constraint exits: it has either been inserted in the store after trying all rules or has been removed from the constraint store.

`fail`

  An active constraint fails.

`redo`

  An active constraint starts looking for an alternative solution.

In addition to the above ports, CHR constraints have five additional ports:

`wake`

  A suspended constraint is woken and becomes active.

`insert`

  An active constraint has tried all rules and is suspended in the constraint store.

`remove`

  An active or passive constraint is removed from the constraint store, if it had been inserted.

`try`

  An active constraints tries a rule with possibly some passive constraints. The try port is entered just before committing to the rule.

`apply`

  An active constraints commits to a rule with possibly some passive constraints. The apply port is entered just after committing to the rule.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 13.4.2 Tracing

Tracing is enabled with the chr_trace/0 predicate and disabled with the chr_notrace/0 predicate.

When enabled the tracer will step through the `call`, `exit`, `fail`, `wake` and `apply` ports, accepting debug commands, and simply write out the other ports.

The following debug commans are currently supported:

            CHR debug options:

                    <cr>    creep           c       creep
    		s	skip
    		g	ancestors
                    n       nodebug
    		b	break
                    a       abort
                    f       fail
                    ?       help            h       help

Their meaning is:

`creep`

  Step to the next port.

`skip`

  Skip to exit port of this call or wake port.

`ancestors`

  Print list of ancestor call and wake ports.

`nodebug`

  Disable the tracer.

`break`

  Enter a recursive Prolog toplevel. See break/0.

`abort`

  Exit to the toplevel. See abort/0.

`fail`

  Insert failure in execution.

`help`

  Print the above available debug options.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 13.4.3 CHR Debugging Predicates

The ‘`chr`’ module contains several predicates that allow inspecting and printing the content of the constraint store.

`chr_trace/0`

  Activate the CHR tracer. By default the CHR tracer is activated and deactivated automatically by the Prolog predicates trace/0 and notrace/0.

`chr_notrace/0`

  De-activate the CHR tracer. By default the CHR tracer is activated and deactivated automatically by the Prolog predicates trace/0 and notrace/0.

`chr_leash/0`

  Define the set of CHR ports on which the CHR tracer asks for user intervention (i.e. stops). Spec is either a list of ports or a predefined ‘alias’. Defined aliases are: `full` to stop at all ports, `none` or `off` to never stop, and `default` to stop at the `call`, `exit`, `fail`, `wake` and `apply` ports. See also leash/1.

`chr_show_store(+Mod)`

  Prints all suspended constraints of module Mod to the standard output. This predicate is automatically called by the SWI-Prolog toplevel at the end of each query for every CHR module currently loaded. The prolog-flag `chr_toplevel_show_store` controls whether the toplevel shows the constraint stores. The value `true` enables it. Any other value disables it.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 13.5 Examples

Here are two example constraint solvers written in CHR.

- The program below defines a solver with one constraint, `leq/2`, which is a less-than-or-equal constraint.

      :- module(leq,[cycle/3, leq/2]).
      :- use_module(library(chr)).

      :- constraints leq/2.
      reflexivity   leq(X,X) <=> true.
      antisymmetry  leq(X,Y), leq(Y,X) <=> X = Y.
      idempotence   leq(X,Y) \ leq(X,Y) <=> true.
      transitivity  leq(X,Y), leq(Y,Z) ==> leq(X,Z).

      cycle(X,Y,Z):-
              leq(X,Y),
              leq(Y,Z),
              leq(Z,X).

- The program below implements a simple finite domain constraint solver.

      :- module(dom,[dom/2]).
      :- use_module(library(chr)).

      :- constraints dom/2.

      dom(X,[]) <=> fail.
      dom(X,[Y]) <=> X = Y.
      dom(X,L1), dom(X,L2) <=> intersection(L1,L2,L3), dom(X,L3).

      intersection([],_,[]).
      intersection([H|T],L2,[H|L3]) :-
              member(H,L2), !,
              intersection(T,L2,L3).
      intersection([_|T],L2,L3) :-
              intersection(T,L2,L3).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 13.6 Compatibility with SICStus CHR

There are small differences between CHR in SWI-Prolog and newer YAPs and SICStus and older versions of YAP. Besides differences in available options and pragmas, the following differences should be noted:

`[The handler/1 declaration]`

  In SICStus every CHR module requires a `handler/1` declaration declaring a unique handler name. This declaration is valid syntax in SWI-Prolog, but will have no effect. A warning will be given during compilation.

`[The rules/1 declaration]`

  In SICStus, for every CHR module it is possible to only enable a subset of the available rules through the `rules/1` declaration. The declaration is valid syntax in SWI-Prolog, but has no effect. A warning is given during compilation.

`[Sourcefile naming]`

  SICStus uses a two-step compiler, where ‘`chr`’ files are first translated into ‘`pl`’ files. For SWI-Prolog CHR rules may be defined in a file with any extension.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 13.7 Guidelines

In this section we cover several guidelines on how to use CHR to write constraint solvers and how to do so efficiently.

`[Set semantics]`

  The CHR system allows the presence of identical constraints, i.e. multiple constraints with the same functor, arity and arguments. For most constraint solvers, this is not desirable: it affects efficiency and possibly termination. Hence appropriate simpagation rules should be added of the form:

      {constraint \ constraint <=> true}.

`[Multi-headed rules]`

  Multi-headed rules are executed more efficiently when the constraints share one or more variables.

`[Mode and type declarations]`

  Provide mode and type declarations to get more efficient program execution. Make sure to disable debug (‘`-nodebug`’) and enable optimization (‘`-O`’).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 14 Logtalk

The Logtalk object-oriented extension is available after running its standalone installer by using the `yaplgt` command in POSIX systems or by using the `Logtalk - YAP` shortcut in the Logtalk program group in the Start Menu on Windows systems. For more information please see the URL http://logtalk.org/.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 15 MYDDAS

The MYDDAS database project was developed within a FCT project aiming at the development of a highly efficient deductive database system, based on the coupling of the MySQL relational database system with the Yap Prolog system. MYDDAS was later expanded to support the ODBC interface.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.1 Requirements and Installation Guide

Next, we describe how to usen of the YAP with the MYDDAS System. The use of this system is entirely depend of the MySQL development libraries or the ODBC development libraries. At least one of the this development libraries must be installed on the computer system, otherwise MYDDAS will not compile. The MySQL development libraries from MySQL 3.23 an above are know to work. We recommend the usage of MySQL versusODBC, but it is possible to have both options installed

At the same time, without any problem. The MYDDAS system automatically controls the two options. Currently, MYDDAS is know to compile without problems in Linux. The usage of this system on Windows has not been tested yet. MYDDAS must be enabled at configure time. This can be done with the following options:

`--enable-myddas`

  This option will detect which development libraries are installed on the computer system, MySQL, ODBC or both, and will compile the Yap system with the support for which libraries it detects;

`--enable-myddas-stats`

  This option is only available in MySQL. It includes code to get statistics from the MYDDAS system;

`--enable-top-level`

  This option is only available in MySQL. It enables the option to interact with the MySQL server in two different ways. As if we were on the MySQL Client Shell, and as if we were using Datalog.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.2 MYDDAS Architecture

The system includes four main blocks that are put together through the MYDDAS interface: the Yap Prolog compiler, the MySQL database system, an ODBC layer and a Prolog to SQL compiler. Current effort is put on the MySQL interface rather than on the ODBC interface. If you want to use the full power of the MYDDAS interface we recommend you to use a MySQL database. Other databases, such as Oracle, PostGres or Microsoft SQL Server, can be interfaced through the ODBC layer, but with limited performance and features support.

The main structure of the MYDDAS interface is simple. Prolog queries involving database goals are translated to SQL using the Prolog to SQL compiler; then the SQL expression is sent to the database system, which returns the set of tuples satisfying the query; and finally those tuples are made available to the Prolog engine as terms. For recursive queries involving database goals, the YapTab tabling engine provides the necessary support for an efficient evaluation of such queries.

An important aspect of the MYDDAS interface is that for the programmer the use of predicates which are defined in database relations is completely transparent. An example of this transparent support is the Prolog cut operator, which has exactly the same behaviour from predicates defined in the Prolog program source code, or from predicates defined in database as relations.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.3 Loading MYDDAS

Begin by starting YAP and loading the library `use_module(library(myddas))`. This library already includes the Prolog to SQL Compiler described in [2] and [1]. In MYDDAS this compiler has been extended to support further constructs which allow a more efficient SQL translation.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.4 Connecting to and disconnecting from a Database Server

`db open(+,+,+,+,+).`
`db open(+,+,+,+).`
`db close(+).`
`db_close.`

Assuming the MySQL server is running and we have an account, we can login to MySQL by invoking `db_open/5` as one of the following:

    ?- db_open(mysql,Connection,Host/Database,User,Password).
    ?- db_open(mysql,Connection,Host/Database/Port,User,Password).
    ?- db_open(mysql,Connection,Host/Database/UnixSocket,User,Password).
    ?- db_open(mysql,Connection,Host/Database/Port/UnixSocket,User,Password).

If the login is successful, there will be a response of `yes`. For instance:

    ?- db_open(mysql,con1,localhost/guest_db,guest,'').

uses the MySQL native interface, selected by the first argument, to open a connection identified by the `con1` atom, to an instance of a MySQL server running on host `localhost`, using database guest `db` and user `guest` with empty `password`. To disconnect from the `con1` connection we use:

    ?- db_close(con1).

Alternatively, we can use `db_open/4` and `db_close/0,` without an argument to identify the connection. In this case the default connection is used, with atom `myddas`. Thus using

    ?- db_open(mysql,localhost/guest_db,guest,'').
    ?- db_close.

or

    ?- db_open(mysql,myddas,localhost/guest_db,guest,'').
    ?- db_close(myddas).

is exactly the same.

MYDDAS also supports ODBC. To connect to a database using an ODBC driver you must have configured on your system a ODBC DSN. If so, the `db_open/4` and `db_open/5` have the following mode:

     ?- db_open(odbc,Connection,ODBC_DSN,User,Password).
     ?- db_open(odbc,ODBC_DSN,User,Password).

For instance, if you do `db_open(odbc,odbc_dsn,guest,'')`. it will connect to a database, through ODBC, using the definitions on the `odbc_dsn` DSN configured on the system. The user will be the user `guest` with no password.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.5 Accessing a Relation

`db_import(+Conn,+RelationName,+PredName).`
`db_import(+RelationName,+PredName).`

Assuming you have access permission for the relation you wish to import, you can use `db_import/3` or `db_import/2` as:

    ?- db_import(Conn,RelationName,PredName).
    ?- db_import(RelationName,PredName).

where RelationName, is the name of relation we wish to access, PredName is the name of the predicate we wish to use to access the relation from YAP. Conn, is the connection identifier, which again can be dropped so that the default myddas connection is used. For instance, if we want to access the relation phonebook, using the predicate `phonebook/3` we write:

    ?- db_import(con1,phonebook,phonebook).
    yes
    ?- phonebook(Letter,Name,Number).
    Letter = 'D',
    Name = 'John Doe',
    Number = 123456789 ?
    yes

Backtracking can then be used to retrieve the next row of the relation phonebook. Records with particular field values may be selected in the same way as in Prolog. (In particular, no mode specification for database predicates is required). For instance:

    ?- phonebook(Letter,'John Doe',Letter).
    Letter = 'D',
    Number = 123456789 ?
    yes

generates the query

    SELECT A.Letter , 'John Doe' , A.Number
    FROM 'phonebook' A
    WHERE A.Name = 'John Doe';

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.6 View Level Interface

`db view(+,+,+).`
`db view(+,+).`

If we import a database relation, such as an edge relation representing the edges of a directed graph, through

    ?- db_import('Edge',edge).
    yes

and we then write a query to retrieve all the direct cycles in the graph, such as

    ?- edge(A,B), edge(B,A).
    A = 10,
    B = 20 ?

this is clearly inefficient [3], because of relation-level access. Relation-level access means that a separate SQL query will be generated for every goal in the body of the clause. For the second `edge/2` goal, a SQL query is generated using the variable bindings that result from the first `edge/2` goal execution. If the second `edge/2` goal fails, or if alternative solutions are demanded, backtracking access the next tuple for the first `edge/2` goal and another SQL query will be generated for the second `edge/2` goal. The generation of this large number of queries and the communication overhead with the database system for each of them, makes the relation-level approach inefficient. To solve this problem the view level interface can be used for the definition of rules whose bodies includes only imported database predicates. One can use the view level interface through the predicates `db_view/3` and `db_view/2`:

    ?- db_view(Conn,PredName(Arg_1,...,Arg_n),DbGoal).
    ?- db_view(PredName(Arg_1,...,Arg_n),DbGoal).

All arguments are standard Prolog terms. Arg1 through Argn define the attributes to be retrieved from the database, while DbGoal defines the selection restrictions and join conditions. Conn is the connection identifier, which again can be dropped. Calling predicate `PredName/n` will retrieve database tuples using a single SQL query generated for the DbGoal. We next show an example of a view definition for the direct cycles discussed above. Assuming the declaration:

    ?- db_import('Edge',edge).
    yes

we write:

    ?- db_view(direct_cycle(A,B),(edge(A,B), edge(B,A))).
    yes
    ?- direct_cycle(A,B)).
    A = 10,
    B = 20 ?

This call generates the SQL statement:

    SELECT A.attr1 , A.attr2
    FROM Edge A , Edge B
    WHERE B.attr1 = A.attr2 AND B.attr2 = A.attr1;

Backtracking, as in relational level interface, can be used to retrieve the next row of the view. The view interface also supports aggregate function predicates such as `sum`, `avg`, `count`, `min` and `max`. For instance:

    ?- db_view(count(X),(X is count(B, B^edge(10,B)))).

generates the query :

    SELECT COUNT(A.attr2)
    FROM Edge A WHERE A.attr1 = 10;

To know how to use db `view/3`, please refer to Draxler’s Prolog to SQL Compiler Manual.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.7 Accessing Tables in Data Sources Using SQL

`db_sql(+,+,?).`
`db_sql(+,?).`

It is also possible to explicitly send a SQL query to the database server using

    ?- db_sql(Conn,SQL,List).
    ?- db_sql(SQL,List).

where SQL is an arbitrary SQL expression, and List is a list holding the first tuple of result set returned by the server. The result set can also be navigated through backtracking.

Example:

    ?- db_sql('SELECT * FROM phonebook',LA).
    LA = ['D','John Doe',123456789] ?

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.8 Insertion of Rows

`db_assert(+,+).`
`db_assert(+).`

Assuming you have imported the related base table using `db_import/2` or `db_import/3`, you can insert to that table by using `db_assert/2` predicate any given fact.

    ?- db_assert(Conn,Fact).
    ?- db_assert(Fact).

The second argument must be declared with all of its arguments bound to constants. For example assuming `helloWorld` is imported through `db_import/2`:

    ?- db_import('Hello World',helloWorld).
    yes
    ?- db_assert(helloWorld('A' ,'Ana',31)).
    yes

This, would generate the following query

    INSERT INTO helloWorld
    VALUES ('A','Ana',3)

which would insert into the helloWorld, the following row: `A,Ana,31`. If we want to insert `NULL` values into the relation, we call `db_assert/2` with a uninstantiated variable in the data base imported predicate. For example, the following query on the YAP-prolog system:

    ?- db_assert(helloWorld('A',NULL,31)).
    yes

Would insert the row: `A,null value,31` into the relation `Hello World`, assuming that the second row allows null values.

`db insert(+,+,+).`
`db insert(+,+).`

This predicate would create a new database predicate, which will insert any given tuple into the database.

    ?- db_insert(Conn,RelationName,PredName).
    ?- db_insert(RelationName,PredName).

This would create a new predicate with name PredName, that will insert tuples into the relation RelationName. is the connection identifier. For example, if we wanted to insert the new tuple `('A',null,31)` into the relation `Hello World`, we do:

    ?- db_insert('Hello World',helloWorldInsert).
    yes
    ?- helloWorldInsert('A',NULL,31).
    yes

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.9 Types of Attributes

`db_get_attributes_types(+,+,?).`
`db_get_attributes_types(+,?).`

The prototype for this predicate is the following:

    ?- db_get_attributes_types(Conn,RelationName,ListOfFields).
    ?- db_get_attributes_types(RelationName,ListOfFields).

You can use the predicate `db_get_attributes types/2` or `db_get_attributes_types/3`, to know what are the names and attributes types of the fields of a given relation. For example:

    ?- db_get_attributes_types(myddas,'Hello World',LA).
    LA = ['Number',integer,'Name',string,'Letter',string] ?
    yes

where `Hello World` is the name of the relation and `myddas` is the connection identifier.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.10 Number of Fields

`db_number_of_fields(+,?).`
`db_number_of_fields(+,+,?).`

The prototype for this predicate is the following:

     ?- db_number_of_fields(Conn,RelationName,Arity).
     ?- db_number_of_fields(RelationName,Arity).

You can use the predicate `db_number_of_fields/2` or `db_number_of_fields/3` to know what is the arity of a given relation. Example:

    ?- db_number_of_fields(myddas,'Hello World',Arity).
    Arity = 3 ?
    yes

where `Hello World` is the name of the relation and `myddas` is the connection identifier.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.11 Describing a Relation

`db_datalog_describe(+,+).`
`db_datalog_describe(+).`

The db `datalog_describe/2` predicate does not really returns any value. It simply prints to the screen the result of the MySQL describe command, the same way as `DESCRIBE` in the MySQL prompt would.

    ?- db_datalog_describe(myddas,'Hello World').
    +----------+----------+------+-----+---------+-------+
    |   Field  |  Type    | Null | Key | Default | Extra |
    +----------+----------+------+-----+---------+-------+
    +  Number  | int(11)  | YES  |     |   NULL  |       |
    +  Name    | char(10) | YES  |     |   NULL  |       |
    +  Letter  | char(1)  | YES  |     |   NULL  |       |
    +----------+----------+------+-----+---------+-------+
    yes

`db_describe(+,+).`
`db_describe(+).`

The `db_describe/3` predicate does the same action as `db_datalog_describe/2` predicate but with one major difference. The results are returned by backtracking. For example, the last query:

     ?- db_describe(myddas,'Hello World',Term).
    Term = tableInfo('Number',int(11),'YES','',null(0),'') ? ;
    Term = tableInfo('Name',char(10),'YES','',null(1),'' ? ;
    Term = tableInfo('Letter',char(1),'YES','',null(2),'') ? ;
    no

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.12 Enumeration Relations

`db_datalog_show_tables(+).`
`db_datalog_show_tables`

If we need to know what relations exists in a given MySQL Schema, we can use the `db_datalog_show_tables/1` predicate. As `db_datalog_describe/2`, it does not returns any value, but instead prints to the screen the result of the `SHOW TABLES` command, the same way as it would be in the MySQL prompt.

    ?- db_datalog_show_tables(myddas).
    +-----------------+
    | Tables_in_guest |
    +-----------------+
    |   Hello World   |
    +-----------------+
    yes

`db_show_tables(+, ?).`
`db_show_tables(?)`

The `db_show_tables/2` predicate does the same action as `db_show_tables/1` predicate but with one major difference. The results are returned by backtracking. For example, given the last query:

    ?- db_show_tables(myddas,Table).
    Table = table('Hello World') ? ;
    no

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.13 The MYDDAS MySQL Top Level

`db_top_level(+,+,+,+,+).`
`db_top_level(+,+,+,+).`

Through MYDDAS is also possible to access the MySQL Database Server, in the same wthe mysql client. In this mode, is possible to query the SQL server by just using the standard SQL language. This mode is exactly the same as different from the standard mysql client. We can use this mode, by invoking the db top level/5. as one of the following:

    ?- db_top_level(mysql,Connection,Host/Database,User,Password).
    ?- db_top_level(mysql,Connection,Host/Database/Port,User,Password).
    ?- db_top_level(mysql,Connection,Host/Database/UnixSocket,User,Password).
    ?- db_top_level(mysql,Connection,Host/Database/Port/UnixSocket,User,Password).

Usage is similar as the one described for the `db_open/5` predicate discussed above. If the login is successful, automatically the prompt of the mysql client will be used. For example:

     ?- db_top_level(mysql,con1,localhost/guest_db,guest,'').

opens a connection identified by the `con1` atom, to an instance of a MySQL server running on host `localhost`, using database guest `db` and user `guest` with empty password. After this is possible to use MYDDAS as the mysql client.

      ?- db_top_level(mysql,con1,localhost/guest_db,guest,'').
    Reading table information for completion of table and column names
    You can turn off this feature to get a quicker startup with -A

    Welcome to the MySQL monitor.
    Commands end with ; or \g.

    Your MySQL connection id is 4468 to server version: 4.0.20
    Type 'help;' or '\h' for help.
    Type '\c' to clear the buffer.
    mysql> exit
    Bye
    yes
    ?-

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 15.14 Other MYDDAS Properties

`db_verbose(+).`
`db_top_level(+,+,+,+).`

When we ask a question to YAP, using a predicate asserted by `db_import/3`, or by `db_view/3`, this will generate a SQL `QUERY`. If we want to see that query, we must to this at a given point in our session on YAP.

    ?- db_verbose(1).
    yes
    ?-

If we want to disable this feature, we must call the `db_verbose/1` predicate with the value 0.

`db_module(?).`

When we create a new database predicate, by using `db_import/3`, `db_view/3` or `db_insert/3`, that predicate will be asserted by default on the `user` module. If we want to change this value, we can use the `db_module/1` predicate to do so.

    ?- db_module(lists).
    yes
    ?-

By executing this predicate, all of the predicates asserted by the predicates enumerated earlier will created in the lists module. If we want to put back the value on default, we can manually put the value user. Example:

    ?- db_module(user).
    yes
    ?-

We can also see in what module the predicates are being asserted by doing:

    ?- db_module(X).
    X=user
    yes
     ?-

`db_my_result_set(?).`

The MySQL C API permits two modes for transferring the data generated by a query to the client, in our case YAP. The first mode, and the default mode used by the MYDDAS-MySQL, is to store the result. This mode copies all the information generated to the client side.

    ?- db_my_result_set(X).
    X=store_result
    yes

The other mode that we can use is use result. This one uses the result set created directly from the server. If we want to use this mode, he simply do

     ?- db_my_result_set(use_result).
    yes

After this command, all of the database predicates will use use result by default. We can change this by doing again `db_my_result_set(store_result)`.

`db_my_sql_mode(+Conn,?SQL_Mode).`
`db_my_sql_mode(?SQL_Mode).`

The MySQL server allows the user to change the SQL mode. This can be very useful for debugging proposes. For example, if we want MySQL server not to ignore the INSERT statement warnings and instead of taking action, report an error, we could use the following SQL mode.

      ?-db_my_sql_mode(traditional). yes

You can see the available SQL Modes at the MySQL homepage at http://www.mysql.org.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 16 Threads

YAP implements a SWI-Prolog compatible multithreading library. Like in SWI-Prolog, Prolog threads have their own stacks and only share the Prolog heap: predicates, records, flags and other global non-backtrackable data. The package is based on the POSIX thread standard (Butenhof:1997:PPT) used on most popular systems except for MS-Windows.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 16.1 Creating and Destroying Prolog Threads

`thread_create(:Goal, -Id, +Options)`

  Create a new Prolog thread (and underlying C-thread) and start it by executing Goal. If the thread is created successfully, the thread-identifier of the created thread is unified to Id. Options is a list of options. Currently defined options are:

  `stack`

    Set the limit in K-Bytes to which the Prolog stacks of this thread may grow. If omitted, the limit of the calling thread is used. See also the commandline `-S` option.

  `trail`

    Set the limit in K-Bytes to which the trail stack of this thread may grow. If omitted, the limit of the calling thread is used. See also the commandline option `-T`.

  `alias`

    Associate an alias-name with the thread. This named may be used to refer to the thread and remains valid until the thread is joined (see `thread_join/2`).

  `at_exit`

    Define an exit hook for the thread. This hook is called when the thread terminates, no matter its exit status.

  `detached`

    If `false` (default), the thread can be waited for using `thread_join/2`. `thread_join/2` must be called on this thread to reclaim the all resources associated to the thread. If `true`, the system will reclaim all associated resources automatically after the thread finishes. Please note that thread identifiers are freed for reuse after a detached thread finishes or a normal thread has been joined. See also `thread_join/2` and `thread_detach/1`.

  The Goal argument is copied to the new Prolog engine. This implies further instantiation of this term in either thread does not have consequences for the other thread: Prolog threads do not share data from their stacks.

`thread_create(:Goal, -Id)`

  Create a new Prolog thread using default options. See `thread_create/3`.

`thread_create(:Goal)`

  Create a new Prolog detached thread using default options. See `thread_create/3`.

`thread_self(-Id)`

  Get the Prolog thread identifier of the running thread. If the thread has an alias, the alias-name is returned.

`thread_join(+Id, -Status)`

  Wait for the termination of thread with given Id. Then unify the result-status of the thread with Status. After this call, Id becomes invalid and all resources associated with the thread are reclaimed. Note that threads with the attribute `detached` `true` cannot be joined. See also `current_thread/2`.

  A thread that has been completed without `thread_join/2` being called on it is partly reclaimed: the Prolog stacks are released and the C-thread is destroyed. A small data-structure representing the exit-status of the thread is retained until `thread_join/2` is called on the thread. Defined values for Status are:

  `true`

    The goal has been proven successfully.

  `false`

    The goal has failed.

  `exception(Term)`

    The thread is terminated on an exception. See `print_message/2` to turn system exceptions into readable messages.

  `exited(Term)`

    The thread is terminated on `thread_exit/1` using the argument Term.

`thread_detach(+Id)`

  Switch thread into detached-state (see `detached` option at `thread_create/3` at runtime. Id is the identifier of the thread placed in detached state.

  One of the possible applications is to simplify debugging. Threads that are created as `detached` leave no traces if they crash. For not-detached threads the status can be inspected using `current_thread/2`. Threads nobody is waiting for may be created normally and detach themselves just before completion. This way they leave no traces on normal completion and their reason for failure can be inspected.

`thread_yield`

  Voluntarily relinquish the processor.

`thread_exit(+Term)`

  Terminates the thread immediately, leaving `exited(Term)` as result-state for `thread_join/2`. If the thread has the attribute `detached` `true` it terminates, but its exit status cannot be retrieved using `thread_join/2` making the value of Term irrelevant. The Prolog stacks and C-thread are reclaimed.

`thread_at_exit(:Term)`

  Run Goal just before releasing the thread resources. This is to be compared to `at_halt/1`, but only for the current thread. These hooks are ran regardless of why the execution of the thread has been completed. As these hooks are run, the return-code is already available through `thread_property/2` using the result of `thread_self/1` as thread-identifier. If you want to guarantee the execution of an exit hook no matter how the thread terminates (the thread can be aborted before reaching the `thread_at_exit/1` call), consider using instead the `at_exit/1` option of `thread_create/3`.

`thread_setconcurrency(+Old, -New)`

  Determine the concurrency of the process, which is defined as the maximum number of concurrently active threads. ‘Active’ here means they are using CPU time. This option is provided if the thread-implementation provides `pthread_setconcurrency()`. Solaris is a typical example of this family. On other systems this predicate unifies Old to 0 (zero) and succeeds silently.

`thread_sleep(+Time)`

  Make current thread sleep for Time seconds. Time may be an integer or a floating point number. When time is zero or a negative value the call succeeds and returns immediately. This call should not be used if alarms are also being used.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 16.2 Monitoring Threads

Normal multi-threaded applications should not need these the predicates from this section because almost any usage of these predicates is unsafe. For example checking the existence of a thread before signalling it is of no use as it may vanish between the two calls. Catching exceptions using `catch/3` is the only safe way to deal with thread-existence errors.

These predicates are provided for diagnosis and monitoring tasks.

`thread_property(?Id, ?Property)`

  Enumerates the properties of the specified thread. Calling `thread_property/2` does not influence any thread. See also `thread_join/2`. For threads that have an alias-name, this name can be used in Id instead of the numerical thread identifier. Property is one of:

  `status(Status)`

    The thread status of a thread (see below).

  `alias(Alias)`

    The thread alias, if it exists.

  `at_exit(AtExit)`

    The thread exit hook, if defined (not available if the thread is already terminated).

  `detached(Boolean)`

    The detached state of the thread.

  `stack(Size)`

    The thread stack data-area size.

  `trail(Size)`

    The thread trail data-area size.

  `system(Size)`

    The thread system data-area size.

`current_thread(+Id, -Status)`

  Enumerates identifiers and status of all currently known threads. Calling `current_thread/2` does not influence any thread. See also `thread_join/2`. For threads that have an alias-name, this name is returned in Id instead of the numerical thread identifier. Status is one of:

  `running`

    The thread is running. This is the initial status of a thread. Please note that threads waiting for something are considered running too.

  `false`

    The Goal of the thread has been completed and failed.

  `true`

    The Goal of the thread has been completed and succeeded.

  `exited(Term)`

    The Goal of the thread has been terminated using `thread_exit/1` with Term as argument. If the underlying native thread has exited (using pthread_exit()) Term is unbound.

  `exception(Term)`

    The Goal of the thread has been terminated due to an uncaught exception (see `throw/1` and `catch/3`).

`thread_statistics(+Id, +Key, -Value)`

  Obtains statistical information on thread Id as `statistics/2` does in single-threaded applications. This call returns all keys of `statistics/2`, although only information statistics about the stacks and CPU time yield different values for each thread.

`mutex_statistics`

  Print usage statistics on internal mutexes and mutexes associated with dynamic predicates. For each mutex two numbers are printed: the number of times the mutex was acquired and the number of collisions: the number times the calling thread has to wait for the mutex. The collision-count is not available on Windows as this would break portability to Windows-95/98/ME or significantly harm performance. Generally collision count is close to zero on single-CPU hardware.

`threads`

  Prints a table of current threads and their status.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 16.3 Thread communication

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 16.3.1 Message Queues

Prolog threads can exchange data using dynamic predicates, database records, and other globally shared data. These provide no suitable means to wait for data or a condition as they can only be checked in an expensive polling loop. Message queues provide a means for threads to wait for data or conditions without using the CPU.

Each thread has a message-queue attached to it that is identified by the thread. Additional queues are created using `message_queue_create/2`.

`thread_send_message(+Term)`

  Places Term in the message-queue of the thread running the goal. Any term can be placed in a message queue, but note that the term is copied to the receiving thread and variable-bindings are thus lost. This call returns immediately.

`thread_send_message(+QueueOrThreadId, +Term)`

  Place Term in the given queue or default queue of the indicated thread (which can even be the message queue of itself (see `thread_self/1`). Any term can be placed in a message queue, but note that the term is copied to the receiving thread and variable-bindings are thus lost. This call returns immediately.

  If more than one thread is waiting for messages on the given queue and at least one of these is waiting with a partially instantiated Term, the waiting threads are all sent a wakeup signal, starting a rush for the available messages in the queue. This behaviour can seriously harm performance with many threads waiting on the same queue as all-but-the-winner perform a useless scan of the queue. If there is only one waiting thread or all waiting threads wait with an unbound variable an arbitrary thread is restarted to scan the queue.

`thread_get_message(?Term)`

  Examines the thread message-queue and if necessary blocks execution until a term that unifies to Term arrives in the queue. After a term from the queue has been unified unified to Term, the term is deleted from the queue and this predicate returns.

  Please note that not-unifying messages remain in the queue. After the following has been executed, thread 1 has the term `gnu` in its queue and continues execution using A is `gnat`.

         <thread 1>
         thread_get_message(a(A)),

         <thread 2>
         thread_send_message(b(gnu)),
         thread_send_message(a(gnat)),

  See also `thread_peek_message/1`.

`message_queue_create(?Queue)`

  If Queue is an atom, create a named queue. To avoid ambiguity on `thread_send_message/2`, the name of a queue may not be in use as a thread-name. If Queue is unbound an anonymous queue is created and Queue is unified to its identifier.

`message_queue_destroy(+Queue)`

  Destroy a message queue created with `message_queue_create/1`. It is not allows to destroy the queue of a thread. Neither is it allowed to destroy a queue other threads are waiting for or, for anonymous message queues, may try to wait for later.

`thread_get_message(+Queue, ?Term)`

  As `thread_get_message/1`, operating on a given queue. It is allowed to peek into another thread’s message queue, an operation that can be used to check whether a thread has swallowed a message sent to it.

`thread_peek_message(?Term)`

  Examines the thread message-queue and compares the queued terms with Term until one unifies or the end of the queue has been reached. In the first case the call succeeds (possibly instantiating Term. If no term from the queue unifies this call fails.

`thread_peek_message(+Queue, ?Term)`

  As `thread_peek_message/1`, operating on a given queue. It is allowed to peek into another thread’s message queue, an operation that can be used to check whether a thread has swallowed a message sent to it.

Explicit message queues are designed with the worker-pool model in mind, where multiple threads wait on a single queue and pick up the first goal to execute. Below is a simple implementation where the workers execute arbitrary Prolog goals. Note that this example provides no means to tell when all work is done. This must be realised using additional synchronisation.

    %	create_workers(+Id, +N)
    %
    %	Create a pool with given Id and number of workers.

    create_workers(Id, N) :-
    	message_queue_create(Id),
    	forall(between(1, N, _),
    	       thread_create(do_work(Id), _, [])).

    do_work(Id) :-
    	repeat,
    	  thread_get_message(Id, Goal),
    	  (   catch(Goal, E, print_message(error, E))
    	  ->  true
    	  ;   print_message(error, goal_failed(Goal, worker(Id)))
    	  ),
    	fail.

    %	work(+Id, +Goal)
    %
    %	Post work to be done by the pool

    work(Id, Goal) :-
    	thread_send_message(Id, Goal).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 16.3.2 Signalling Threads

These predicates provide a mechanism to make another thread execute some goal as an interrupt. Signalling threads is safe as these interrupts are only checked at safe points in the virtual machine. Nevertheless, signalling in multi-threaded environments should be handled with care as the receiving thread may hold a mutex (see `with_mutex/2`). Signalling probably only makes sense to start debugging threads and to cancel no-longer-needed threads with `throw/1`, where the receiving thread should be designed carefully do handle exceptions at any point.

`thread_signal(+ThreadId, :Goal)`

  Make thread ThreadId execute Goal at the first opportunity. In the current implementation, this implies at the first pass through the Call-port. The predicate `thread_signal/2` itself places Goal into the signalled-thread’s signal queue and returns immediately.

  Signals (interrupts) do not cooperate well with the world of multi-threading, mainly because the status of mutexes cannot be guaranteed easily. At the call-port, the Prolog virtual machine holds no locks and therefore the asynchronous execution is safe.

  Goal can be any valid Prolog goal, including `throw/1` to make the receiving thread generate an exception and `trace/0` to start tracing the receiving thread.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 16.3.3 Threads and Dynamic Predicates

Besides queues threads can share and exchange data using dynamic predicates. The multi-threaded version knows about two types of dynamic predicates. By default, a predicate declared dynamic (see `dynamic/1`) is shared by all threads. Each thread may assert, retract and run the dynamic predicate. Synchronisation inside Prolog guarantees the consistency of the predicate. Updates are logical: visible clauses are not affected by assert/retract after a query started on the predicate. In many cases primitive from thread synchronisation should be used to ensure application invariants on the predicate are maintained.

Besides shared predicates, dynamic predicates can be declared with the `thread_local/1` directive. Such predicates share their attributes, but the clause-list is different in each thread.

`thread_local(+Functor/Arity)`

  related to the dynamic/1 directive. It tells the system that the predicate may be modified using `assert/1`, `retract/1`, etc, during execution of the program. Unlike normal shared dynamic data however each thread has its own clause-list for the predicate. As a thread starts, this clause list is empty. If there are still clauses as the thread terminates these are automatically reclaimed by the system. The `thread_local` property implies the property `dynamic`.

  Thread-local dynamic predicates are intended for maintaining thread-specific state or intermediate results of a computation.

  It is not recommended to put clauses for a thread-local predicate into a file as in the example below as the clause is only visible from the thread that loaded the source-file. All other threads start with an empty clause-list.

      :- thread_local
      	foo/1.

      foo(gnat).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 16.4 Thread Synchronisation

All internal Prolog operations are thread-safe. This implies two Prolog threads can operate on the same dynamic predicate without corrupting the consistency of the predicate. This section deals with user-level mutexes (called monitors in ADA or critical-sections by Microsoft). A mutex is a MUTual EXclusive device, which implies at most one thread can hold a mutex.

Mutexes are used to realise related updates to the Prolog database. With ‘related’, we refer to the situation where a ‘transaction’ implies two or more changes to the Prolog database. For example, we have a predicate `address/2`, representing the address of a person and we want to change the address by retracting the old and asserting the new address. Between these two operations the database is invalid: this person has either no address or two addresses, depending on the assert/retract order.

Here is how to realise a correct update:

    :- initialization
    	mutex_create(addressbook).

    change_address(Id, Address) :-
    	mutex_lock(addressbook),
    	retractall(address(Id, _)),
    	asserta(address(Id, Address)),
    	mutex_unlock(addressbook).

`mutex_create(?MutexId)`

  Create a mutex. if MutexId is an atom, a named mutex is created. If it is a variable, an anonymous mutex reference is returned. There is no limit to the number of mutexes that can be created.

`mutex_destroy(+MutexId)`

  Destroy a mutex. After this call, MutexId becomes invalid and further references yield an `existence_error` exception.

`with_mutex(+MutexId, :Goal)`

  Execute Goal while holding MutexId. If Goal leaves choicepoints, these are destroyed (as in `once/1`). The mutex is unlocked regardless of whether Goal succeeds, fails or raises an exception. An exception thrown by Goal is re-thrown after the mutex has been successfully unlocked. See also `mutex_create/2`.

  Although described in the thread-section, this predicate is also available in the single-threaded version, where it behaves simply as `once/1`.

`mutex_lock(+MutexId)`

  Lock the mutex. Prolog mutexes are recursive mutexes: they can be locked multiple times by the same thread. Only after unlocking it as many times as it is locked, the mutex becomes available for locking by other threads. If another thread has locked the mutex the calling thread is suspended until to mutex is unlocked.

  If MutexId is an atom, and there is no current mutex with that name, the mutex is created automatically using `mutex_create/1`. This implies named mutexes need not be declared explicitly.

  Please note that locking and unlocking mutexes should be paired carefully. Especially make sure to unlock mutexes even if the protected code fails or raises an exception. For most common cases use `with_mutex/2`, which provides a safer way for handling Prolog-level mutexes.

`mutex_trylock(+MutexId)`

  As mutex_lock/1, but if the mutex is held by another thread, this predicates fails immediately.

`mutex_unlock(+MutexId)`

  Unlock the mutex. This can only be called if the mutex is held by the calling thread. If this is not the case, a `permission_error` exception is raised.

`mutex_unlock_all`

  Unlock all mutexes held by the current thread. This call is especially useful to handle thread-termination using `abort/0` or exceptions. See also `thread_signal/2`.

`current_mutex(?MutexId, ?ThreadId, ?Count)`

  Enumerates all existing mutexes. If the mutex is held by some thread, ThreadId is unified with the identifier of the holding thread and Count with the recursive count of the mutex. Otherwise, ThreadId is `[]` and Count is 0.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 17 Parallelism

There has been a sizeable amount of work on an or-parallel implementation for YAP, called YAPOr. Most of this work has been performed by Ricardo Rocha. In this system parallelism is exploited implicitly by running several alternatives in or-parallel. This option can be enabled from the `configure` script or by checking the system’s `Makefile`.

YAPOr is still a very experimental system, going through rapid development. The following restrictions are of note:

- YAPOr currently only supports the Linux/X86 and SPARC/Solaris platforms. Porting to other Unix-like platforms should be straightforward.
- YAPOr does not support parallel updates to the data-base.
- YAPOr does not support opening or closing of streams during parallel execution.
- Garbage collection and stack shifting are not supported in YAPOr.
- Built-ins that cause side-effects can only be executed when left-most in the search-tree. There are no primitives to provide asynchronous or cavalier execution of these built-ins, as in Aurora or Muse.
- YAP does not support voluntary suspension of work.

We expect that some of these restrictions will be removed in future releases.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 18 Tabling

YAPTab is the tabling engine that extends YAP’s execution model to support tabled evaluation for definite programs. YAPTab was implemented by Ricardo Rocha and its implementation is largely based on the ground-breaking design of the XSB Prolog system, which implements the SLG-WAM. Tables are implemented using tries and YAPTab supports the dynamic intermixing of batched scheduling and local scheduling at the subgoal level. Currently, the following restrictions are of note:

- YAPTab does not handle tabled predicates with loops through negation (undefined behaviour).
- YAPTab does not handle tabled predicates with cuts (undefined behaviour).
- YAPTab does not support coroutining (configure error).
- YAPTab does not support tabling dynamic predicates (permission error).

To experiment with YAPTab use `--enable-tabling` in the configure script or add `-DTABLING` to `YAP_EXTRAS` in the system’s `Makefile`. We next describe the set of built-ins predicates designed to interact with YAPTab and control tabled execution:

`table +P`

  Declares predicate P (or a list of predicates P1,...,Pn or [P1,...,Pn]) as a tabled predicate. P must be written in the form name/arity. Examples:

      :- table son/3.
      :- table father/2.
      :- table mother/2.

  or

      :- table son/3, father/2, mother/2.

  or

      :- table [son/3, father/2, mother/2].

`is_tabled(+P)`

  Succeeds if the predicate P (or a list of predicates P1,...,Pn or [P1,...,Pn]), of the form name/arity, is a tabled predicate.

`tabling_mode(+P,?Mode)`

  Sets or reads the default tabling mode for a tabled predicate P (or a list of predicates P1,...,Pn or [P1,...,Pn]). The list of Mode options includes:

  `batched`

    Defines that, by default, batched scheduling is the scheduling strategy to be used to evaluated calls to predicate P.

  `local`

    Defines that, by default, local scheduling is the scheduling strategy to be used to evaluated calls to predicate P.

  `exec_answers`

    Defines that, by default, when a call to predicate P is already evaluated (completed), answers are obtained by executing compiled WAM-like code directly from the trie data structure. This reduces the loading time when backtracking, but the order in which answers are obtained is undefined.

  `load_answers`

    Defines that, by default, when a call to predicate P is already evaluated (completed), answers are obtained (as a consumer) by loading them from the trie data structure. This guarantees that answers are obtained in the same order as they were found. Somewhat less efficient but creates less choice-points.

  The default tabling mode for a new tabled predicate is `batched` and `exec_answers`. To set the tabling mode for all predicates at once you can use the `yap_flag/2` predicate as described next.

`yap_flag(tabling_mode,?Mode)`

  Sets or reads the tabling mode for all tabled predicates. The list of Mode options includes:

  `default`

    Defines that (i) all calls to tabled predicates are evaluated using the predicate default mode, and that (ii) answers for all completed calls are obtained by using the predicate default mode.

  `batched`

    Defines that all calls to tabled predicates are evaluated using batched scheduling. This option ignores the default tabling mode of each predicate.

  `local`

    Defines that all calls to tabled predicates are evaluated using local scheduling. This option ignores the default tabling mode of each predicate.

  `exec_answers`

    Defines that answers for all completed calls are obtained by executing compiled WAM-like code directly from the trie data structure. This option ignores the default tabling mode of each predicate.

  `load_answers`

    Defines that answers for all completed calls are obtained by loading them from the trie data structure. This option ignores the default tabling mode of each predicate.

`abolish_table(+P)`

  Removes all the entries from the table space for predicate P (or a list of predicates P1,...,Pn or [P1,...,Pn]). The predicate remains as a tabled predicate.

`abolish_all_tables/0`

  Removes all the entries from the table space for all tabled predicates. The predicates remain as tabled predicates.

`show_table(+P)`

  Prints table contents (subgoals and answers) for predicate P (or a list of predicates P1,...,Pn or [P1,...,Pn]).

`table_statistics(+P)`

  Prints table statistics (subgoals and answers) for predicate P (or a list of predicates P1,...,Pn or [P1,...,Pn]).

`tabling_statistics/0`

  Prints statistics on space used by all tables.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 19 Tracing at Low Level

It is possible to follow the flow at abstract machine level if YAP is compiled with the flag `LOW_LEVEL_TRACER`. Note that this option is of most interest to implementers, as it quickly generates an huge amount of information.

Low level tracing can be toggled from an interrupt handler by using the option `T`. There are also two built-ins that activate and deactivate low level tracing:

`start_low_level_trace`

  Begin display of messages at procedure entry and retry.

`stop_low_level_trace`

  Stop display of messages at procedure entry and retry.

Note that this compile-time option will slow down execution.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 20 Profiling the Abstract Machine

Implementors may be interested in detecting on which abstract machine instructions are executed by a program. The `ANALYST` flag can give WAM level information. Note that this option slows down execution very substantially, and is only of interest to developers of the system internals, or to system debuggers.

`reset_op_counters`

  Reinitialize all counters.

`show_op_counters(+A)`

  Display the current value for the counters, using label A. The label must be an atom.

`show_ops_by_group(+A)`

  Display the current value for the counters, organized by groups, using label A. The label must be an atom.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 21 Debugging

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 21.1 Debugging Predicates

The following predicates are available to control the debugging of programs:

`debug`

  Switches the debugger on.

`debugging`

  Outputs status information about the debugger which includes the leash mode and the existing spy-points, when the debugger is on.

`nodebug`

  Switches the debugger off.

`spy +P`

  Sets spy-points on all the predicates represented by P. P can either be a single specification or a list of specifications. Each one must be of the form Name/Arity or Name. In the last case all predicates with the name Name will be spied. As in C-Prolog, system predicates and predicates written in C, cannot be spied.

`nospy +P`

  Removes spy-points from all predicates specified by P. The possible forms for P are the same as in `spy P`.

`nospyall`

  Removes all existing spy-points.

`notrace`

  Switches off the debugger and stops tracing.

`leash(+M)`

  Sets leashing mode to M. The mode can be specified as:

  `full`

    prompt on Call, Exit, Redo and Fail

  `tight`

    prompt on Call, Redo and Fail

  `half`

    prompt on Call and Redo

  `loose`

    prompt on Call

  `off`

    never prompt

  `none`

    never prompt, same as `off`

  The initial leashing mode is `full`.

  The user may also specify directly the debugger ports where he wants to be prompted. If the argument for leash is a number N, each of lower four bits of the number is used to control prompting at one the ports of the box model. The debugger will prompt according to the following conditions:

  - if `N/\ 1 =\= 0` prompt on fail
  - if `N/\ 2 =\= 0` prompt on redo
  - if `N/\ 4 =\= 0` prompt on exit
  - if `N/\ 8 =\= 0` prompt on call

  Therefore, `leash(15)` is equivalent to `leash(full)` and `leash(0)` is equivalent to `leash(off)`.

  Another way of using `leash` is to give it a list with the names of the ports where the debugger should stop. For example, `leash([call,exit,redo,fail])` is the same as `leash(full)` or `leash(15)` and `leash([fail])` might be used instead of `leash(1)`.

`spy_write(+Stream,Term)`

  If defined by the user, this predicate will be used to print goals by the debugger instead of `write/2`.

`trace`

  Switches on the debugger and starts tracing.

`notrace`

  Ends tracing and exits the debugger. This is the same as `nodebug/0`.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 21.2 Interacting with the debugger

Debugging with YAP is similar to debugging with C-Prolog. Both systems include a procedural debugger, based on Byrd’s four port model. In this model, execution is seen at the procedure level: each activation of a procedure is seen as a box with control flowing into and out of that box.

In the four port model control is caught at four key points: before entering the procedure, after exiting the procedure (meaning successful evaluation of all queries activated by the procedure), after backtracking but before trying new alternative to the procedure and after failing the procedure. Each one of these points is named a port:

               *--------------------------------------*
       Call    |                                      |    Exit
    ---------> +  descendant(X,Y) :- offspring(X,Y).  + --------->
               |                                      |
               |  descendant(X,Z) :-                  |
    <--------- +     offspring(X,Y), descendant(Y,Z). + <---------
       Fail    |                                      |    Redo
               *--------------------------------------*

`Call`

  The call port is activated before initial invocation of procedure. Afterwards, execution will try to match the goal with the head of existing clauses for the procedure.

`Exit`

  This port is activated if the procedure succeeds. Control will now leave the procedure and return to its ancestor.

`Redo`

  if the goal, or goals, activated after the call port fail then backtracking will eventually return control to this procedure through the redo port.

`Fail`

  If all clauses for this predicate fail, then the invocation fails, and control will try to redo the ancestor of this invocation.

To start debugging, the user will either call `trace` or spy the relevant procedures, entering debug mode, and start execution of the program. When finding the first spy-point, YAP’s debugger will take control and show a message of the form:

    * (1)  call:  quicksort([1,2,3],_38) ?

The debugger message will be shown while creeping, or at spy-points, and it includes four or five fields:

- The first three characters are used to point out special states of the debugger. If the port is exit and the first character is ’?’, the current call is non-deterministic, that is, it still has alternatives to be tried. If the second character is a `*`, execution is at a spy-point. If the third character is a `>`, execution has returned either from a skip, a fail or a redo command.
- The second field is the activation number, and uniquely identifies the activation. The number will start from 1 and will be incremented for each activation found by the debugger.
- In the third field, the debugger shows the active port.
- The fourth field is the goal. The goal is written by `write_term/3` on the standard error stream, using the options given by `debugger_print_options`.

If the active port is leashed, the debugger will prompt the user with a `?`, and wait for a command. A debugger command is just a character, followed by a return. By default, only the call and redo entries are leashed, but the `leash/1` predicate can be used in order to make the debugger stop where needed.

There are several commands available, but the user only needs to remember the help command, which is `h`. This command shows all the available options, which are:

`c - creep`

  this command makes YAP continue execution and stop at the next leashed port.

`return - creep`

  the same as c

`l - leap`

  YAP will execute until it meets a port for a spied predicate; this mode keeps all computation history for debugging purposes, so it is more expensive than standard execution. Use `k` or `z` for fast execution.

`k - quasi-leap`

  similar to leap but faster since the computation history is not kept; useful when leap becomes too slow.

`z - zip`

  same as `k`

`s - skip`

  YAP will continue execution without showing any messages until returning to the current activation. Spy-points will be ignored in this mode. Note that this command keeps all debugging history, use `t` for fast execution. This command is meaningless, and therefore illegal, in the fail and exit ports.

`t - fast-skip`

  similar to skip but faster since computation history is not kept; useful if skip becomes slow.

`f [GoalId] - fail`

  If given no argument, forces YAP to fail the goal, skipping the fail port and backtracking to the parent. If `f` receives a goal number as the argument, the command fails all the way to the goal. If goal GoalId has completed execution, YAP fails until meeting the first active ancestor.

`r [GoalId] - retry`

  This command forces YAP to jump back call to the port. Note that any side effects of the goal cannot be undone. This command is not available at the call port. If `f` receives a goal number as the argument, the command retries goal GoalId instead. If goal GoalId has completed execution, YAP fails until meeting the first active ancestor.

`a - abort`

  execution will be aborted, and the interpreter will return to the top-level. YAP disactivates debug mode, but spypoints are not removed.

`n - nodebug`

  stop debugging and continue execution. The command will not clear active spy-points.

`e - exit`

  leave YAP.

`h - help`

  show the debugger commands.

`! Query`

  execute a query. YAP will not show the result of the query.

`b - break`

  break active execution and launch a break level. This is the same as `! break`.

`+ - spy this goal`

  start spying the active goal. The same as `! spy G` where G is the active goal.

`- - nospy this goal`

  stop spying the active goal. The same as `! nospy G` where G is the active goal.

`p - print`

  shows the active goal using print/1

`d - display`

  shows the active goal using display/1

`<Depth - debugger write depth`

  sets the maximum write depth, both for composite terms and lists, that will be used by the debugger. For more information about `write_depth/2` (see section Controlling Input/Output).

`< - full term`

  resets to the default of ten the debugger’s maximum write depth. For more information about `write_depth/2` (see section Controlling Input/Output).

`A - alternatives`

  show the list of backtrack points in the current execution.

`g [N]`

  show the list of ancestors in the current debugging environment. If it receives N, show the first N ancestors.

The debugging information, when fast-skip `quasi-leap` is used, will be lost.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 22 Efficiency Considerations

We next discuss several issues on trying to make Prolog programs run fast in YAP. We assume two different programming styles:

• Execution of deterministic programs often

  boils down to a recursive loop of the form:

      loop(Env) :-
              do_something(Env,NewEnv),
              loop(NewEnv).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 22.1 Deterministic Programs

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 22.2 Non-Deterministic Programs

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 22.3 Data-Base Operations

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 22.4 Indexing

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 22.5 Profiling

The indexation mechanism restricts the set of clauses to be tried in a procedure by using information about the status of the instantiated arguments of the goal. These arguments are then used as a key, selecting a restricted set of a clauses from all the clauses forming the procedure.

As an example, the two clauses for concatenate:

    concatenate([],L,L).
    concatenate([H|T],A,[H|NT]) :- concatenate(T,A,NT).

If the first argument for the goal is a list, then only the second clause is of interest. If the first argument is the nil atom, the system needs to look only for the first clause. The indexation generates instructions that test the value of the first argument, and then proceed to a selected clause, or group of clauses.

Note that if the first argument was a free variable, then both clauses should be tried. In general, indexation will not be useful if the first argument is a free variable.

When activating a predicate, a Prolog system needs to store state information. This information, stored in a structure known as choice point or fail point, is necessary when backtracking to other clauses for the predicate. The operations of creating and using a choice point are very expensive, both in the terms of space used and time spent. Creating a choice point is not necessary if there is only a clause for the predicate as there are no clauses to backtrack to. With indexation, this situation is extended: in the example, if the first argument was the atom nil, then only one clause would really be of interest, and it is pointless to create a choice point. This feature is even more useful if the first argument is a list: without indexation, execution would try the first clause, creating a choice point. The clause would fail, the choice point would then be used to restore the previous state of the computation and the second clause would be tried. The code generated by the indexation mechanism would behave much more efficiently: it would test the first argument and see whether it is a list, and then proceed directly to the second clause.

An important side effect concerns the use of "cut". In the above example, some programmers would use a "cut" in the first clause just to inform the system that the predicate is not backtrackable and force the removal the choice point just created. As a result, less space is needed but with a great loss in expressive power: the "cut" would prevent some uses of the procedure, like generating lists through backtracking. Of course, with indexation the "cut" becomes useless: the choice point is not even created.

Indexation is also very important for predicates with a large number of clauses that are used like tables:

    logician(aristoteles,greek).
    logician(frege,german).
    logician(russel,english).
    logician(godel,german).
    logician(whitehead,english).

An interpreter like C-Prolog, trying to answer the query:

    ?- logician(godel,X).

would blindly follow the standard Prolog strategy, trying first the first clause, then the second, the third and finally finding the relevant clause. Also, as there are some more clauses after the important one, a choice point has to be created, even if we know the next clauses will certainly fail. A "cut" would be needed to prevent some possible uses for the procedure, like generating all logicians. In this situation, the indexing mechanism generates instructions that implement a search table. In this table, the value of the first argument would be used as a key for fast search of possibly matching clauses. For the query of the last example, the result of the search would be just the fourth clause, and again there would be no need for a choice point.

If the first argument is a complex term, indexation will select clauses just by testing its main functor. However, there is an important exception: if the first argument of a clause is a list, the algorithm also uses the list’s head if not a variable. For instance, with the following clauses,

    rules([],B,B).
    rules([n(N)|T],I,O) :- rules_for_noun(N,I,N), rules(T,N,O).
    rules([v(V)|T],I,O) :- rules_for_verb(V,I,N), rules(T,N,O).
    rules([q(Q)|T],I,O) :- rules_for_qualifier(Q,I,N), rules(T,N,O).

if the first argument of the goal is a list, its head will be tested, and only the clauses matching it will be tried during execution.

Some advice on how to take a good advantage of this mechanism:

- Try to make the first argument an input argument.
- Try to keep together all clauses whose first argument is not a variable, that will decrease the number of tests since the other clauses are always tried.
- Try to avoid predicates having a lot of clauses with the same key. For instance, the procedure:

    type(n(mary),person).
    type(n(john), person).
    type(n(chair),object).
    type(v(eat),active).
    type(v(rest),passive).

becomes more efficient with:

    type(n(N),T) :- type_of_noun(N,T).
    type(v(V),T) :- type_of_verb(V,T).

    type_of_noun(mary,person).
    type_of_noun(john,person).
    type_of_noun(chair,object).

    type_of_verb(eat,active).
    type_of_verb(rest,passive).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 23 C Language interface to YAP

YAP provides the user with the necessary facilities for writing predicates in a language other than Prolog. Since, under Unix systems, most language implementations are link-able to C, we will describe here only the YAP interface to the C language.

Before describing in full detail how to interface to C code, we will examine a brief example.

Assume the user requires a predicate `my_process_id(Id)` which succeeds when Id unifies with the number of the process under which YAP is running.

In this case we will create a `my_process.c` file containing the C-code described below.

    #include "YAP/YAPInterface.h"

    static int my_process_id(void)
    {
         YAP_Term pid = YAP_MkIntTerm(getpid());
         YAP_Term out = YAP_ARG1;
         return(YAP_Unify(out,pid));
    }

    void init_my_predicates()
    {
         YAP_UserCPredicate("my_process_id",my_process_id,1);
    }

The commands to compile the above file depend on the operating system. Under Linux (i386 and Alpha) you should use:

          gcc -c -shared -fPIC my_process.c
          ld -shared -o my_process.so my_process.o

Under WIN32 in a MINGW/CYGWIN environment, using the standard installation path you should use:

          gcc -mno-cygwin  -I "c:/Yap/include" -c my_process.c
          gcc -mno-cygwin "c:/Yap/bin/yap.dll" --shared -o my_process.dll my_process.o

Under WIN32 in a pure CYGWIN environment, using the standard installation path, you should use:

          gcc -I/usr/local -c my_process.c
          gcc -shared -o my_process.dll my_process.o /usr/local/bin/yap.dll

Under Solaris2 it is sufficient to use:

          gcc  -fPIC -c my_process.c

Under SunOS it is sufficient to use:

          gcc -c my_process.c

Under Digital Unix you need to create a `so` file. Use:

          gcc tst.c -c -fpic
          ld my_process.o -o my_process.so -shared -expect_unresolved '*'

and replace my `process.so` for my `process.o` in the remainder of the example. And could be loaded, under YAP, by executing the following Prolog goal

          load_foreign_files(['my_process'],[],init_my_predicates).

Note that since YAP4.3.3 you should not give the suffix for object files. YAP will deduce the correct suffix from the operating system it is running under.

After loading that file the following Prolog goal

           my_process_id(N)

would unify N with the number of the process under which YAP is running.

Having presented a full example, we will now examine in more detail the contents of the C source code file presented above.

The include statement is used to make available to the C source code the macros for the handling of Prolog terms and also some YAP public definitions.

The function `my_process_id` is the implementation, in C, of the desired predicate. Note that it returns an integer denoting the success of failure of the goal and also that it has no arguments even though the predicate being defined has one. In fact the arguments of a Prolog predicate written in C are accessed through macros, defined in the include file, with names YAP_ARG1, YAP_ARG2, ..., YAP_ARG16 or with YAP_A(N) where N is the argument number (starting with 1). In the present case the function uses just one local variable of type `YAP_Term`, the type used for holding YAP terms, where the integer returned by the standard unix function `getpid()` is stored as an integer term (the conversion is done by `YAP_MkIntTerm(Int))`. Then it calls the pre-defined routine `YAP_Unify(YAP_Term, YAP_Term)` which in turn returns an integer denoting success or failure of the unification.

The role of the procedure `init_my_predicates` is to make known to YAP, by calling `YAP_UserCPredicate`, the predicates being defined in the file. This is in fact why, in the example above, `init_my_predicates` was passed as the third argument to `load_foreign_files`.

The rest of this appendix describes exhaustively how to interface C to YAP.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.1 Terms

This section provides information about the primitives available to the C programmer for manipulating Prolog terms.

Several C typedefs are included in the header file `yap/YAPInterface.h` to describe, in a portable way, the C representation of Prolog terms. The user should write is programs using this macros to ensure portability of code across different versions of YAP.

The more important typedef is YAP_Term which is used to denote the type of a Prolog term.

Terms, from a point of view of the C-programmer, can be classified as follows

uninstantiated variables
instantiated variables
integers
floating-point numbers
database references
atoms
pairs (lists)
compound terms

The primitive

         YAP_Bool YAP_IsVarTerm(YAP_Term t)

returns true iff its argument is an uninstantiated variable. Conversely the primitive

          YAP_Bool YAP_NonVarTerm(YAP_Term t)

returns true iff its argument is not a variable.

The user can create a new uninstantiated variable using the primitive

          YAP_Term  YAP_MkVarTerm()

The following primitives can be used to discriminate among the different types of non-variable terms:

          YAP_Bool YAP_IsIntTerm(YAP_Term t)
          YAP_Bool YAP_IsFloatTerm(YAP_Term t)
          YAP_Bool YAP_IsDbRefTerm(YAP_Term t)
          YAP_Bool YAP_IsAtomTerm(YAP_Term t)
          YAP_Bool YAP_IsPairTerm(YAP_Term t)
          YAP_Bool YAP_IsApplTerm(YAP_Term t)

Next, we mention the primitives that allow one to destruct and construct terms. All the above primitives ensure that their result is dereferenced, i.e. that it is not a pointer to another term.

The following primitives are provided for creating an integer term from an integer and to access the value of an integer term.

          YAP_Term YAP_MkIntTerm(YAP_Int  i)
          YAP_Int  YAP_IntOfTerm(YAP_Term t)

where `YAP_Int` is a typedef for the C integer type appropriate for the machine or compiler in question (normally a long integer). The size of the allowed integers is implementation dependent but is always greater or equal to 24 bits: usually 32 bits on 32 bit machines, and 64 on 64 bit machines.

The two following primitives play a similar role for floating-point terms

          YAP_Term YAP_MkFloatTerm(YAP_flt double)
          YAP_flt  YAP_FloatOfTerm(YAP_Term t)

where `flt` is a typedef for the appropriate C floating point type, nowadays a `double`

The following primitives are provided for verifying whether a term is a big int, creating a term from a big integer and to access the value of a big int from a term.

          YAP_Bool YAP_IsBigNumTerm(YAP_Term t)
          YAP_Term YAP_MkBigNumTerm(void  *b)
          void *YAP_BigNumOfTerm(YAP_Term t, void *b)

YAP must support bignum for the configuration you are using (check the YAP configuration and setup). For now, YAP only supports the GNU GMP library, and `void *` will be a cast for `mpz_t`. Notice that `YAP_BigNumOfTerm` requires the number to be already initialised. As an example, we show how to print a bignum:

    static int
    p_print_bignum(void)
    {
      mpz_t mz;
      if (!YAP_IsBigNumTerm(YAP_ARG1))
        return FALSE;

      mpz_init(mz);
      YAP_BigNumOfTerm(YAP_ARG1, mz);
      gmp_printf("Shows up as %Zd\n", mz);
      mpz_clear(mz);
      return TRUE;
    }

Currently, no primitives are supplied to users for manipulating data base references.

A special typedef `YAP_Atom` is provided to describe Prolog atoms (symbolic constants). The two following primitives can be used to manipulate atom terms

          YAP_Term YAP_MkAtomTerm(YAP_Atom at)
          YAP_Atom YAP_AtomOfTerm(YAP_Term t)

The following primitives are available for associating atoms with their names

          YAP_Atom  YAP_LookupAtom(char * s)
          YAP_Atom  YAP_FullLookupAtom(char * s)
          char     *YAP_AtomName(YAP_Atom t)

The function `YAP_LookupAtom` looks up an atom in the standard hash table. The function `YAP_FullLookupAtom` will also search if the atom had been "hidden": this is useful for system maintenance from C code. The functor `YAP_AtomName` returns a pointer to the string for the atom.

The following primitives handle constructing atoms from strings with wide characters, and vice-versa:

          YAP_Atom  YAP_LookupWideAtom(wchar_t * s)
          wchar_t  *YAP_WideAtomName(YAP_Atom t)

The following primitive tells whether an atom needs wide atoms in its representation:

          int  YAP_IsWideAtom(YAP_Atom t)

The following primitive can be used to obtain the size of an atom in a representation-independent way:

          int      YAP_AtomNameLength(YAP_Atom t)

The next routines give users some control over the atom garbage collector. They allow the user to guarantee that an atom is not to be garbage collected (this is important if the atom is hold externally to the Prolog engine, allow it to be collected, and call a hook on garbage collection:

          int  YAP_AtomGetHold(YAP_Atom at)
          int  YAP_AtomReleaseHold(YAP_Atom at)
          int  YAP_AGCRegisterHook(YAP_AGC_hook f)
          YAP_Term  YAP_TailOfTerm(YAP_Term t)

A pair is a Prolog term which consists of a tuple of two Prolog terms designated as the head and the tail of the term. Pairs are most often used to build lists. The following primitives can be used to manipulate pairs:

          YAP_Term  YAP_MkPairTerm(YAP_Term Head, YAP_Term Tail)
          YAP_Term  YAP_MkNewPairTerm(void)
          YAP_Term  YAP_HeadOfTerm(YAP_Term t)
          YAP_Term  YAP_TailOfTerm(YAP_Term t)

One can construct a new pair from two terms, or one can just build a pair whose head and tail are new unbound variables. Finally, one can fetch the head or the tail.

A compound term consists of a functor and a sequence of terms with length equal to the arity of the functor. A functor, described in C by the typedef `Functor`, consists of an atom and of an integer. The following primitives were designed to manipulate compound terms and functors

          YAP_Term     YAP_MkApplTerm(YAP_Functor f, unsigned long int n, YAP_Term[] args)
          YAP_Term     YAP_MkNewApplTerm(YAP_Functor f, int n)
          YAP_Term     YAP_ArgOfTerm(int argno,YAP_Term ts)
          YAP_Term    *YAP_ArgsOfTerm(YAP_Term ts)
          YAP_Functor  YAP_FunctorOfTerm(YAP_Term ts)

The `YAP_MkApplTerm` function constructs a new term, with functor f (of arity n), and using an array args of n terms with n equal to the arity of the functor. `YAP_MkNewApplTerm` builds up a compound term whose arguments are unbound variables. `YAP_ArgOfTerm` gives an argument to a compound term. `argno` should be greater or equal to 1 and less or equal to the arity of the functor. `YAP_ArgsOfTerm` returns a pointer to an array of arguments.

YAP allows one to manipulate the functors of compound term. The function `YAP_FunctorOfTerm` allows one to obtain a variable of type `YAP_Functor` with the functor to a term. The following functions then allow one to construct functors, and to obtain their name and arity.

          YAP_Functor  YAP_MkFunctor(YAP_Atom a,unsigned long int arity)
          YAP_Atom     YAP_NameOfFunctor(YAP_Functor f)
          YAP_Int      YAP_ArityOfFunctor(YAP_Functor f)

Note that the functor is essentially a pair formed by an atom, and arity.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.2 Unification

YAP provides a single routine to attempt the unification of two Prolog terms. The routine may succeed or fail:

          Int      YAP_Unify(YAP_Term a, YAP_Term b)

The routine attempts to unify the terms a and b returning `TRUE` if the unification succeeds and `FALSE` otherwise.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.3 Strings

The YAP C-interface now includes an utility routine to copy a string represented as a list of a character codes to a previously allocated buffer

          int YAP_StringToBuffer(YAP_Term String, char *buf, unsigned int bufsize)

The routine copies the list of character codes String to a previously allocated buffer buf. The string including a terminating null character must fit in bufsize characters, otherwise the routine will simply fail. The StringToBuffer routine fails and generates an exception if String is not a valid string.

The C-interface also includes utility routines to do the reverse, that is, to copy a from a buffer to a list of character codes, to a difference list, or to a list of character atoms. The routines work either on strings of characters or strings of wide characters:

          YAP_Term YAP_BufferToString(char *buf)
          YAP_Term YAP_NBufferToString(char *buf, size_t len)
          YAP_Term YAP_WideBufferToString(wchar_t *buf)
          YAP_Term YAP_NWideBufferToString(wchar_t *buf, size_t len)
          YAP_Term YAP_BufferToAtomList(char *buf)
          YAP_Term YAP_NBufferToAtomList(char *buf, size_t len)
          YAP_Term YAP_WideBufferToAtomList(wchar_t *buf)
          YAP_Term YAP_NWideBufferToAtomList(wchar_t *buf, size_t len)

Users are advised to use the N version of the routines. Otherwise, the user-provided string must include a terminating null character.

The C-interface function calls the parser on a sequence of characters stored at buf and returns the resulting term.

          YAP_Term YAP_ReadBuffer(char *buf,YAP_Term *error)

The user-provided string must include a terminating null character. Syntax errors will cause returning `FALSE` and binding error to a Prolog term.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.4 Memory Allocation

The next routine can be used to ask space from the Prolog data-base:

          void      *YAP_AllocSpaceFromYAP(int size)

The routine returns a pointer to a buffer allocated from the code area, or `NULL` if sufficient space was not available.

The space allocated with `YAP_AllocSpaceFromYAP` can be released back to YAP by using:

          void      YAP_FreeSpaceFromYAP(void *buf)

The routine releases a buffer allocated from the code area. The system may crash if `buf` is not a valid pointer to a buffer in the code area.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.5 Controlling YAP Streams from `C`

The C-Interface also provides the C-application with a measure of control over the YAP Input/Output system. The first routine allows one to find a file number given a current stream:

          int      YAP_StreamToFileNo(YAP_Term stream)

This function gives the file descriptor for a currently available stream. Note that null streams and in memory streams do not have corresponding open streams, so the routine will return a negative. Moreover, YAP will not be aware of any direct operations on this stream, so information on, say, current stream position, may become stale.

A second routine that is sometimes useful is:

          void      YAP_CloseAllOpenStreams(void)

This routine closes the YAP Input/Output system except for the first three streams, that are always associated with the three standard Unix streams. It is most useful if you are doing `fork()`.

Last, one may sometimes need to flush all streams:

          void      YAP_CloseAllOpenStreams(void)

It is also useful before you do a `fork()`, or otherwise you may have trouble with unflushed output.

The next routine allows a currently open file to become a stream. The routine receives as arguments a file descriptor, the true file name as a string, an atom with the user name, and a set of flags:

          void      YAP_OpenStream(void *FD, char *name, YAP_Term t, int flags)

The available flags are `YAP_INPUT_STREAM`, `YAP_OUTPUT_STREAM`, `YAP_APPEND_STREAM`, `YAP_PIPE_STREAM`, `YAP_TTY_STREAM`, `YAP_POPEN_STREAM`, `YAP_BINARY_STREAM`, and `YAP_SEEKABLE_STREAM`. By default, the stream is supposed to be at position 0. The argument name gives the name by which YAP should know the new stream.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.6 Utility Functions in `C`

The C-Interface provides the C-application with a a number of utility functions that are useful.

The first provides a way to insert a term into the data-base

          void      *YAP_Record(YAP_Term t)

This function returns a pointer to a copy of the term in the database (or to `NULL` if the operation fails.

The next functions provides a way to recover the term from the data-base:

          YAP_Term      YAP_Recorded(void *handle)

Notice that the semantics are the same as for `recorded/3`: this function creates a new copy of the term in the stack, with fresh variables. The function returns `0L` if it cannot create a new term.

Last, the next function allows one to recover space:

          int      YAP_Erase(void *handle)

Notice that any accesses using handle after this operation may lead to a crash.

The following functions are often required to compare terms.

The first function succeeds if two terms are actually the same term, as `==/2`:

          int      YAP_ExactlyEqual(YAP_Term t1, YAP_Term t2)

The second function succeeds if two terms are variant terms, and returns 0 otherwise, as `=/=2`:

          int      YAP_Variant(YAP_Term t1, YAP_Term t2)

The second function computes a hash function for a term, as in `term_hash/4`.

         YAP_Int    YAP_TermHash(YAP_Term t, YAP_Int range, YAP_Int depth, int  ignore_variables));

The first three arguments follow `term_has/4`. The last argument indicates what to do if we find a variable: if `0` fail, otherwise ignore the variable.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.7 From `C` back to Prolog

There are several ways to call Prolog code from C-code. By default, the `YAP_RunGoal()` should be used for this task. It assumes the engine has been initialised before:

      YAP_RunGoal(YAP_Term Goal)

Execute query Goal and return 1 if the query succeeds, and 0 otherwise. The predicate returns 0 if failure, otherwise it will return an YAP_Term.

Quite often, one wants to run a query once. In this case you should use Goal:

      YAP_RunGoalOnce(YAP_Term Goal)

The `YAP_RunGoal()` function makes sure to recover stack space at the end of execution.

Prolog terms are pointers: a problem users often find is that the term Goal may actually be moved around during the execution of `YAP_RunGoal()`, due to garbage collection or stack shifting. If this is possible, Goal will become invalid after executing `YAP_RunGoal()`. In this case, it is a good idea to save Goal slots, as shown next:

      long sl = YAP_InitSlot(scoreTerm);

      out = YAP_RunGoal(t);
      t = YAP_GetFromSlot(sl);
      YAP_RecoverSlots(1);
      if (out == 0) return FALSE;

Slots are safe houses in the stack, the garbage collector and the stack shifter know about them and make sure they have correct values. In this case, we use a slot to preserve t during the execution of `YAP_RunGoal`. When the execution of t is over we read the (possibly changed) value of t back from the slot sl and tell YAP that the slot sl is not needed and can be given back to the system. The slot functions are as follows:

`YAP_Int YAP_NewSlots(int NumberOfSlots)`

  Allocate NumberOfSlots from the stack and return an handle to the last one. The other handle can be obtained by decrementing the handle.

`YAP_Int YAP_CurrentSlot(void)`

  Return a handle to the system’s default slot.

`YAP_Int YAP_InitSlot(YAP_Term t)`

  Create a new slot, initialise it with t, and return a handle to this slot, that also becomes the current slot.

`YAP_Term *YAP_AddressFromSlot(YAP_Int slot)`

  Return the address of slot slot: please use with care.

`void YAP_PutInSlot(YAP_Int slot, YAP_Term t)`

  Set the contents of slot slot to t.

`int YAP_RecoverSlots(int HowMany)`

  Recover the space for HowMany slots: these will include the current default slot. Fails if no such slots exist.

`YAP_Int YAP_ArgsToSlots(int HowMany)`

  Store the current first HowMany arguments in new slots.

`void YAP_SlotsToArgs(int HowMany, YAP_Int slot)`

  Set the first HowMany arguments to the HowMany slots starting at slot.

The following functions complement YAP_RunGoal:

  Look for the next solution to the current query by forcing YAP to backtrack to the latest goal. Notice that slots allocated since the last `YAP_RunGoal` will become invalid.

``int` YAP_Reset(`void`)`

  Reset execution environment (similar to the `abort/0` built-in). This is useful when you want to start a new query before asking all solutions to the previous query.

``int` YAP_ShutdownGoal(`int backtrack`)`

  Clean up the current goal. If `backtrack` is true, stack space will be recovered and bindings will be undone. In both cases, any slots allocated since the goal was created will become invalid.

``YAP_Bool` YAP_GoalHasException(`YAP_Term *tp`)`

  Check if the last goal generated an exception, and if so copy it to the space pointed to by tp

``void` YAP_ClearExceptions(`void`)`

  Reset any exceptions left over by the system.

The YAP_RunGoal interface is designed to be very robust, but may not be the most efficient when repeated calls to the same goal are made and when there is no interest in processing exception. The YAP_EnterGoal interface should have lower-overhead:

``YAP_PredEntryPtr` YAP_FunctorToPred(`YAP_Functor` f,`

  Return the predicate whose main functor is f.

``YAP_PredEntryPtr` YAP_AtomToPred(`YAP_Atom` at,`

  Return the arity 0 predicate whose name is at.

``YAP_Bool` YAP_EnterGoal(`YAP_PredEntryPtr` pe,`

  `YAP_Term *` array, `YAP_dogoalinfo *` infop) Execute a query for predicate pe. The query is given as an array of terms Array. infop is the address of a goal handle that can be used to backtrack and to recover space. Succeeds if a solution was found.

  Notice that you cannot create new slots if an YAP_EnterGoal goal is open.

``YAP_Bool` YAP_RetryGoal(`YAP_dogoalinfo *` infop)`

  Backtrack to a query created by `YAP_EnterGoal`. The query is given by the handle infop. Returns whether a new solution could be be found.

``YAP_Bool` YAP_LeaveGoal(`YAP_Bool` backtrack,`

  `YAP_dogoalinfo *` infop) Exit a query query created by `YAP_EnterGoal`. If `backtrack` is `TRUE`, variable bindings are undone and Heap space is recovered. Otherwise, only stack space is recovered, ie, `LeaveGoal` executes a cut.

Next, follows an example of how to use `YAP_EnterGoal`:

    void
    runall(YAP_Term g)
    {
        YAP_dogoalinfo goalInfo;
        YAP_Term *goalArgs = YAP_ArraysOfTerm(g);
        YAP_Functor *goalFunctor = YAP_FunctorOfTerm(g);
        YAP_PredEntryPtr goalPred = YAP_FunctorToPred(goalFunctor);

        result = YAP_EnterGoal( goalPred, goalArgs, &goalInfo );
        while (result)
           result = YAP_RetryGoal( &goalInfo );
        YAP_LeaveGoal(TRUE, &goalInfo);
    }

YAP allows calling a new Prolog interpreter from `C`. One way is to first construct a goal `G`, and then it is sufficient to perform:

          YAP_Bool      YAP_CallProlog(YAP_Term G)

the result will be `FALSE`, if the goal failed, or `TRUE`, if the goal succeeded. In this case, the variables in G will store the values they have been unified with. Execution only proceeds until finding the first solution to the goal, but you can call `findall/3` or friends if you need all the solutions.

Notice that during execution, garbage collection or stack shifting may have moved the terms

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.8 Module Manipulation in C

YAP allows one to create a new module from C-code. To create the new code it is sufficient to call:

          YAP_Module      YAP_CreateModule(YAP_Atom ModuleName)

Notice that the new module does not have any predicates associated and that it is not the current module. To find the current module, you can call:

          YAP_Module      YAP_CurrentModule()

Given a module, you may want to obtain the corresponding name. This is possible by using:

          YAP_Term      YAP_ModuleName(YAP_Module mod)

Notice that this function returns a term, and not an atom. You can `YAP_AtomOfTerm` to extract the corresponding Prolog atom.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.9 Miscellaneous C Functions

``void` YAP_Throw(`YAP_Term exception`)`
``void` YAP_AsyncThrow(`YAP_Term exception`)`

  Throw an exception with term exception, just like if you called `throw/2`. The function `YAP_AsyncThrow` is supposed to be used from interrupt handlers.

``int` YAP_SetYAPFlag(`yap_flag_t flag, int value`)`

  This function allows setting some YAP flags from `C` .Currently, only two boolean flags are accepted: `YAPC_ENABLE_GC` and `YAPC_ENABLE_AGC`. The first enables/disables the standard garbage collector, the second does the same for the atom garbage collector.‘

``int` YAP_HaltRegisterHook(`YAP_halt_hook f, void *closure`)`

  Register the function f to be called if YAP is halted. The function is called with two arguments: the exit code of the process (`0` if this cannot be determined on your operating system) and the closure argument closure.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.10 Writing predicates in C

We will distinguish two kinds of predicates:

deterministic predicates which either fail or succeed but are not

  backtrackable, like the one in the introduction;

backtrackable

  predicates which can succeed more than once.

The first kind of predicates should be implemented as a C function with no arguments which should return zero if the predicate fails and a non-zero value otherwise. The predicate should be declared to YAP, in the initialization routine, with a call to

          void YAP_UserCPredicate(char *name, YAP_Bool *fn(), unsigned long int arity);

where name is the name of the predicate, fn is the C function implementing the predicate and arity is its arity.

For the second kind of predicates we need three C functions. The first one is called when the predicate is first activated; the second one is called on backtracking to provide (possibly) other solutions; the last one is called on pruning. Note also that we normally also need to preserve some information to find out the next solution.

In fact the role of the two functions can be better understood from the following Prolog definition

           p :- start.
           p :- repeat,
                    continue.

where `start` and `continue` correspond to the two C functions described above.

As an example we will consider implementing in C a predicate `n100(N)` which, when called with an instantiated argument should succeed if that argument is a numeral less or equal to 100, and, when called with an uninstantiated argument, should provide, by backtracking, all the positive integers less or equal to 100.

To do that we first declare a structure, which can only consist of Prolog terms, containing the information to be preserved on backtracking and a pointer variable to a structure of that type.

    #include "YAPInterface.h"

    static int start_n100(void);
    static int continue_n100(void);

    typedef struct {
        YAP_Term next_solution;  /* the next solution */
       } n100_data_type;

    n100_data_type *n100_data;

We now write the `C` function to handle the first call:

    static int start_n100(void)
    {
          YAP_Term t = YAP_ARG1;
          YAP_PRESERVE_DATA(n100_data,n100_data_type);
          if(YAP_IsVarTerm(t)) {
              n100_data->next_solution = YAP_MkIntTerm(0);
              return continue_n100();
           }
          if(!YAP_IsIntTerm(t) || YAP_IntOfTerm(t)<0 || YAP_IntOfTerm(t)>100) {
              YAP_cut_fail();
          } else {
              YAP_cut_succeed();
          }
    }

The routine starts by getting the dereference value of the argument. The call to `YAP_PRESERVE_DATA` is used to initialize the memory which will hold the information to be preserved across backtracking. The first argument is the variable we shall use, and the second its type. Note that we can only use `YAP_PRESERVE_DATA` once, so often we will want the variable to be a structure. This data is visible to the garbage collector, so it should consist of Prolog terms, as in the example. It is also correct to store pointers to objects external to YAP stacks, as the garbage collector will ignore such references.

If the argument of the predicate is a variable, the routine initializes the structure to be preserved across backtracking with the information required to provide the next solution, and exits by calling `continue_n100` to provide that solution.

If the argument was not a variable, the routine then checks if it was an integer, and if so, if its value is positive and less than 100. In that case it exits, denoting success, with `YAP_cut_succeed`, or otherwise exits with `YAP_cut_fail` denoting failure.

The reason for using for using the functions `YAP_cut_succeed` and `YAP_cut_fail` instead of just returning a non-zero value in the first case, and zero in the second case, is that otherwise, if backtracking occurred later, the routine `continue_n100` would be called to provide additional solutions.

The code required for the second function is

    static int continue_n100(void)
    {
          int n;
          YAP_Term t;
          YAP_Term sol = YAP_ARG1;
          YAP_PRESERVED_DATA(n100_data,n100_data_type);
          n = YAP_IntOfTerm(n100_data->next_solution);
          if( n == 100) {
               t = YAP_MkIntTerm(n);
               YAP_Unify(sol,t);
               YAP_cut_succeed();
            }
           else {
               YAP_Unify(sol,n100_data->next_solution);
               n100_data->next_solution = YAP_MkIntTerm(n+1);
               return(TRUE);
            }
    }

Note that again the macro `YAP_PRESERVED_DATA` is used at the beginning of the function to access the data preserved from the previous solution. Then it checks if the last solution was found and in that case exits with `YAP_cut_succeed` in order to cut any further backtracking. If this is not the last solution then we save the value for the next solution in the data structure and exit normally with 1 denoting success. Note also that in any of the two cases we use the function `YAP_unify` to bind the argument of the call to the value saved in `n100_state->next_solution`.

Note also that the only correct way to signal failure in a backtrackable predicate is to use the `YAP_cut_fail` macro.

Backtrackable predicates should be declared to YAP, in a way similar to what happened with deterministic ones, but using instead a call to

          void YAP_UserBackCutCPredicate(char *name,
                     int *init(), int *cont(), int *cut(),
                     unsigned long int arity, unsigned int sizeof);

where name is a string with the name of the predicate, init, cont, cut are the C functions used to start, continue and when pruning the execution of the predicate, arity is the predicate arity, and sizeof is the size of the data to be preserved in the stack. In this example, we would have something like

    void
    init_n100(void)
    {
      YAP_UserBackCutCPredicate("n100", start_n100, continue_n100, cut_n100, 1, 1);
    }

The argument before last is the predicate’s arity. Notice again the last argument to the call. function argument gives the extra space we want to use for `PRESERVED_DATA`. Space is given in cells, where a cell is the same size as a pointer. The garbage collector has access to this space, hence users should use it either to store terms or to store pointers to objects outside the stacks.

The code for `cut_n100` could be:

    static int cut_n100(void)
    {
      YAP_PRESERVED_DATA_CUT(n100_data,n100_data_type*);

      fprintf("n100 cut with counter %ld\n", YAP_IntOfTerm(n100_data->next_solution));
      return TRUE;
    }

Notice that we have to use `YAP_PRESERVED_DATA_CUT`: this is because the Prolog engine is at a different state during cut.

If no work is required at cut, we can use:

    void
    init_n100(void)
    {
      YAP_UserBackCutCPredicate("n100", start_n100, continue_n100, NULL, 1, 1);
    }

in this case no code is executed at cut time.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.11 Loading Object Files

The primitive predicate

          load_foreign_files(Files,Libs,InitRoutine)

should be used, from inside YAP, to load object files produced by the C compiler. The argument ObjectFiles should be a list of atoms specifying the object files to load, Libs is a list (possibly empty) of libraries to be passed to the unix loader (`ld`) and InitRoutine is the name of the C routine (to be called after the files are loaded) to perform the necessary declarations to YAP of the predicates defined in the files.

YAP will search for ObjectFiles in the current directory first. If it cannot find them it will search for the files using the environment variable `YAPLIBDIR`, if defined, or in the default library.

YAP also supports the SWI-Prolog interface to loading foreign code:

`open_shared_object(+File, -Handle)`

  File is the name of a shared object file (called dynamic load library in MS-Windows). This file is attached to the current process and Handle is unified with a handle to the library. Equivalent to `open_shared_object(File, [], Handle)`. See also load_foreign_library/[1,2].

  On errors, an exception `shared_object`(Action, Message) is raised. Message is the return value from dlerror().

`open_shared_object(+File, -Handle, +Options)`

  As `open_shared_object/2`, but allows for additional flags to be passed. Options is a list of atoms. `now` implies the symbols are resolved immediately rather than lazily (default). `global` implies symbols of the loaded object are visible while loading other shared objects (by default they are local). Note that these flags may not be supported by your operating system. Check the documentation of `dlopen()` or equivalent on your operating system. Unsupported flags are silently ignored.

`close_shared_object(+Handle)`

  Detach the shared object identified by Handle.

`call_shared_object_function(+Handle, +Function)`

  Call the named function in the loaded shared library. The function is called without arguments and the return-value is ignored. In SWI-Prolog, normally this function installs foreign language predicates using calls to `PL_register_foreign()`.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.12 Saving and Restoring

YAP4 currently does not support `save` and `restore` for object code loaded with `load_foreign_files`. We plan to support save and restore in future releases of YAP.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 23.13 Changes to the C-Interface in YAP4

YAP4 includes several changes over the previous `load_foreign_files` interface. These changes were required to support the new binary code formats, such as ELF used in Solaris2 and Linux.

- All Names of YAP objects now start with YAP_. This is designed to avoid clashes with other code. Use `YAPInterface.h` to take advantage of the new interface. `c_interface.h` is still available if you cannot port the code to the new interface.
- Access to elements in the new interface always goes through functions. This includes access to the argument registers, `YAP_ARG1` to `YAP_ARG16`. This change breaks code such as `unify(&ARG1,&t)`, which is nowadays:

      {
         YAP_Unify(ARG1, t);
      }

- `cut_fail()` and `cut_succeed()` are now functions.
- The use of `Deref` is deprecated. All functions that return Prolog terms, including the ones that access arguments, already dereference their arguments.
- Space allocated with PRESERVE_DATA is ignored by garbage collection and stack shifting. As a result, any pointers to a Prolog stack object, including some terms, may be corrupted after garbage collection or stack shifting. Prolog terms should instead be stored as arguments to the backtrackable procedure.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 24 Using YAP as a Library

YAP can be used as a library to be called from other programs. To do so, you must first create the YAP library:

    make library
    make install_library

This will install a file `libyap.a` in LIBDIR and the Prolog headers in INCLUDEDIR. The library contains all the functionality available in YAP, except the foreign function loader and for `YAP`’s startup routines.

To actually use this library you must follow a five step process:

1. You must initialize the YAP environment. A single function, `YAP_FastInit` asks for a contiguous chunk in your memory space, fills it in with the data-base, and sets up YAP’s stacks and execution registers. You can use a saved space from a standard system by calling `save_program/1`.
2. You then have to prepare a query to give to YAP. A query is a Prolog term, and you just have to use the same functions that are available in the C-interface.
3. You can then use `YAP_RunGoal(query)` to actually evaluate your query. The argument is the query term `query`, and the result is 1 if the query succeeded, and 0 if it failed.
4. You can use the term destructor functions to check how arguments were instantiated.
5. If you want extra solutions, you can use `YAP_RestartGoal()` to obtain the next solution.

The next program shows how to use this system. We assume the saved program contains two facts for the procedure `b`:

    #include <stdio.h>
    #include "YAP/YAPInterface.h"

    int
    main(int argc, char *argv[]) {
      if (YAP_FastInit("saved_state") == YAP_BOOT_ERROR)
        exit(1);
      if (YAP_RunGoal(YAP_MkAtomTerm(YAP_LookupAtom("do")))) {
        printf("Success\n");
        while (YAP_RestartGoal())
          printf("Success\n");
      }
      printf("NO\n");
    }

The program first initializes YAP, calls the query for the first time and succeeds, and then backtracks twice. The first time backtracking succeeds, the second it fails and exits.

To compile this program it should be sufficient to do:

    cc -o exem -I../YAP4.3.0 test.c -lYAP -lreadline -lm

You may need to adjust the libraries and library paths depending on the Operating System and your installation of YAP.

Note that YAP4.3.0 provides the first version of the interface. The interface may change and improve in the future.

The following C-functions are available from YAP:

- YAP_CompileClause(`YAP_Term` Clause) Compile the Prolog term Clause and assert it as the last clause for the corresponding procedure.
- `int` YAP_ContinueGoal(`void`) Continue execution from the point where it stopped.
- `void` YAP_Error(`int` ID,`YAP_Term` Cause,`char *` error_description) Generate an YAP System Error with description given by the string error_description. ID is the error ID, if known, or `0`. Cause is the term that caused the crash.
- `void` YAP_Exit(`int` exit_code) Exit YAP immediately. The argument exit_code gives the error code and is supposed to be 0 after successful execution in Unix and Unix-like systems.
- `YAP_Term` YAP_GetValue(`Atom` at) Return the term value associated with the atom at. If no such term exists the function will return the empty list.
- YAP_FastInit(`char *` SavedState) Initialize a copy of YAP from SavedState. The copy is monolithic and currently must be loaded at the same address where it was saved. `YAP_FastInit` is a simpler version of `YAP_Init`.
- YAP_Init(InitInfo) Initialize YAP. The arguments are in a `C` structure of type `YAP_init_args`.

  The fields of InitInfo are `char *` SavedState, `int` HeapSize, `int` StackSize, `int` TrailSize, `int` NumberofWorkers, `int` SchedulerLoop, `int` DelayedReleaseLoad, `int` argc, `char **` argv, `int` ErrorNo, and `char *` ErrorCause. The function returns an integer, which indicates the current status. If the result is `YAP_BOOT_ERROR` booting failed.

  If SavedState is not NULL, try to open and restore the file SavedState. Initially YAP will search in the current directory. If the saved state does not exist in the current directory YAP will use either the default library directory or the directory given by the environment variable `YAPLIBDIR`. Note that currently the saved state must be loaded at the same address where it was saved.

  If HeapSize is different from 0 use HeapSize as the minimum size of the Heap (or code space). If StackSize is different from 0 use HeapSize as the minimum size for the Stacks. If TrailSize is different from 0 use TrailSize as the minimum size for the Trails.

  The NumberofWorkers, NumberofWorkers, and DelayedReleaseLoad are only of interest to the or-parallel system.

  The argument count argc and string of arguments argv arguments are to be passed to user programs as the arguments used to call YAP.

  If booting failed you may consult `ErrorNo` and `ErrorCause` for the cause of the error, or call `YAP_Error(ErrorNo,0L,ErrorCause)` to do default processing.

- `void` YAP_PutValue(`Atom` at, `YAP_Term` value) Associate the term value with the atom at. The term value must be a constant. This functionality is used by YAP as a simple way for controlling and communicating with the Prolog run-time.
- `YAP_Term` YAP_Read(`int (*)(void)` GetC) Parse a Term using the function GetC to input characters.
- `YAP_Term` YAP_Write(`YAP_Term` t) Copy a Term t and all associated constraints. May call the garbage collector and returns `0L` on error (such as no space being available).
- `void` YAP_Write(`YAP_Term` t, `void (*)(int)` PutC, `int` flags) Write a Term t using the function PutC to output characters. The term is written according to a mask of the following flags in the `flag` argument: `YAP_WRITE_QUOTED`, `YAP_WRITE_HANDLE_VARS`, and `YAP_WRITE_IGNORE_OPS`.
- `void` YAP_WriteBuffer(`YAP_Term` t, `char *` buff, `unsigned int` size, `int` flags) Write a YAP_Term t to buffer buff with size size. The term is written according to a mask of the following flags in the `flag` argument: `YAP_WRITE_QUOTED`, `YAP_WRITE_HANDLE_VARS`, and `YAP_WRITE_IGNORE_OPS`.
- `void` YAP_InitConsult(`int` mode, `char *` filename) Enter consult mode on file filename. This mode maintains a few data-structures internally, for instance to know whether a predicate before or not. It is still possible to execute goals in consult mode.

  If mode is `TRUE` the file will be reconsulted, otherwise just consulted. In practice, this function is most useful for bootstrapping Prolog, as otherwise one may call the Prolog predicate `compile/1` or `consult/1` to do compilation.

  Note that it is up to the user to open the file filename. The `YAP_InitConsult` function only uses the file name for internal bookkeeping.

- `void` YAP_EndConsult(`void`) Finish consult mode.

Some observations:

- The system will core dump if you try to load the saved state in a different address from where it was made. This may be a problem if your program uses `mmap`. This problem will be addressed in future versions of YAP.
- Currently, the YAP library will pollute the name space for your program.
- The initial library includes the complete YAP system. In the future we plan to split this library into several smaller libraries (e.g. if you do not want to perform I/O).
- You can generate your own saved states. Look at the `boot.yap` and `init.yap` files.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# 25 Compatibility with Other Prolog systems

YAP has been designed to be as compatible as possible with other Prolog systems, and initially with C-Prolog. More recent work on YAP has included features initially proposed for the Quintus and SICStus Prolog systems.

Developments since `YAP4.1.6` we have striven at making YAP compatible with the ISO-Prolog standard.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 25.1 Compatibility with the C-Prolog interpreter

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 25.1.1 Major Differences between YAP and C-Prolog.

YAP includes several extensions over the original C-Prolog system. Even so, most C-Prolog programs should run under YAP without changes.

The most important difference between YAP and C-Prolog is that, being YAP a compiler, some changes should be made if predicates such as `assert`, `clause` and `retract` are used. First predicates which will change during execution should be declared as `dynamic` by using commands like:

    :- dynamic f/n.

where `f` is the predicate name and n is the arity of the predicate. Note that several such predicates can be declared in a single command:

     :- dynamic f/2, ..., g/1.

Primitive predicates such as `retract` apply only to dynamic predicates. Finally note that not all the C-Prolog primitive predicates are implemented in YAP. They can easily be detected using the `unknown` system predicate provided by YAP.

Last, by default YAP enables character escapes in strings. You can disable the special interpretation for the escape character by using:

    :- yap_flag(character_escapes,off).

or by using:

    :- yap_flag(language,cprolog).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 25.1.2 YAP predicates fully compatible with C-Prolog

These are the Prolog built-ins that are fully compatible in both C-Prolog and YAP:

Jump to: | ! , ; < = > @ [ \ A B C D E F G H I K L N O P R S T V W

| Index Entry |  | Section
! |  |
| !/0 |  | 6.1 Control Predicates
, |  |
| ,/2 |  | 6.1 Control Predicates
; |  |
| ;/2 |  | 6.1 Control Predicates
< |  |
| </2 |  | 6.8 Arithmetic
= |  |
| =../2 |  | 6.4 Predicates on terms
| =:=/2 |  | 6.8 Arithmetic
| =</2 |  | 6.8 Arithmetic
| ==/2 |  | 6.7 Comparing Terms
| =\=/2 |  | 6.8 Arithmetic
> |  |
| >/2 |  | 6.8 Arithmetic
| >=/2 |  | 6.8 Arithmetic
@ |  |
| @</2 |  | 6.7 Comparing Terms
| @</2 |  | 6.7 Comparing Terms
| @>/2 |  | 6.7 Comparing Terms
| @>=/2 |  | 6.7 Comparing Terms
[ |  |
| [-]/1 |  | 4.1 Program loading and updating
| []/1 |  | 4.1 Program loading and updating
\ |  |
| \+/1 |  | 6.1 Control Predicates
| \==/2 |  | 6.7 Comparing Terms
A |  |
| abort/0 |  | 6.1 Control Predicates
| atom/1 |  | 6.4 Predicates on terms
| atomic/1 |  | 6.4 Predicates on terms
B |  |
| bagof/3 |  | 6.13 Collecting Solutions to a Goal
| break/0 |  | 6.1 Control Predicates
C |  |
| call/1 |  | 6.1 Control Predicates
| close/1 |  | 6.9.1 Handling Streams and Files
| compare/3 |  | 6.7 Comparing Terms
| consult/1 |  | 4.1 Program loading and updating
| current_atom/1 |  | 6.10.2 Looking at the Data Base
| current_predicate/1 |  | 6.10.2 Looking at the Data Base
D |  |
| db_reference/1 |  | 6.4 Predicates on terms
| debug/0 |  | 21.1 Debugging Predicates
| debugging/0 |  | 21.1 Debugging Predicates
| display/1 |  | 6.9.3 Handling Input/Output of Terms
E |  |
| erase/1 |  | 6.11 Internal Data Base
| erased/1 |  | 6.11 Internal Data Base
| exists/1 |  | 6.9.7 Controlling Input/Output
| expand_exprs/2 |  | 4.2 Changing the Compiler’s Behavior
| expand_term/2 |  | 6.14 Grammar Rules
F |  |
| fail/0 |  | 6.1 Control Predicates
| fileerrors/0 |  | 6.9.7 Controlling Input/Output
| findall/3 |  | 6.13 Collecting Solutions to a Goal
| functor/3 |  | 6.4 Predicates on terms
G |  |
| get/1 |  | 6.9.4 Handling Input/Output of Characters
| get0/1 |  | 6.9.4 Handling Input/Output of Characters
H |  |
| halt/0 |  | 6.1 Control Predicates
I |  |
| instance/2 |  | 6.11 Internal Data Base
| integer/1 |  | 6.4 Predicates on terms
K |  |
| keysort/2 |  | 6.7 Comparing Terms
L |  |
| leash/1 |  | 21.1 Debugging Predicates
| length/2 |  | 6.7 Comparing Terms
N |  |
| name/2 |  | 6.5 Predicates on Atoms
| nl/0 |  | 6.9.4 Handling Input/Output of Characters
| nodebug/0 |  | 21.1 Debugging Predicates
| nofileerrors/0 |  | 6.9.7 Controlling Input/Output
| nonvar/1 |  | 6.4 Predicates on terms
| nospy/1 |  | 21.1 Debugging Predicates
| not/1 |  | 6.1 Control Predicates
| notrace/0 |  | 21.1 Debugging Predicates
| number/1 |  | 6.4 Predicates on terms
O |  |
| op/3 |  | 6.22 Miscellaneous
P |  |
| primitive/1 |  | 6.4 Predicates on terms
| print/1 |  | 6.9.3 Handling Input/Output of Terms
| prompt/2 |  | 6.22 Miscellaneous
| put/1 |  | 6.9.4 Handling Input/Output of Characters
R |  |
| rational/1 |  | 6.4 Predicates on terms
| read/1 |  | 6.9.3 Handling Input/Output of Terms
| reconsult/1 |  | 4.1 Program loading and updating
| recorda/3 |  | 6.11 Internal Data Base
| recorded/3 |  | 6.11 Internal Data Base
| recordz/3 |  | 6.11 Internal Data Base
| rename/2 |  | 6.15 Access to Operating System Functionality
| repeat/0 |  | 6.1 Control Predicates
S |  |
| save/1 |  | 4.4 Saving and Loading Prolog States
| see/1 |  | 6.9.2 Handling Streams and Files
| seeing/1 |  | 6.9.2 Handling Streams and Files
| seen/0 |  | 6.9.2 Handling Streams and Files
| setof/3 |  | 6.13 Collecting Solutions to a Goal
| sh/0 |  | 6.15 Access to Operating System Functionality
| skip/1 |  | 6.9.4 Handling Input/Output of Characters
| sort/2 |  | 6.7 Comparing Terms
| spy/1 |  | 21.1 Debugging Predicates
| statistics/0 |  | 6.22 Miscellaneous
| system/1 |  | 6.15 Access to Operating System Functionality
T |  |
| tab/1 |  | 6.9.4 Handling Input/Output of Characters
| tell/1 |  | 6.9.2 Handling Streams and Files
| telling/1 |  | 6.9.2 Handling Streams and Files
| term_expansion/2 |  | 6.14 Grammar Rules
| told/0 |  | 6.9.2 Handling Streams and Files
| trace/0 |  | 21.1 Debugging Predicates
| true/0 |  | 6.1 Control Predicates
V |  |
| var/1 |  | 6.4 Predicates on terms
W |  |
| write/1 |  | 6.9.3 Handling Input/Output of Terms
| writeq/1 |  | 6.9.3 Handling Input/Output of Terms

Jump to: | ! , ; < = > @ [ \ A B C D E F G H I K L N O P R S T V W

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 25.1.3 YAP predicates not strictly compatible with C-Prolog

These are YAP built-ins that are also available in C-Prolog, but that are not fully compatible:

Jump to: | A C I L N R

| Index Entry |  | Section
A |  |
| abolish/1 |  | 6.10.1 Modification of the Data Base
| abolish/2 |  | 6.10.1 Modification of the Data Base
| assert/1 |  | 6.10.1 Modification of the Data Base
| assert/2 |  | 6.10.3 Using Data Base References
| asserta/1 |  | 6.10.1 Modification of the Data Base
| asserta/2 |  | 6.10.3 Using Data Base References
| assertz/1 |  | 6.10.1 Modification of the Data Base
| assertz/2 |  | 6.10.3 Using Data Base References
C |  |
| clause/2 |  | 6.10.1 Modification of the Data Base
| clause/3 |  | 6.10.1 Modification of the Data Base
I |  |
| is/2 |  | 6.8 Arithmetic
L |  |
| listing/0 |  | 6.10.2 Looking at the Data Base
| listing/1 |  | 6.10.2 Looking at the Data Base
N |  |
| nth_clause/3 |  | 6.10.1 Modification of the Data Base
R |  |
| retract/2 |  | 6.10.3 Using Data Base References

Jump to: | A C I L N R

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 25.1.4 YAP predicates not available in C-Prolog

These are YAP built-ins not available in C-Prolog.

Jump to: | - = \ A B C D E F G H I J K L M N O P Q R S T U V W Y

| Index Entry |  | Section
- |  |
| ->*/2 |  | 6.1 Control Predicates
| ->/2 |  | 6.1 Control Predicates
= |  |
| =/2 |  | 6.4 Predicates on terms
| =/=2 |  | 6.4 Predicates on terms
| =@=/2 |  | 8 SWI-Prolog Emulation
\ |  |
| \=/2 |  | 6.4 Predicates on terms
A |  |
| abolish_all_tables/0 |  | 18 Tabling
| abolish_table/1 |  | 18 Tabling
| absolute_file_name/2 |  | 6.9.1 Handling Streams and Files
| absolute_file_name/3 |  | 6.9.1 Handling Streams and Files
| add_edges/3 |  | 7.28 Unweighted Graphs
| add_to_array_element/4 |  | 6.20 Arrays
| add_to_heap/4 |  | 7.5 Heaps
| add_vertices/3 |  | 7.28 Unweighted Graphs
| aggregate/3 |  | 7.1 Aggregate
| aggregate/4 |  | 7.1 Aggregate
| aggregate_all/3 |  | 7.1 Aggregate
| aggregate_all/4 |  | 7.1 Aggregate
| alarm/3 |  | 6.15 Access to Operating System Functionality
| all/3 |  | 6.13 Collecting Solutions to a Goal
| always_prompt_user/0 |  | 6.9.7 Controlling Input/Output
| append/2 |  | 7.6 List Manipulation
| append/3 |  | 7.6 List Manipulation
| append/3 |  | 8 SWI-Prolog Emulation
| arg/3 |  | 6.4 Predicates on terms
| array/2 |  | 6.20 Arrays
| array_element/3 |  | 6.20 Arrays
| asserta_static/1 |  | 6.10.1 Modification of the Data Base
| assertz_static/1 |  | 6.10.1 Modification of the Data Base
| assert_static/1 |  | 6.10.1 Modification of the Data Base
| assoc_to_list/2 |  | 7.3 Association Lists
| atomic_concat/2 |  | 6.5 Predicates on Atoms
| atomic_list_concat/2 |  | 6.5 Predicates on Atoms
| atomic_list_concat/3 |  | 6.5 Predicates on Atoms
| atom_chars/2 |  | 6.5 Predicates on Atoms
| atom_codes/2 |  | 6.5 Predicates on Atoms
| atom_concat/2 |  | 6.5 Predicates on Atoms
| atom_concat/3 |  | 6.5 Predicates on Atoms
| atom_length/2 |  | 6.5 Predicates on Atoms
| atom_number/2 |  | 6.5 Predicates on Atoms
| atom_to_chars/2 |  | 7.21 Reading From and Writing To Strings
| atom_to_chars/3 |  | 7.21 Reading From and Writing To Strings
| atom_to_term/3 |  | 7.21 Reading From and Writing To Strings
| attribute_goal/2 |  | 11.2.4 Displaying Attributes
| attribute_goals/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| attr_portray_hook/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| attr_unify_hook/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| attvar/1 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| attvar/1 |  | 11.2.3 Attributed Unification
| at_end_of_stream/0 |  | 6.9.1 Handling Streams and Files
| at_end_of_stream/1 |  | 6.9.1 Handling Streams and Files
| avl_insert/4 |  | 7.4 AVL Trees
| avl_lookup/3 |  | 7.4 AVL Trees
| avl_new/1 |  | 7.4 AVL Trees
B |  |
| bb_delete/2 |  | 6.12 The Blackboard
| bb_get/2 |  | 6.12 The Blackboard
| bb_put/2 |  | 6.12 The Blackboard
| bb_update/3 |  | 6.12 The Blackboard
| between/3 |  | 6.8 Arithmetic
| between/3 |  | 8 SWI-Prolog Emulation
| b_getval/2 |  | 6.17 Global Variables
| b_getval/2 |  | 9 SWI Global variables
| b_setval/2 |  | 6.17 Global Variables
| b_setval/2 |  | 9 SWI Global variables
C |  |
| C/3 |  | 6.14 Grammar Rules
| call/n |  | 6.1 Control Predicates
| callable/1 |  | 6.4 Predicates on terms
| call_cleanup/1 |  | 7.25 Call Cleanup
| call_cleanup/2 |  | 7.25 Call Cleanup
| call_count_data/0 |  | 6.19 Counting Calls
| call_count_data/3 |  | 6.19 Counting Calls
| call_count_data/3 |  | 6.19 Counting Calls
| call_residue/2 |  | 10.2 Co-routining
| call_residue_vars/2 |  | 10.2 Co-routining
| call_shared_object_function/2 |  | 23.11 Loading Object Files
| call_with_args/n |  | 6.1 Control Predicates
| catch/3 |  | 6.1 Control Predicates
| cd/0 |  | 6.15 Access to Operating System Functionality
| cd/1 |  | 6.15 Access to Operating System Functionality
| character_count/2 |  | 6.9.1 Handling Streams and Files
| char_code/2 |  | 6.6 Predicates on Characters
| char_conversion/2 |  | 6.9.3 Handling Input/Output of Terms
| char_type/2 |  | 6.6 Predicates on Characters
| chdir/1 |  | 8 SWI-Prolog Emulation
| checklist/2 |  | 7.8 Maplist
| checknodes/3 |  | 7.8 Maplist
| cleanup_all/0 |  | 7.25 Call Cleanup
| close/2 |  | 6.9.1 Handling Streams and Files
| close_matlab/0 |  | 7.10 MATLAB Package Interface
| close_shared_object/1 |  | 23.11 Loading Object Files
| close_static_array/1 |  | 6.20 Arrays
| code_type/2 |  | 6.6 Predicates on Characters
| compile/1 |  | 4.1 Program loading and updating
| compile/1 |  | 4.1 Program loading and updating
| compile/1 (directive) |  | 4.1 Program loading and updating
| compile_expressions/0 |  | 4.2 Changing the Compiler’s Behavior
| complement/2 |  | 7.28 Unweighted Graphs
| compose/3 |  | 7.28 Unweighted Graphs
| compound/1 |  | 6.4 Predicates on terms
| concat_atom/2 |  | 8 SWI-Prolog Emulation
| concat_atom/3 |  | 8 SWI-Prolog Emulation
| convlist/3 |  | 7.8 Maplist
| copy_line/2 |  | 7.7 Line Manipulation Utilities
| copy_line/2 |  | 7.7 Line Manipulation Utilities
| copy_term/2 |  | 6.4 Predicates on terms
| copy_term/3 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| copy_term_nat/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| create_mutable/2 |  | 6.16 Term Modification
| create_prolog_flag/2 |  | 6.22 Miscellaneous
| current_char_conversion/2 |  | 6.9.3 Handling Input/Output of Terms
| current_foreign_library/2 |  | 7.19 SWI-Prolog’s shlib library
| current_input/1 |  | 6.9.1 Handling Streams and Files
| current_key/2 |  | 6.11 Internal Data Base
| current_line_number/1 |  | 6.9.1 Handling Streams and Files
| current_line_number/2 |  | 6.9.1 Handling Streams and Files
| current_module/1 |  | 6.21 Predicate Information
| current_module/2 |  | 6.21 Predicate Information
| current_mutex/3 |  | 16.4 Thread Synchronisation
| current_op/3 |  | 6.22 Miscellaneous
| current_output/1 |  | 6.9.1 Handling Streams and Files
| current_predicate/2 |  | 6.10.2 Looking at the Data Base
| current_prolog_flag/2 |  | 6.22 Miscellaneous
| current_stream/3 |  | 6.9.1 Handling Streams and Files
| current_thread/2 |  | 16.2 Monitoring Threads
| cyclic_term/1 |  | 6.4 Predicates on terms
| cyclic_term/1 |  | 7.23 Utilities On Terms
D |  |
| datime/1 |  | 7.22 Calling The Operating System from YAP
| db_assert/1 |  | 15.8 Insertion of Rows
| db_assert/2 |  | 15.8 Insertion of Rows
| db_close/1 |  | 15.4 Connecting to and disconnecting from a Database Server
| db_datalog_describe/1 |  | 15.11 Describing a Relation
| db_datalog_describe/2 |  | 15.11 Describing a Relation
| db_describe/1 |  | 15.11 Describing a Relation
| db_describe/2 |  | 15.11 Describing a Relation
| db_get_attributes_types/2 |  | 15.9 Types of Attributes
| db_get_attributes_types/3 |  | 15.9 Types of Attributes
| db_import/2 |  | 15.5 Accessing a Relation
| db_import/3 |  | 15.5 Accessing a Relation
| db_insert/2 |  | 15.8 Insertion of Rows
| db_insert/3 |  | 15.8 Insertion of Rows
| db_module/1 |  | 15.14 Other MYDDAS Properties
| db_my_result_set/1 |  | 15.14 Other MYDDAS Properties
| db_my_sql_mode/1 |  | 15.14 Other MYDDAS Properties
| db_my_sql_mode/2 |  | 15.14 Other MYDDAS Properties
| db_number_of_fields/2 |  | 15.10 Number of Fields
| db_number_of_fields/3 |  | 15.10 Number of Fields
| db_open/4 |  | 15.4 Connecting to and disconnecting from a Database Server
| db_open/5 |  | 15.4 Connecting to and disconnecting from a Database Server
| db_show_tables/1 |  | 15.12 Enumeration Relations
| db_show_tables/2 |  | 15.12 Enumeration Relations
| db_sql/2 |  | 15.7 Accessing Tables in Data Sources Using SQL
| db_sql/3 |  | 15.7 Accessing Tables in Data Sources Using SQL
| db_top_level/4 |  | 15.13 The MYDDAS MySQL Top Level
| db_top_level/5 |  | 15.13 The MYDDAS MySQL Top Level
| db_view/2 |  | 15.6 View Level Interface
| db_view/3 |  | 15.6 View Level Interface
| delete/3 |  | 7.6 List Manipulation
| delete_file/1 |  | 7.22 Calling The Operating System from YAP
| delete_file/2 |  | 7.22 Calling The Operating System from YAP
| del_assoc/4 |  | 7.3 Association Lists
| del_attr/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| del_attrs/1 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| del_edges/3 |  | 7.28 Unweighted Graphs
| del_max_assoc/4 |  | 7.3 Association Lists
| del_min_assoc/4 |  | 7.3 Association Lists
| del_vertices/3 |  | 7.28 Unweighted Graphs
| dgraph_add_edge/4 |  | 7.29 Directed Graphs
| dgraph_add_edges/3 |  | 7.29 Directed Graphs
| dgraph_add_vertex/3 |  | 7.29 Directed Graphs
| dgraph_add_vertices/3 |  | 7.29 Directed Graphs
| dgraph_complement/2 |  | 7.29 Directed Graphs
| dgraph_compose/3 |  | 7.29 Directed Graphs
| dgraph_del_edge/4 |  | 7.29 Directed Graphs
| dgraph_del_edges/3 |  | 7.29 Directed Graphs
| dgraph_del_vertex/3 |  | 7.29 Directed Graphs
| dgraph_del_vertices/3 |  | 7.29 Directed Graphs
| dgraph_edge/2 |  | 7.29 Directed Graphs
| dgraph_edges/2 |  | 7.29 Directed Graphs
| dgraph_isomorphic/4 |  | 7.29 Directed Graphs
| dgraph_max_path/5 |  | 7.29 Directed Graphs
| dgraph_min_path/5 |  | 7.29 Directed Graphs
| dgraph_min_paths/3 |  | 7.29 Directed Graphs
| dgraph_neighbors/3 |  | 7.29 Directed Graphs
| dgraph_neighbours/3 |  | 7.29 Directed Graphs
| dgraph_new/1 |  | 7.29 Directed Graphs
| dgraph_path/3 |  | 7.29 Directed Graphs
| dgraph_path/3 |  | 7.29 Directed Graphs
| dgraph_symmetric_closure/2 |  | 7.29 Directed Graphs
| dgraph_top_sort/2 |  | 7.29 Directed Graphs
| dgraph_top_sort/3 |  | 7.29 Directed Graphs
| dgraph_to_ugraph/2 |  | 7.29 Directed Graphs
| dgraph_to_undgraph/2 |  | 7.30 Undirected Graphs
| dgraph_transitive_closure/2 |  | 7.29 Directed Graphs
| dgraph_transpose/2 |  | 7.29 Directed Graphs
| dgraph_vertices/2 |  | 7.29 Directed Graphs
| dif/2 |  | 10.2 Co-routining
| directory_files/2 |  | 7.22 Calling The Operating System from YAP
| discontiguous/1 (directive) |  | 4.2 Changing the Compiler’s Behavior
| display/1 |  | 6.9.3 Handling Input/Output of Terms
| display/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| do_not_compile_expressions/0 |  | 4.2 Changing the Compiler’s Behavior
| duplicate_term/2 |  | 6.4 Predicates on terms
| dynamic/1 |  | 6.10 Using the Clausal Data Base
| dynamic_predicate/2 |  | 6.10 Using the Clausal Data Base
E |  |
| edges/2 |  | 7.28 Unweighted Graphs
| elif/1 |  | 4.3 Conditional Compilation
| else/0 |  | 4.3 Conditional Compilation
| empty_assoc/1 |  | 7.3 Association Lists
| empty_heap/1 |  | 7.5 Heaps
| empty_queue/1 |  | 7.14 Queues
| endif/0 |  | 4.3 Conditional Compilation
| environ/2 |  | 6.15 Access to Operating System Functionality
| environ/2 |  | 7.22 Calling The Operating System from YAP
| eraseall/1 |  | 6.11 Internal Data Base
| exception/3 |  | 6.2 Handling Undefined Procedures
| exclude/3 |  | 7.8 Maplist
| exec/3 |  | 7.22 Calling The Operating System from YAP
| expand_file_name/2 |  | 4.2 Changing the Compiler’s Behavior
F |  |
| false/0 |  | 6.1 Control Predicates
| fields/2 |  | 7.7 Line Manipulation Utilities
| fields/3 |  | 7.7 Line Manipulation Utilities
| file_base_name/2 |  | 6.9.1 Handling Streams and Files
| file_exists/1 |  | 7.22 Calling The Operating System from YAP
| file_exists/2 |  | 7.22 Calling The Operating System from YAP
| file_filter/3 |  | 7.7 Line Manipulation Utilities
| file_filter_with_init/5 |  | 7.7 Line Manipulation Utilities
| file_name_extension/3 |  | 6.9.1 Handling Streams and Files
| file_property/2 |  | 7.22 Calling The Operating System from YAP
| file_search_path/2 |  | 4.2 Changing the Compiler’s Behavior
| filter/3 |  | 7.7 Line Manipulation Utilities
| findall/4 |  | 6.13 Collecting Solutions to a Goal
| flatten/2 |  | 7.6 List Manipulation
| float/1 |  | 6.4 Predicates on terms
| flush_output/0 |  | 6.9.1 Handling Streams and Files
| flush_output/1 |  | 6.9.1 Handling Streams and Files
| forall/2 |  | 6.1 Control Predicates
| forall/2 |  | 8.2 Forall
| foreach/2 |  | 7.1 Aggregate
| format/1 |  | 6.9.3 Handling Input/Output of Terms
| format/2 |  | 6.9.3 Handling Input/Output of Terms
| format/3 |  | 6.9.3 Handling Input/Output of Terms
| format_to_chars/3 |  | 7.21 Reading From and Writing To Strings
| format_to_chars/4 |  | 7.21 Reading From and Writing To Strings
| fragile |  | 7.25 Call Cleanup
| freeze/2 |  | 10.2 Co-routining
| free_variables/4 |  | 7.1 Aggregate
| frozen/2 |  | 10.2 Co-routining
G |  |
| garbage_collect/0 |  | 6.1 Control Predicates
| garbage_collect_atoms/0 |  | 6.1 Control Predicates
| gc/0 |  | 6.1 Control Predicates
| gen_assoc/3 |  | 7.3 Association Lists
| get/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| get0/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| getcwd/1 |  | 6.15 Access to Operating System Functionality
| getrand/1 |  | 7.15 Random Number Generator
| get_assoc/3 |  | 7.3 Association Lists
| get_assoc/5 |  | 7.3 Association Lists
| get_attr/3 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| get_attrs/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| get_atts/2 |  | 11.2.2 Attribute Manipulation
| get_byte/1 |  | 6.9.4 Handling Input/Output of Characters
| get_byte/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| get_char/1 |  | 6.9.4 Handling Input/Output of Characters
| get_char/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| get_code/1 |  | 6.9.4 Handling Input/Output of Characters
| get_code/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| get_from_heap/4 |  | 7.5 Heaps
| get_label/3 |  | 7.27 Updatable Binary Trees
| get_mutable/2 |  | 6.16 Term Modification
| get_mutable/2 |  | 6.16 Term Modification
| get_next_assoc/4 |  | 7.3 Association Lists
| get_prev_assoc/4 |  | 7.3 Association Lists
| get_value/2 |  | 6.11 Internal Data Base
| glue/3 |  | 7.7 Line Manipulation Utilities
| goal_expansion/3 |  | 6.14 Grammar Rules
| ground/1 |  | 6.4 Predicates on terms
| grow_heap/1 |  | 6.1 Control Predicates
| grow_stack/1 |  | 6.1 Control Predicates
H |  |
| halt/1 |  | 6.1 Control Predicates
| head_queue/2 |  | 7.14 Queues
| heap_size/2 |  | 7.5 Heaps
| heap_to_list/2 |  | 7.5 Heaps
| hide/1 |  | 4.2 Changing the Compiler’s Behavior
| hide_predicate/1 |  | 4.2 Changing the Compiler’s Behavior
| host_id/1 |  | 7.22 Calling The Operating System from YAP
| host_name/1 |  | 7.22 Calling The Operating System from YAP
I |  |
| if/1 |  | 4.3 Conditional Compilation
| if/3 |  | 6.1 Control Predicates
| ignore/1 |  | 6.1 Control Predicates
| include/3 |  | 7.8 Maplist
| incore/1 |  | 6.1 Control Predicates
| initialization/0 |  | 6.22 Miscellaneous
| initialization/1 (directive) |  | 4.2 Changing the Compiler’s Behavior
| initialization/2 (directive) |  | 4.2 Changing the Compiler’s Behavior
| intersection/3 |  | 7.6 List Manipulation
| is_assoc/1 |  | 7.3 Association Lists
| is_list/1 |  | 6.4 Predicates on terms
| is_mutable/1 |  | 6.16 Term Modification
| is_rbtree/1 |  | 7.17 Red-Black Trees
| is_stream/1 |  | 6.9.1 Handling Streams and Files
| is_tabled/1 |  | 18 Tabling
J |  |
| join_queue/3 |  | 7.14 Queues
| jump_queue/3 |  | 7.14 Queues
K |  |
| key_statistics/3 |  | 6.11 Internal Data Base
| key_statistics/4 |  | 6.11 Internal Data Base
| kill/2 |  | 7.22 Calling The Operating System from YAP
L |  |
| last/2 |  | 7.6 List Manipulation
| length_queue/2 |  | 7.14 Queues
| library_directory/1 |  | 4.2 Changing the Compiler’s Behavior
| library_directory/1 |  | 4.2 Changing the Compiler’s Behavior
| line_count/2 |  | 6.9.1 Handling Streams and Files
| line_position/2 |  | 6.9.1 Handling Streams and Files
| list_concat/2 |  | 7.6 List Manipulation
| list_join_queue/3 |  | 7.14 Queues
| list_jump_queue/3 |  | 7.14 Queues
| list_to_assoc/2 |  | 7.3 Association Lists
| list_to_heap/2 |  | 7.5 Heaps
| list_to_ord_set/2 |  | 7.12 Ordered Sets
| list_to_queue/2 |  | 7.14 Queues
| list_to_rbtree/2 |  | 7.17 Red-Black Trees
| list_to_rbtree/2 |  | 7.17 Red-Black Trees
| list_to_tree/2 |  | 7.27 Updatable Binary Trees
| load_files/2 |  | 4.1 Program loading and updating
| load_foreign_library/1 |  | 7.19 SWI-Prolog’s shlib library
| load_foreign_library/2 |  | 7.19 SWI-Prolog’s shlib library
| ls/0 |  | 6.15 Access to Operating System Functionality
M |  |
| make/0 |  | 4.1 Program loading and updating
| make_diagram/2 |  | 7.33 Block Diagram
| make_diagram/2 |  | 7.33 Block Diagram
| make_directory/2 |  | 7.22 Calling The Operating System from YAP
| make_queue/1 |  | 7.14 Queues
| mapargs/3 |  | 7.8 Maplist
| maplist/2 |  | 8.1 Invoking Predicates on all Members of a List
| maplist/3 |  | 7.8 Maplist
| maplist/3 |  | 7.8 Maplist
| maplist/3 |  | 8.1 Invoking Predicates on all Members of a List
| maplist/4 |  | 7.8 Maplist
| maplist/4 |  | 8.1 Invoking Predicates on all Members of a List
| maplist/5 |  | 7.8 Maplist
| mapnodes/3 |  | 7.8 Maplist
| map_assoc/2 |  | 7.3 Association Lists
| map_assoc/3 |  | 7.3 Association Lists
| map_tree/3 |  | 7.27 Updatable Binary Trees
| matlab_cells/2 |  | 7.10 MATLAB Package Interface
| matlab_cells/3 |  | 7.10 MATLAB Package Interface
| matlab_eval_string/1 |  | 7.10 MATLAB Package Interface
| matlab_eval_string/2 |  | 7.10 MATLAB Package Interface
| matlab_get_variable/2 |  | 7.10 MATLAB Package Interface
| matlab_initialized_cells/4 |  | 7.10 MATLAB Package Interface
| matlab_item/3 |  | 7.10 MATLAB Package Interface
| matlab_item/3 |  | 7.10 MATLAB Package Interface
| matlab_item/4 |  | 7.10 MATLAB Package Interface
| matlab_item/4 |  | 7.10 MATLAB Package Interface
| matlab_matrix/4 |  | 7.10 MATLAB Package Interface
| matlab_on/0 |  | 7.10 MATLAB Package Interface
| matlab_sequence/3 |  | 7.10 MATLAB Package Interface
| matlab_set/4 |  | 7.10 MATLAB Package Interface
| matlab_vector/4 |  | 7.10 MATLAB Package Interface
| matlab_zeros/2 |  | 7.10 MATLAB Package Interface
| matlab_zeros/3 |  | 7.10 MATLAB Package Interface
| matlab_zeros/4 |  | 7.10 MATLAB Package Interface
| matlab_zeros/4 |  | 7.10 MATLAB Package Interface
| matrix_add/3 |  | 7.9 Matrix Library
| matrix_agg_cols/2 |  | 7.9 Matrix Library
| matrix_agg_lines/2 |  | 7.9 Matrix Library
| matrix_arg_to_offset/3 |  | 7.9 Matrix Library
| matrix_column/3 |  | 7.9 Matrix Library
| matrix_dec/2 |  | 7.9 Matrix Library
| matrix_dec/3 |  | 7.9 Matrix Library
| matrix_dims/2 |  | 7.9 Matrix Library
| matrix_expand/3 |  | 7.9 Matrix Library
| matrix_get/3 |  | 7.9 Matrix Library
| matrix_inc/2 |  | 7.9 Matrix Library
| matrix_inc/3 |  | 7.9 Matrix Library
| matrix_max/2 |  | 7.9 Matrix Library
| matrix_maxarg/2 |  | 7.9 Matrix Library
| matrix_min/2 |  | 7.9 Matrix Library
| matrix_minarg/2 |  | 7.9 Matrix Library
| matrix_ndims/2 |  | 7.9 Matrix Library
| matrix_new/3 |  | 7.9 Matrix Library
| matrix_new/4 |  | 7.9 Matrix Library
| matrix_new_set/4 |  | 7.9 Matrix Library
| matrix_offset_to_arg/3 |  | 7.9 Matrix Library
| matrix_op/4 |  | 7.9 Matrix Library
| matrix_op/4 |  | 7.9 Matrix Library
| matrix_op_to_cols/4 |  | 7.9 Matrix Library
| matrix_op_to_lines/4 |  | 7.9 Matrix Library
| matrix_reorder/3 |  | 7.9 Matrix Library
| matrix_select/4 |  | 7.9 Matrix Library
| matrix_set/3 |  | 7.9 Matrix Library
| matrix_set_all/2 |  | 7.9 Matrix Library
| matrix_shuffle/3 |  | 7.9 Matrix Library
| matrix_size/2 |  | 7.9 Matrix Library
| matrix_sum/2 |  | 7.9 Matrix Library
| matrix_to_list/2 |  | 7.9 Matrix Library
| matrix_type/2 |  | 7.9 Matrix Library
| max_assoc/3 |  | 7.3 Association Lists
| max_list/2 |  | 7.6 List Manipulation
| member/2 |  | 7.6 List Manipulation
| memberchk/2 |  | 7.6 List Manipulation
| merge/3 |  | 7.12 Ordered Sets
| message_hook/3 |  | 6.3 Message Handling
| message_queue_create/1 |  | 16.3.1 Message Queues
| message_queue_destroy/1 |  | 16.3.1 Message Queues
| message_to_string/2 |  | 6.3 Message Handling
| meta_predicate/1 (directive) |  | 5.4 Meta-Predicates in Modules
| min_assoc/3 |  | 7.3 Association Lists
| min_list/2 |  | 7.6 List Manipulation
| min_of_heap/3 |  | 7.5 Heaps
| min_of_heap/5 |  | 7.5 Heaps
| mktemp/2 |  | 7.22 Calling The Operating System from YAP
| mktime/2 |  | 7.22 Calling The Operating System from YAP
| module/1 |  | 5.2 Defining a New Module
| module/2 (directive) |  | 5.2 Defining a New Module
| module/3 (directive) |  | 5.2 Defining a New Module
| module_transparent/1 (directive) |  | 5.4 Meta-Predicates in Modules
| mpi_barrier/0 |  | 7.32 LAM
| mpi_bcast/2 |  | 7.32 LAM
| mpi_bcast/3 |  | 7.32 LAM
| mpi_bcast/3 |  | 7.32 LAM
| mpi_comm_rank/1 |  | 7.32 LAM
| mpi_comm_size/1 |  | 7.32 LAM
| mpi_finalize/0 |  | 7.32 LAM
| mpi_gc/0 |  | 7.32 LAM
| mpi_init/0 |  | 7.32 LAM
| mpi_irecv/3 |  | 7.32 LAM
| mpi_isend/4 |  | 7.32 LAM
| mpi_recv/3 |  | 7.32 LAM
| mpi_send/3 |  | 7.32 LAM
| mpi_test/2 |  | 7.32 LAM
| mpi_test_recv/3 |  | 7.32 LAM
| mpi_version/2 |  | 7.32 LAM
| mpi_wait/2 |  | 7.32 LAM
| mpi_wait_recv/3 |  | 7.32 LAM
| multifile/1 (directive) |  | 4.2 Changing the Compiler’s Behavior
| mutex_create/1 |  | 16.4 Thread Synchronisation
| mutex_destroy/1 |  | 16.4 Thread Synchronisation
| mutex_lock/1 |  | 16.4 Thread Synchronisation
| mutex_statistics/0 |  | 16.2 Monitoring Threads
| mutex_trylock/1 |  | 16.4 Thread Synchronisation
| mutex_unlock/1 |  | 16.4 Thread Synchronisation
| mutex_unlock_all/0 |  | 16.4 Thread Synchronisation
N |  |
| nb_beam/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_beam_add/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_beam_close/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_beam_del/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_beam_empty/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_beam_peek/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_beam_size/2 |  | 7.11 Non-Backtrackable Data Structures
| nb_current/2 |  | 6.17 Global Variables
| nb_current/2 |  | 9 SWI Global variables
| nb_delete/1 |  | 9 SWI Global variables
| nb_delete/2 |  | 6.17 Global Variables
| nb_getval/2 |  | 6.17 Global Variables
| nb_getval/2 |  | 9 SWI Global variables
| nb_heap/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_heap_add/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_heap_close/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_heap_del/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_heap_empty/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_heap_peek/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_heap_size/2 |  | 7.11 Non-Backtrackable Data Structures
| nb_linkarg/3 |  | 6.17 Global Variables
| nb_linkval/2 |  | 6.17 Global Variables
| nb_queue/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_queue_close/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_queue_dequeue/2 |  | 7.11 Non-Backtrackable Data Structures
| nb_queue_empty/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_queue_enqueue/2 |  | 7.11 Non-Backtrackable Data Structures
| nb_queue_peek/2 |  | 7.11 Non-Backtrackable Data Structures
| nb_queue_size/2 |  | 7.11 Non-Backtrackable Data Structures
| nb_setarg/3 |  | 6.17 Global Variables
| nb_setval/2 |  | 6.17 Global Variables
| nb_setval/2 |  | 9 SWI Global variables
| nb_set_shared_arg/3 |  | 6.17 Global Variables
| nb_set_shared_val/2 |  | 6.17 Global Variables
| neighbors/3 |  | 7.28 Unweighted Graphs
| neighbours/3 |  | 7.28 Unweighted Graphs
| new_variables_in_term/3 |  | 7.23 Utilities On Terms
| nl/1 |  | 6.9.5 Input/Output Predicates applied to Streams
| nogc/0 |  | 6.1 Control Predicates
| nospyall/0 |  | 21.1 Debugging Predicates
| no_source/0 |  | 4.2 Changing the Compiler’s Behavior
| nth/3 |  | 7.6 List Manipulation
| nth/4 |  | 7.6 List Manipulation
| nth0/3 |  | 7.6 List Manipulation
| nth0/4 |  | 7.6 List Manipulation
| nth1/3 |  | 7.6 List Manipulation
| nth1/3 |  | 8 SWI-Prolog Emulation
| nth1/4 |  | 7.6 List Manipulation
| nth_instance/3 |  | 6.11 Internal Data Base
| nth_instance/4 |  | 6.11 Internal Data Base
| numbervars/3 |  | 6.4 Predicates on terms
| number_atom/2 |  | 6.5 Predicates on Atoms
| number_chars/2 |  | 6.5 Predicates on Atoms
| number_codes/2 |  | 6.5 Predicates on Atoms
| number_to_chars/2 |  | 7.21 Reading From and Writing To Strings
| number_to_chars/3 |  | 7.21 Reading From and Writing To Strings
| numlist/3 |  | 7.6 List Manipulation
O |  |
| once/1 |  | 6.1 Control Predicates
| on_cleanup/1 |  | 7.25 Call Cleanup
| on_signal/3 |  | 6.15 Access to Operating System Functionality
| open/3 |  | 6.9.1 Handling Streams and Files
| open/4 |  | 6.9.1 Handling Streams and Files
| open_chars_stream/2 |  | 7.21 Reading From and Writing To Strings
| open_shared_object/2 |  | 23.11 Loading Object Files
| open_shared_object/3 |  | 23.11 Loading Object Files
| ordsubset/2 |  | 7.12 Ordered Sets
| ord_add_element/3 |  | 7.12 Ordered Sets
| ord_del_element/3 |  | 7.12 Ordered Sets
| ord_disjoint/2 |  | 7.12 Ordered Sets
| ord_insert/3 |  | 7.12 Ordered Sets
| ord_intersect/2 |  | 7.12 Ordered Sets
| ord_intersect/3 |  | 7.12 Ordered Sets
| ord_intersect/4 |  | 7.12 Ordered Sets
| ord_list_to_assoc/2 |  | 7.3 Association Lists
| ord_member/2 |  | 7.12 Ordered Sets
| ord_seteq/2 |  | 7.12 Ordered Sets
| ord_setproduct/3 |  | 7.12 Ordered Sets
| ord_subtract/3 |  | 7.12 Ordered Sets
| ord_symdiff/3 |  | 7.12 Ordered Sets
| ord_union/2 |  | 7.12 Ordered Sets
| ord_union/3 |  | 7.12 Ordered Sets
| ord_union/4 |  | 7.12 Ordered Sets
P |  |
| partition/4 |  | 7.8 Maplist
| partition/5 |  | 7.8 Maplist
| path/1 |  | 4.2 Changing the Compiler’s Behavior
| path/1 |  | 4.2 Changing the Compiler’s Behavior
| path/1 |  | 4.2 Changing the Compiler’s Behavior
| peek_byte/1 |  | 6.9.4 Handling Input/Output of Characters
| peek_byte/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| peek_char/1 |  | 6.9.4 Handling Input/Output of Characters
| peek_char/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| peek_code/1 |  | 6.9.4 Handling Input/Output of Characters
| peek_code/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| permutation/2 |  | 7.6 List Manipulation
| phrase/2 |  | 6.14 Grammar Rules
| phrase/3 |  | 6.14 Grammar Rules
| pid/1 |  | 7.22 Calling The Operating System from YAP
| plus/3 |  | 6.8 Arithmetic
| popen/3 |  | 7.22 Calling The Operating System from YAP
| portray_clause/1 |  | 6.10.2 Looking at the Data Base
| portray_clause/2 |  | 6.10.2 Looking at the Data Base
| predicate_property/2 |  | 6.10.2 Looking at the Data Base
| predsort/3 |  | 6.7 Comparing Terms
| print/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| print_message/2 |  | 6.3 Message Handling
| print_message_lines/3 |  | 6.3 Message Handling
| process/2 |  | 7.7 Line Manipulation Utilities
| profiled_reset/0 |  | 6.18.1 The Count Profiler
| profile_data/3 |  | 6.18.1 The Count Profiler
| profinit/0 |  | 6.18.2 Tick Profiler
| profoff/0 |  | 6.18.2 Tick Profiler
| profon/0 |  | 6.18.2 Tick Profiler
| project_attributes/2 |  | 11.2.4 Displaying Attributes
| project_attributes/2 |  | 11.2.5 Projecting Attributes
| prolog_file_name/2 |  | 4.2 Changing the Compiler’s Behavior
| prolog_flag/3 |  | 6.22 Miscellaneous
| prolog_initialization/1 |  | 6.22 Miscellaneous
| prolog_load_context/2 |  | 6.22 Miscellaneous
| prolog_to_os_filename/2 |  | 4.2 Changing the Compiler’s Behavior
| public/1 (directive) |  | 4.2 Changing the Compiler’s Behavior
| put/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| putenv/2 |  | 6.15 Access to Operating System Functionality
| put_assoc/4 |  | 7.3 Association Lists
| put_attr/3 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| put_attrs/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| put_atts/2 |  | 11.2.2 Attribute Manipulation
| put_byte/1 |  | 6.9.4 Handling Input/Output of Characters
| put_byte/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| put_char/1 |  | 6.9.4 Handling Input/Output of Characters
| put_char/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| put_code/1 |  | 6.9.4 Handling Input/Output of Characters
| put_code/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| put_label/4 |  | 7.27 Updatable Binary Trees
| pwd/0 |  | 6.15 Access to Operating System Functionality
Q |  |
| queue_to_list/2 |  | 7.14 Queues
R |  |
| random/1 |  | 7.15 Random Number Generator
| random/3 |  | 7.15 Random Number Generator
| randseq/3 |  | 7.15 Random Number Generator
| randset/3 |  | 7.15 Random Number Generator
| rannum/1 |  | 7.13 Pseudo Random Number Integer Generator
| ranstart/0 |  | 7.13 Pseudo Random Number Integer Generator
| ranstart/1 |  | 7.13 Pseudo Random Number Integer Generator
| ranunif/2 |  | 7.13 Pseudo Random Number Integer Generator
| rb_apply/4 |  | 7.17 Red-Black Trees
| rb_clone/3 |  | 7.17 Red-Black Trees
| rb_delete/3 |  | 7.17 Red-Black Trees
| rb_delete/4 |  | 7.17 Red-Black Trees
| rb_del_max/4 |  | 7.17 Red-Black Trees
| rb_del_min/4 |  | 7.17 Red-Black Trees
| rb_empty/1 |  | 7.17 Red-Black Trees
| rb_insert/4 |  | 7.17 Red-Black Trees
| rb_insert_new/4 |  | 7.17 Red-Black Trees
| rb_keys/2 |  | 7.17 Red-Black Trees
| rb_lookup/3 |  | 7.17 Red-Black Trees
| rb_lookupall/3 |  | 7.17 Red-Black Trees
| rb_map/3 |  | 7.17 Red-Black Trees
| rb_max/3 |  | 7.17 Red-Black Trees
| rb_min/3 |  | 7.17 Red-Black Trees
| rb_new/1 |  | 7.17 Red-Black Trees
| rb_next/4 |  | 7.17 Red-Black Trees
| rb_partial_map/4 |  | 7.17 Red-Black Trees
| rb_previous/4 |  | 7.17 Red-Black Trees
| rb_size/2 |  | 7.17 Red-Black Trees
| rb_update/4 |  | 7.17 Red-Black Trees
| rb_visit/2 |  | 7.17 Red-Black Trees
| reachable/3 |  | 7.28 Unweighted Graphs
| read/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| read_file_to_codes/3 |  | 7.16 Read Utilities
| read_file_to_terms/3 |  | 7.16 Read Utilities
| read_from_chars/2 |  | 7.21 Reading From and Writing To Strings
| read_line_to_codes/2 |  | 7.16 Read Utilities
| read_line_to_codes/3 |  | 7.16 Read Utilities
| read_stream_to_codes/3 |  | 7.16 Read Utilities
| read_stream_to_codes/3 |  | 7.16 Read Utilities
| read_term/2 |  | 6.9.3 Handling Input/Output of Terms
| read_term/3 |  | 6.9.5 Input/Output Predicates applied to Streams
| recorda/3 |  | 6.11 Internal Data Base
| recordaifnot/3 |  | 6.11 Internal Data Base
| recordaifnot/3 |  | 6.11 Internal Data Base
| recorda_at/3 |  | 6.11 Internal Data Base
| recordzifnot/3 |  | 6.11 Internal Data Base
| recordz_at/3 |  | 6.11 Internal Data Base
| reexport/1 |  | 5.5 Re-Exporting Predicates From Other Modules
| reexport/2 |  | 5.5 Re-Exporting Predicates From Other Modules
| regexp/3 |  | 7.18 Regular Expressions
| regexp/4 |  | 7.18 Regular Expressions
| remove_duplicates/2 |  | 7.6 List Manipulation
| remove_from_path/1 |  | 4.2 Changing the Compiler’s Behavior
| rename_file/2 |  | 7.22 Calling The Operating System from YAP
| reset_op_counters/0 |  | 20 Profiling the Abstract Machine
| reset_static_array/1 |  | 6.20 Arrays
| resize_static_array/3 |  | 6.20 Arrays
| restore/1 |  | 4.4 Saving and Loading Prolog States
| retract/1 |  | 6.10.1 Modification of the Data Base
| retractall/1 |  | 6.10.1 Modification of the Data Base
| reverse/2 |  | 7.6 List Manipulation
S |  |
| same_length/2 |  | 7.6 List Manipulation
| save/2 |  | 4.4 Saving and Loading Prolog States
| save_program/1 |  | 4.4 Saving and Loading Prolog States
| save_program/2 |  | 4.4 Saving and Loading Prolog States
| scan_integer/3 |  | 7.7 Line Manipulation Utilities
| scan_natural/3 |  | 7.7 Line Manipulation Utilities
| search_for/2 |  | 7.7 Line Manipulation Utilities
| search_for/2 |  | 7.7 Line Manipulation Utilities
| search_for/2 |  | 7.7 Line Manipulation Utilities
| select/3 |  | 7.6 List Manipulation
| selectchk/3 |  | 7.6 List Manipulation
| selectlist/3 |  | 7.8 Maplist
| serve_queue/3 |  | 7.14 Queues
| setarg/3n |  | 6.16 Term Modification
| setenv/2 |  | 8 SWI-Prolog Emulation
| setrand/1 |  | 7.15 Random Number Generator
| setup_call_catcher_cleanup/4 |  | 7.25 Call Cleanup
| setup_call_cleanup/3 |  | 7.25 Call Cleanup
| set_input/1 |  | 6.9.1 Handling Streams and Files
| set_output/1 |  | 6.9.1 Handling Streams and Files
| set_prolog_flag/2 |  | 6.22 Miscellaneous
| set_stream_position/2 |  | 6.9.1 Handling Streams and Files
| set_value/2 |  | 6.11 Internal Data Base
| shell/0 |  | 7.22 Calling The Operating System from YAP
| shell/1 |  | 7.22 Calling The Operating System from YAP
| shell/1 |  | 7.22 Calling The Operating System from YAP
| showprofres/0 |  | 6.18.2 Tick Profiler
| showprofres/1 |  | 6.18.2 Tick Profiler
| show_ops_by_group/1 |  | 20 Profiling the Abstract Machine
| show_op_counters/1 |  | 20 Profiling the Abstract Machine
| show_table/1 |  | 18 Tabling
| simple/1 |  | 6.4 Predicates on terms
| skip/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| sleep/1 |  | 7.22 Calling The Operating System from YAP
| socket/2 |  | 6.9.8 Using Sockets From YAP
| socket/4 |  | 6.9.8 Using Sockets From YAP
| socket_accept/2 |  | 6.9.8 Using Sockets From YAP
| socket_accept/2 |  | 6.9.8 Using Sockets From YAP
| socket_accept/3 |  | 6.9.8 Using Sockets From YAP
| socket_bind/2 |  | 6.9.8 Using Sockets From YAP
| socket_buffering/4 |  | 6.9.8 Using Sockets From YAP
| socket_close/1 |  | 6.9.8 Using Sockets From YAP
| socket_connect/3 |  | 6.9.8 Using Sockets From YAP
| socket_listen/2 |  | 6.9.8 Using Sockets From YAP
| socket_select/5 |  | 6.9.8 Using Sockets From YAP
| source/0 |  | 4.2 Changing the Compiler’s Behavior
| source_file/1 |  | 6.22 Miscellaneous
| source_file/2 |  | 6.22 Miscellaneous
| source_location/2 |  | 6.22 Miscellaneous
| source_mode/2 |  | 4.2 Changing the Compiler’s Behavior
| splay_access/5 |  | 7.20 Splay Trees
| splay_delete/4 |  | 7.20 Splay Trees
| splay_init/3 |  | 7.20 Splay Trees
| splay_insert/4 |  | 7.20 Splay Trees
| splay_join/3 |  | 7.20 Splay Trees
| splay_split/5 |  | 7.20 Splay Trees
| split/2 |  | 7.7 Line Manipulation Utilities
| split/3 |  | 7.7 Line Manipulation Utilities
| spy_write/2 |  | 21.1 Debugging Predicates
| srandom/1 |  | 6.8 Arithmetic
| start_low_level_trace/0 |  | 19 Tracing at Low Level
| start_low_level_trace/0 |  | 19 Tracing at Low Level
| start_matlab/1 |  | 7.10 MATLAB Package Interface
| static_array/3 |  | 6.20 Arrays
| static_array/3 |  | 6.20 Arrays
| static_array_location/4 |  | 6.20 Arrays
| static_array_properties/3 |  | 6.20 Arrays
| static_array_to_term/3 |  | 6.20 Arrays
| statistics/2 |  | 6.22 Miscellaneous
| stream_position/2 |  | 6.9.1 Handling Streams and Files
| stream_position_data/3 |  | 6.9.1 Handling Streams and Files
| stream_property/2 |  | 6.9.1 Handling Streams and Files
| stream_select/3 |  | 6.9.1 Handling Streams and Files
| style_check/1 |  | 4.2 Changing the Compiler’s Behavior
| style_check/1 |  | 4.2 Changing the Compiler’s Behavior
| sublist/2 |  | 7.6 List Manipulation
| subsumes/2 |  | 7.23 Utilities On Terms
| subsumes_chk/2 |  | 7.23 Utilities On Terms
| subsumes_term/2 |  | 6.4 Predicates on terms
| subtract/3 |  | 7.6 List Manipulation
| sub_atom/5 |  | 6.5 Predicates on Atoms
| succ/3 |  | 6.8 Arithmetic
| suffix/2 |  | 7.6 List Manipulation
| sumargs/4 |  | 7.8 Maplist
| sumlist/2 |  | 7.6 List Manipulation
| sumlist/4 |  | 7.8 Maplist
| sumnodes/4 |  | 7.8 Maplist
| sum_list/2 |  | 7.6 List Manipulation
| sum_list/3 |  | 7.6 List Manipulation
| system/0 |  | 7.22 Calling The Operating System from YAP
| system/2 |  | 7.22 Calling The Operating System from YAP
| system_predicate/2 |  | 6.10.2 Looking at the Data Base
T |  |
| tab/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| table/1 |  | 18 Tabling
| table_statistics/1 |  | 18 Tabling
| tabling_mode/2 |  | 18 Tabling
| tabling_statistics/0 |  | 18 Tabling
| term_attvars/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| term_hash/2 |  | 7.23 Utilities On Terms
| term_hash/4 |  | 7.23 Utilities On Terms
| term_to_atom/2 |  | 7.21 Reading From and Writing To Strings
| term_to_atom/2 |  | 8 SWI-Prolog Emulation
| term_variables/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| threads/0 |  | 16.2 Monitoring Threads
| thread_at_exit/1 |  | 16.1 Creating and Destroying Prolog Threads
| thread_create/1 |  | 16.1 Creating and Destroying Prolog Threads
| thread_create/2 |  | 16.1 Creating and Destroying Prolog Threads
| thread_create/3 |  | 16.1 Creating and Destroying Prolog Threads
| thread_detach/1 |  | 16.1 Creating and Destroying Prolog Threads
| thread_exit/1 |  | 16.1 Creating and Destroying Prolog Threads
| thread_get_message/1 |  | 16.3.1 Message Queues
| thread_get_message/2 |  | 16.3.1 Message Queues
| thread_join/2 |  | 16.1 Creating and Destroying Prolog Threads
| thread_local/1 (directive) |  | 16.3.3 Threads and Dynamic Predicates
| thread_peek_message/1 |  | 16.3.1 Message Queues
| thread_peek_message/2 |  | 16.3.1 Message Queues
| thread_property/2 |  | 16.2 Monitoring Threads
| thread_self/1 |  | 16.1 Creating and Destroying Prolog Threads
| thread_send_message/1 |  | 16.3.1 Message Queues
| thread_send_message/2 |  | 16.3.1 Message Queues
| thread_setconcurrency/2 |  | 16.1 Creating and Destroying Prolog Threads
| thread_signal/2 |  | 16.3.2 Signalling Threads
| thread_sleep/1 |  | 16.1 Creating and Destroying Prolog Threads
| thread_statistics/3 |  | 16.2 Monitoring Threads
| thread_yield/0 |  | 16.1 Creating and Destroying Prolog Threads
| throw/1 |  | 6.1 Control Predicates
| time/1 |  | 6.22 Miscellaneous
| time_file/2 |  | 6.9.1 Handling Streams and Files
| time_out/3 |  | 7.26 Calls With Timeout
| tmpnam/1 |  | 7.22 Calling The Operating System from YAP
| tmp_file/2 |  | 7.22 Calling The Operating System from YAP
| top_sort/2 |  | 7.28 Unweighted Graphs
| top_sort/3 |  | 7.28 Unweighted Graphs
| transitive_closure/2 |  | 7.28 Unweighted Graphs
| transpose/3 |  | 7.28 Unweighted Graphs
| tree_size/2 |  | 7.27 Updatable Binary Trees
| tree_to_list/2 |  | 7.27 Updatable Binary Trees
| trie_check_entry/3 |  | 7.24 Trie DataStructure
| trie_close/1 |  | 7.24 Trie DataStructure
| trie_close_all/0 |  | 7.24 Trie DataStructure
| trie_get_entry/2 |  | 7.24 Trie DataStructure
| trie_load/2 |  | 7.24 Trie DataStructure
| trie_max_stats/4 |  | 7.24 Trie DataStructure
| trie_mode/1 |  | 7.24 Trie DataStructure
| trie_open/1 |  | 7.24 Trie DataStructure
| trie_print/1 |  | 7.24 Trie DataStructure
| trie_put_entry/3 |  | 7.24 Trie DataStructure
| trie_remove_entry/1 |  | 7.24 Trie DataStructure
| trie_remove_subtree/1 |  | 7.24 Trie DataStructure
| trie_save/2 |  | 7.24 Trie DataStructure
| trie_stats/4 |  | 7.24 Trie DataStructure
| trie_usage/4 |  | 7.24 Trie DataStructure
| ttyget/1 |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| ttyget0/1 |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| ttynl/0 |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| ttyput/1 |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| ttyskip/1 |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| ttytab/1 |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
U |  |
| ugraph_to_dgraph/2 |  | 7.29 Directed Graphs
| undgraph_add_edges/3 |  | 7.30 Undirected Graphs
| undgraph_add_vertices/3 |  | 7.30 Undirected Graphs
| undgraph_complement/2 |  | 7.30 Undirected Graphs
| undgraph_del_edges/3 |  | 7.30 Undirected Graphs
| undgraph_del_vertices/3 |  | 7.30 Undirected Graphs
| undgraph_edge/2 |  | 7.30 Undirected Graphs
| undgraph_edges/2 |  | 7.30 Undirected Graphs
| undgraph_neighbors/3 |  | 7.30 Undirected Graphs
| undgraph_neighbours/3 |  | 7.30 Undirected Graphs
| undgraph_new/1 |  | 7.30 Undirected Graphs
| undgraph_vertices/2 |  | 7.30 Undirected Graphs
| unhide/1 |  | 4.2 Changing the Compiler’s Behavior
| unifiable/3 |  | 7.23 Utilities On Terms
| unify_with_occurs_check/2 |  | 6.4 Predicates on terms
| unix/1 |  | 6.15 Access to Operating System Functionality
| unknown/2 |  | 6.2 Handling Undefined Procedures
| unknown_predicate_handler/3 |  | 6.2 Handling Undefined Procedures
| unload_foreign_library/1 |  | 7.19 SWI-Prolog’s shlib library
| unload_foreign_library/2 |  | 7.19 SWI-Prolog’s shlib library
| update_array/3 |  | 6.20 Arrays
| update_mutable/2 |  | 6.16 Term Modification
| use_foreign_library/1 |  | 7.19 SWI-Prolog’s shlib library
| use_foreign_library/2 |  | 7.19 SWI-Prolog’s shlib library
| use_module/1 |  | 5.3 Using Modules
| use_module/2 |  | 5.3 Using Modules
| use_module/3 |  | 5.3 Using Modules
V |  |
| variables_within_term/3 |  | 7.23 Utilities On Terms
| variable_in_term/2 |  | 7.23 Utilities On Terms
| variant/2 |  | 7.23 Utilities On Terms
| verify_attributes/3 |  | 11.2.3 Attributed Unification
| version/0 |  | 6.22 Miscellaneous
| version/1 |  | 6.22 Miscellaneous
| vertices/2 |  | 7.28 Unweighted Graphs
| vertices_edges_to_ugraph/3 |  | 7.28 Unweighted Graphs
W |  |
| wait/2 |  | 7.22 Calling The Operating System from YAP
| when/2 |  | 10.2 Co-routining
| with_mutex/2 |  | 16.4 Thread Synchronisation
| with_output_to/2 |  | 6.9.3 Handling Input/Output of Terms
| with_output_to_chars/2 |  | 7.21 Reading From and Writing To Strings
| with_output_to_chars/3 |  | 7.21 Reading From and Writing To Strings
| with_output_to_chars/4 |  | 7.21 Reading From and Writing To Strings
| working_directory/2 |  | 7.22 Calling The Operating System from YAP
| working_directory/2 |  | 8 SWI-Prolog Emulation
| write/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| writeln/1 |  | 6.9.3 Handling Input/Output of Terms
| writeq/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| write_canonical/1 |  | 6.9.5 Input/Output Predicates applied to Streams
| write_canonical/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| write_depth/3 |  | 6.9.7 Controlling Input/Output
| write_term/2 |  | 6.9.3 Handling Input/Output of Terms
| write_term/3 |  | 6.9.5 Input/Output Predicates applied to Streams
| write_to_chars/2 |  | 7.21 Reading From and Writing To Strings
| write_to_chars/3 |  | 7.21 Reading From and Writing To Strings
Y |  |
| yap_flag/2 |  | 6.22 Miscellaneous

Jump to: | - = \ A B C D E F G H I J K L M N O P Q R S T U V W Y

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 25.1.5 YAP predicates not available in C-Prolog

These are C-Prolog built-ins not available in YAP:

`'LC'`

  The following Prolog text uses lower case letters.

`'NOLC'`

  The following Prolog text uses upper case letters only.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 25.2 Compatibility with the Quintus and SICStus Prolog systems

The Quintus Prolog system was the first Prolog compiler to use Warren’s Abstract Machine. This system was very influential in the Prolog community. Quintus Prolog implemented compilation into an abstract machine code, which was then emulated. Quintus Prolog also included several new built-ins, an extensive library, and in later releases a garbage collector. The SICStus Prolog system, developed at SICS (Swedish Institute of Computer Science), is an emulator based Prolog system largely compatible with Quintus Prolog. SICStus Prolog has evolved through several versions. The current version includes several extensions, such as an object implementation, co-routining, and constraints.

Recent work in YAP has been influenced by work in Quintus and SICStus Prolog. Wherever possible, we have tried to make YAP compatible with recent versions of these systems, and specifically of SICStus Prolog. You should use

    :- yap_flag(language, sicstus).

for maximum compatibility with SICStus Prolog.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 25.2.1 Major Differences between YAP and SICStus Prolog.

Both YAP and SICStus Prolog obey the Edinburgh Syntax and are based on the WAM. Even so, there are quite a few important differences:

- Differently from SICStus Prolog, YAP does not have a notion of interpreted code. All code in YAP is compiled.
- YAP does not support an intermediate byte-code representation, so the `fcompile/1` and `load/1` built-ins are not available in YAP.
- YAP implements escape sequences as in the ISO standard. SICStus Prolog implements Unix-like escape sequences.
- YAP implements `initialization/1` as per the ISO standard. Use `prolog_initialization/1` for the SICStus Prolog compatible built-in.
- Prolog flags are different in SICStus Prolog and in YAP.
- The SICStus Prolog `on_exception/3` and `raise_exception` built-ins correspond to the ISO built-ins `catch/3` and `throw/1`.
- The following SICStus Prolog v3 built-ins are not (currently) implemented in YAP (note that this is only a partial list): `file_search_path/2`, `stream_interrupt/3`, `reinitialize/0`, `help/0`, `help/1`, `trimcore/0`, `load_files/1`, `load_files/2`, and `require/1`.

  The previous list is incomplete. We also cannot guarantee full compatibility for other built-ins (although we will try to address any such incompatibilities). Last, SICStus Prolog is an evolving system, so one can be expect new incompatibilities to be introduced in future releases of SICStus Prolog.

- YAP allows asserting and abolishing static code during execution through the `assert_static/1` and `abolish/1` built-ins. This is not allowed in Quintus Prolog or SICStus Prolog.
- The socket predicates, although designed to be compatible with SICStus Prolog, are built-ins, not library predicates, in YAP.
- This list is incomplete.

The following differences only exist if the `language` flag is set to `yap` (the default):

- The `consult/1` predicate in YAP follows C-Prolog semantics. That is, it adds clauses to the data base, even for preexisting procedures. This is different from `consult/1` in SICStus Prolog.
- By default, the data-base in YAP follows "immediate update semantics", instead of "logical update semantics", as Quintus Prolog or SICStus Prolog do. The difference is depicted in the next example:

      :- dynamic a/1.

      ?- assert(a(1)).

      ?- retract(a(X)), X1 is X +1, assertz(a(X)).

  With immediate semantics, new clauses or entries to the data base are visible in backtracking. In this example, the first call to `retract/1` will succeed. The call to assertz/1 will then succeed. On backtracking, the system will retry `retract/1`. Because the newly asserted goal is visible to `retract/1`, it can be retracted from the data base, and `retract(a(X))` will succeed again. The process will continue generating integers for ever. Immediate semantics were used in C-Prolog.

  With logical update semantics, any additions or deletions of clauses for a goal will not affect previous activations of the goal. In the example, the call to `assertz/1` will not see the update performed by the `assertz/1`, and the query will have a single solution.

  Calling `yap_flag(update_semantics,logical)` will switch YAP to use logical update semantics.

- `dynamic/1` is a built-in, not a directive, in YAP.
- By default, YAP fails on undefined predicates. To follow default SICStus Prolog use:

      :- yap_flag(unknown,error).

- By default, directives in YAP can be called from the top level.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 25.2.2 YAP predicates fully compatible with SICStus Prolog

These are the Prolog built-ins that are fully compatible in both SICStus Prolog and YAP:

Jump to: | ! , - ; < = > @ \ A B C D E F G H I J K L M N O P Q R S T U V W

| Index Entry |  | Section
! |  |
| !/0 |  | 6.1 Control Predicates
, |  |
| ,/2 |  | 6.1 Control Predicates
- |  |
| ->/2 |  | 6.1 Control Predicates
; |  |
| ;/2 |  | 6.1 Control Predicates
< |  |
| </2 |  | 6.8 Arithmetic
= |  |
| =../2 |  | 6.4 Predicates on terms
| =/2 |  | 6.4 Predicates on terms
| =/=2 |  | 6.4 Predicates on terms
| =:=/2 |  | 6.8 Arithmetic
| =</2 |  | 6.8 Arithmetic
| ==/2 |  | 6.7 Comparing Terms
| =\=/2 |  | 6.8 Arithmetic
> |  |
| >/2 |  | 6.8 Arithmetic
| >=/2 |  | 6.8 Arithmetic
@ |  |
| @</2 |  | 6.7 Comparing Terms
| @</2 |  | 6.7 Comparing Terms
| @>/2 |  | 6.7 Comparing Terms
| @>=/2 |  | 6.7 Comparing Terms
\ |  |
| \+/1 |  | 6.1 Control Predicates
| \==/2 |  | 6.7 Comparing Terms
A |  |
| abort/0 |  | 6.1 Control Predicates
| absolute_file_name/2 |  | 6.9.1 Handling Streams and Files
| absolute_file_name/3 |  | 6.9.1 Handling Streams and Files
| add_edges/3 |  | 7.28 Unweighted Graphs
| add_to_heap/4 |  | 7.5 Heaps
| add_vertices/3 |  | 7.28 Unweighted Graphs
| aggregate/3 |  | 7.1 Aggregate
| aggregate/4 |  | 7.1 Aggregate
| aggregate_all/3 |  | 7.1 Aggregate
| aggregate_all/4 |  | 7.1 Aggregate
| append/2 |  | 7.6 List Manipulation
| append/3 |  | 7.6 List Manipulation
| arg/3 |  | 6.4 Predicates on terms
| assoc_to_list/2 |  | 7.3 Association Lists
| atom/1 |  | 6.4 Predicates on terms
| atomic/1 |  | 6.4 Predicates on terms
| atom_codes/2 |  | 6.5 Predicates on Atoms
| atom_concat/2 |  | 6.5 Predicates on Atoms
| atom_number/2 |  | 6.5 Predicates on Atoms
| atom_to_chars/2 |  | 7.21 Reading From and Writing To Strings
| atom_to_chars/3 |  | 7.21 Reading From and Writing To Strings
| atom_to_term/3 |  | 7.21 Reading From and Writing To Strings
| attribute_goal/2 |  | 11.2.4 Displaying Attributes
| at_end_of_stream/0 |  | 6.9.1 Handling Streams and Files
| at_end_of_stream/1 |  | 6.9.1 Handling Streams and Files
B |  |
| bb_delete/2 |  | 6.12 The Blackboard
| bb_get/2 |  | 6.12 The Blackboard
| bb_put/2 |  | 6.12 The Blackboard
| bb_update/3 |  | 6.12 The Blackboard
| between/3 |  | 6.8 Arithmetic
| break/0 |  | 6.1 Control Predicates
C |  |
| C/3 |  | 6.14 Grammar Rules
| call/1 |  | 6.1 Control Predicates
| callable/1 |  | 6.4 Predicates on terms
| call_cleanup/1 |  | 7.25 Call Cleanup
| call_cleanup/2 |  | 7.25 Call Cleanup
| call_residue/2 |  | 10.2 Co-routining
| call_residue_vars/2 |  | 10.2 Co-routining
| character_count/2 |  | 6.9.1 Handling Streams and Files
| char_code/2 |  | 6.6 Predicates on Characters
| char_conversion/2 |  | 6.9.3 Handling Input/Output of Terms
| cleanup_all/0 |  | 7.25 Call Cleanup
| close/1 |  | 6.9.1 Handling Streams and Files
| compare/3 |  | 6.7 Comparing Terms
| compile/1 |  | 4.1 Program loading and updating
| compile/1 |  | 4.1 Program loading and updating
| complement/2 |  | 7.28 Unweighted Graphs
| compose/3 |  | 7.28 Unweighted Graphs
| compound/1 |  | 6.4 Predicates on terms
| copy_term/2 |  | 6.4 Predicates on terms
| copy_term/3 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| copy_term_nat/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| create_mutable/2 |  | 6.16 Term Modification
| current_atom/1 |  | 6.10.2 Looking at the Data Base
| current_char_conversion/2 |  | 6.9.3 Handling Input/Output of Terms
| current_input/1 |  | 6.9.1 Handling Streams and Files
| current_key/2 |  | 6.11 Internal Data Base
| current_module/1 |  | 6.21 Predicate Information
| current_module/2 |  | 6.21 Predicate Information
| current_op/3 |  | 6.22 Miscellaneous
| current_output/1 |  | 6.9.1 Handling Streams and Files
| current_predicate/1 |  | 6.10.2 Looking at the Data Base
| current_predicate/2 |  | 6.10.2 Looking at the Data Base
| current_stream/3 |  | 6.9.1 Handling Streams and Files
| cyclic_term/1 |  | 6.4 Predicates on terms
| cyclic_term/1 |  | 7.23 Utilities On Terms
D |  |
| datime/1 |  | 7.22 Calling The Operating System from YAP
| db_reference/1 |  | 6.4 Predicates on terms
| debugging/0 |  | 21.1 Debugging Predicates
| delete/3 |  | 7.6 List Manipulation
| delete_file/1 |  | 7.22 Calling The Operating System from YAP
| delete_file/2 |  | 7.22 Calling The Operating System from YAP
| del_assoc/4 |  | 7.3 Association Lists
| del_edges/3 |  | 7.28 Unweighted Graphs
| del_max_assoc/4 |  | 7.3 Association Lists
| del_min_assoc/4 |  | 7.3 Association Lists
| del_vertices/3 |  | 7.28 Unweighted Graphs
| dgraph_del_vertex/3 |  | 7.29 Directed Graphs
| dgraph_del_vertices/3 |  | 7.29 Directed Graphs
| dif/2 |  | 10.2 Co-routining
| directory_files/2 |  | 7.22 Calling The Operating System from YAP
| discontiguous/1 (directive) |  | 4.2 Changing the Compiler’s Behavior
| display/1 |  | 6.9.3 Handling Input/Output of Terms
| display/1 |  | 6.9.3 Handling Input/Output of Terms
| display/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| duplicate_term/2 |  | 6.4 Predicates on terms
E |  |
| edges/2 |  | 7.28 Unweighted Graphs
| empty_assoc/1 |  | 7.3 Association Lists
| empty_heap/1 |  | 7.5 Heaps
| empty_queue/1 |  | 7.14 Queues
| environ/2 |  | 6.15 Access to Operating System Functionality
| environ/2 |  | 7.22 Calling The Operating System from YAP
| exception/3 |  | 6.2 Handling Undefined Procedures
| exec/3 |  | 7.22 Calling The Operating System from YAP
| expand_term/2 |  | 6.14 Grammar Rules
F |  |
| fail/0 |  | 6.1 Control Predicates
| false/0 |  | 6.1 Control Predicates
| fileerrors/0 |  | 6.9.7 Controlling Input/Output
| file_exists/1 |  | 7.22 Calling The Operating System from YAP
| file_exists/2 |  | 7.22 Calling The Operating System from YAP
| file_property/2 |  | 7.22 Calling The Operating System from YAP
| file_search_path/2 |  | 4.2 Changing the Compiler’s Behavior
| findall/3 |  | 6.13 Collecting Solutions to a Goal
| findall/4 |  | 6.13 Collecting Solutions to a Goal
| flatten/2 |  | 7.6 List Manipulation
| float/1 |  | 6.4 Predicates on terms
| flush_output/0 |  | 6.9.1 Handling Streams and Files
| flush_output/1 |  | 6.9.1 Handling Streams and Files
| foreach/2 |  | 7.1 Aggregate
| format_to_chars/3 |  | 7.21 Reading From and Writing To Strings
| format_to_chars/4 |  | 7.21 Reading From and Writing To Strings
| fragile |  | 7.25 Call Cleanup
| freeze/2 |  | 10.2 Co-routining
| free_variables/4 |  | 7.1 Aggregate
| frozen/2 |  | 10.2 Co-routining
| functor/3 |  | 6.4 Predicates on terms
G |  |
| garbage_collect/0 |  | 6.1 Control Predicates
| garbage_collect_atoms/0 |  | 6.1 Control Predicates
| gc/0 |  | 6.1 Control Predicates
| gen_assoc/3 |  | 7.3 Association Lists
| get/1 |  | 6.9.4 Handling Input/Output of Characters
| get/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| get0/1 |  | 6.9.4 Handling Input/Output of Characters
| get0/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| getrand/1 |  | 7.15 Random Number Generator
| get_assoc/3 |  | 7.3 Association Lists
| get_assoc/5 |  | 7.3 Association Lists
| get_atts/2 |  | 11.2.2 Attribute Manipulation
| get_from_heap/4 |  | 7.5 Heaps
| get_label/3 |  | 7.27 Updatable Binary Trees
| get_mutable/2 |  | 6.16 Term Modification
| get_mutable/2 |  | 6.16 Term Modification
| get_next_assoc/4 |  | 7.3 Association Lists
| get_prev_assoc/4 |  | 7.3 Association Lists
| ground/1 |  | 6.4 Predicates on terms
H |  |
| halt/0 |  | 6.1 Control Predicates
| halt/1 |  | 6.1 Control Predicates
| head_queue/2 |  | 7.14 Queues
| heap_size/2 |  | 7.5 Heaps
| heap_to_list/2 |  | 7.5 Heaps
| host_id/1 |  | 7.22 Calling The Operating System from YAP
| host_name/1 |  | 7.22 Calling The Operating System from YAP
I |  |
| if/3 |  | 6.1 Control Predicates
| incore/1 |  | 6.1 Control Predicates
| initialization/0 |  | 6.22 Miscellaneous
| integer/1 |  | 6.4 Predicates on terms
| intersection/3 |  | 7.6 List Manipulation
| is/2 |  | 6.8 Arithmetic
| is_assoc/1 |  | 7.3 Association Lists
| is_list/1 |  | 6.4 Predicates on terms
| is_mutable/1 |  | 6.16 Term Modification
J |  |
| join_queue/3 |  | 7.14 Queues
| jump_queue/3 |  | 7.14 Queues
K |  |
| keysort/2 |  | 6.7 Comparing Terms
| kill/2 |  | 7.22 Calling The Operating System from YAP
L |  |
| last/2 |  | 7.6 List Manipulation
| leash/1 |  | 21.1 Debugging Predicates
| length/2 |  | 6.7 Comparing Terms
| length_queue/2 |  | 7.14 Queues
| line_count/2 |  | 6.9.1 Handling Streams and Files
| line_position/2 |  | 6.9.1 Handling Streams and Files
| listing/1 |  | 6.10.2 Looking at the Data Base
| list_join_queue/3 |  | 7.14 Queues
| list_jump_queue/3 |  | 7.14 Queues
| list_to_assoc/2 |  | 7.3 Association Lists
| list_to_heap/2 |  | 7.5 Heaps
| list_to_ord_set/2 |  | 7.12 Ordered Sets
| list_to_queue/2 |  | 7.14 Queues
| list_to_tree/2 |  | 7.27 Updatable Binary Trees
| load_files/2 |  | 4.1 Program loading and updating
M |  |
| make_directory/2 |  | 7.22 Calling The Operating System from YAP
| make_queue/1 |  | 7.14 Queues
| map_assoc/2 |  | 7.3 Association Lists
| map_assoc/3 |  | 7.3 Association Lists
| map_tree/3 |  | 7.27 Updatable Binary Trees
| max_assoc/3 |  | 7.3 Association Lists
| max_list/2 |  | 7.6 List Manipulation
| member/2 |  | 7.6 List Manipulation
| memberchk/2 |  | 7.6 List Manipulation
| merge/3 |  | 7.12 Ordered Sets
| message_hook/3 |  | 6.3 Message Handling
| meta_predicate/1 (directive) |  | 5.4 Meta-Predicates in Modules
| min_assoc/3 |  | 7.3 Association Lists
| min_list/2 |  | 7.6 List Manipulation
| min_of_heap/3 |  | 7.5 Heaps
| min_of_heap/5 |  | 7.5 Heaps
| mktemp/2 |  | 7.22 Calling The Operating System from YAP
| module/1 |  | 5.2 Defining a New Module
| module/2 (directive) |  | 5.2 Defining a New Module
| module/3 (directive) |  | 5.2 Defining a New Module
| module_transparent/1 (directive) |  | 5.4 Meta-Predicates in Modules
| multifile/1 (directive) |  | 4.2 Changing the Compiler’s Behavior
N |  |
| name/2 |  | 6.5 Predicates on Atoms
| neighbors/3 |  | 7.28 Unweighted Graphs
| neighbours/3 |  | 7.28 Unweighted Graphs
| nl/0 |  | 6.9.4 Handling Input/Output of Characters
| nl/1 |  | 6.9.5 Input/Output Predicates applied to Streams
| nodebug/0 |  | 21.1 Debugging Predicates
| nofileerrors/0 |  | 6.9.7 Controlling Input/Output
| nogc/0 |  | 6.1 Control Predicates
| nonvar/1 |  | 6.4 Predicates on terms
| nospy/1 |  | 21.1 Debugging Predicates
| nospyall/0 |  | 21.1 Debugging Predicates
| notrace/0 |  | 21.1 Debugging Predicates
| nth/3 |  | 7.6 List Manipulation
| nth/4 |  | 7.6 List Manipulation
| nth0/3 |  | 7.6 List Manipulation
| nth0/4 |  | 7.6 List Manipulation
| nth1/3 |  | 7.6 List Manipulation
| nth1/4 |  | 7.6 List Manipulation
| number/1 |  | 6.4 Predicates on terms
| numbervars/3 |  | 6.4 Predicates on terms
| number_codes/2 |  | 6.5 Predicates on Atoms
| number_to_chars/2 |  | 7.21 Reading From and Writing To Strings
| number_to_chars/3 |  | 7.21 Reading From and Writing To Strings
| numlist/3 |  | 7.6 List Manipulation
O |  |
| on_cleanup/1 |  | 7.25 Call Cleanup
| op/3 |  | 6.22 Miscellaneous
| open/3 |  | 6.9.1 Handling Streams and Files
| open_chars_stream/2 |  | 7.21 Reading From and Writing To Strings
| ordsubset/2 |  | 7.12 Ordered Sets
| ord_add_element/3 |  | 7.12 Ordered Sets
| ord_del_element/3 |  | 7.12 Ordered Sets
| ord_disjoint/2 |  | 7.12 Ordered Sets
| ord_insert/3 |  | 7.12 Ordered Sets
| ord_intersect/2 |  | 7.12 Ordered Sets
| ord_intersect/3 |  | 7.12 Ordered Sets
| ord_intersect/4 |  | 7.12 Ordered Sets
| ord_list_to_assoc/2 |  | 7.3 Association Lists
| ord_member/2 |  | 7.12 Ordered Sets
| ord_seteq/2 |  | 7.12 Ordered Sets
| ord_setproduct/3 |  | 7.12 Ordered Sets
| ord_subtract/3 |  | 7.12 Ordered Sets
| ord_symdiff/3 |  | 7.12 Ordered Sets
| ord_union/2 |  | 7.12 Ordered Sets
| ord_union/3 |  | 7.12 Ordered Sets
| ord_union/4 |  | 7.12 Ordered Sets
P |  |
| peek_char/1 |  | 6.9.4 Handling Input/Output of Characters
| permutation/2 |  | 7.6 List Manipulation
| phrase/2 |  | 6.14 Grammar Rules
| phrase/3 |  | 6.14 Grammar Rules
| pid/1 |  | 7.22 Calling The Operating System from YAP
| plus/3 |  | 6.8 Arithmetic
| popen/3 |  | 7.22 Calling The Operating System from YAP
| portray_clause/1 |  | 6.10.2 Looking at the Data Base
| portray_clause/2 |  | 6.10.2 Looking at the Data Base
| primitive/1 |  | 6.4 Predicates on terms
| print/1 |  | 6.9.3 Handling Input/Output of Terms
| print/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| print_message/2 |  | 6.3 Message Handling
| print_message_lines/3 |  | 6.3 Message Handling
| project_attributes/2 |  | 11.2.4 Displaying Attributes
| project_attributes/2 |  | 11.2.5 Projecting Attributes
| prolog_file_name/1 |  | 4.2 Changing the Compiler’s Behavior
| prolog_flag/3 |  | 6.22 Miscellaneous
| prolog_load_context/2 |  | 6.22 Miscellaneous
| prompt/2 |  | 6.22 Miscellaneous
| put/1 |  | 6.9.4 Handling Input/Output of Characters
| put/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| put_assoc/4 |  | 7.3 Association Lists
| put_atts/2 |  | 11.2.2 Attribute Manipulation
| put_label/4 |  | 7.27 Updatable Binary Trees
Q |  |
| queue_to_list/2 |  | 7.14 Queues
R |  |
| random/1 |  | 7.15 Random Number Generator
| random/3 |  | 7.15 Random Number Generator
| randseq/3 |  | 7.15 Random Number Generator
| randset/3 |  | 7.15 Random Number Generator
| rational/1 |  | 6.4 Predicates on terms
| reachable/3 |  | 7.28 Unweighted Graphs
| read/1 |  | 6.9.3 Handling Input/Output of Terms
| read/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| read_from_chars/2 |  | 7.21 Reading From and Writing To Strings
| remove_duplicates/2 |  | 7.6 List Manipulation
| rename_file/2 |  | 7.22 Calling The Operating System from YAP
| repeat/0 |  | 6.1 Control Predicates
| restore/1 |  | 4.4 Saving and Loading Prolog States
| reverse/2 |  | 7.6 List Manipulation
S |  |
| same_length/2 |  | 7.6 List Manipulation
| save_program/1 |  | 4.4 Saving and Loading Prolog States
| save_program/2 |  | 4.4 Saving and Loading Prolog States
| see/1 |  | 6.9.2 Handling Streams and Files
| seeing/1 |  | 6.9.2 Handling Streams and Files
| seen/0 |  | 6.9.2 Handling Streams and Files
| select/3 |  | 7.6 List Manipulation
| serve_queue/3 |  | 7.14 Queues
| setrand/1 |  | 7.15 Random Number Generator
| set_input/1 |  | 6.9.1 Handling Streams and Files
| set_output/1 |  | 6.9.1 Handling Streams and Files
| set_stream_position/2 |  | 6.9.1 Handling Streams and Files
| shell/0 |  | 7.22 Calling The Operating System from YAP
| shell/1 |  | 7.22 Calling The Operating System from YAP
| shell/1 |  | 7.22 Calling The Operating System from YAP
| simple/1 |  | 6.4 Predicates on terms
| skip/1 |  | 6.9.4 Handling Input/Output of Characters
| skip/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| sleep/1 |  | 7.22 Calling The Operating System from YAP
| socket/2 |  | 6.9.8 Using Sockets From YAP
| socket/4 |  | 6.9.8 Using Sockets From YAP
| socket_accept/2 |  | 6.9.8 Using Sockets From YAP
| socket_accept/2 |  | 6.9.8 Using Sockets From YAP
| socket_accept/3 |  | 6.9.8 Using Sockets From YAP
| socket_bind/2 |  | 6.9.8 Using Sockets From YAP
| socket_buffering/4 |  | 6.9.8 Using Sockets From YAP
| socket_close/1 |  | 6.9.8 Using Sockets From YAP
| socket_connect/3 |  | 6.9.8 Using Sockets From YAP
| socket_listen/2 |  | 6.9.8 Using Sockets From YAP
| socket_select/5 |  | 6.9.8 Using Sockets From YAP
| sort/2 |  | 6.7 Comparing Terms
| source_file/1 |  | 6.22 Miscellaneous
| source_file/2 |  | 6.22 Miscellaneous
| source_location/2 |  | 6.22 Miscellaneous
| spy/1 |  | 21.1 Debugging Predicates
| stream_position/2 |  | 6.9.1 Handling Streams and Files
| stream_position_data/3 |  | 6.9.1 Handling Streams and Files
| stream_select/3 |  | 6.9.1 Handling Streams and Files
| sublist/2 |  | 7.6 List Manipulation
| subsumes/2 |  | 7.23 Utilities On Terms
| subsumes_chk/2 |  | 7.23 Utilities On Terms
| subsumes_term/2 |  | 6.4 Predicates on terms
| subtract/3 |  | 7.6 List Manipulation
| succ/3 |  | 6.8 Arithmetic
| suffix/2 |  | 7.6 List Manipulation
| sumlist/2 |  | 7.6 List Manipulation
| sum_list/2 |  | 7.6 List Manipulation
| sum_list/3 |  | 7.6 List Manipulation
| system/0 |  | 7.22 Calling The Operating System from YAP
| system/2 |  | 7.22 Calling The Operating System from YAP
| system_predicate/2 |  | 6.10.2 Looking at the Data Base
T |  |
| tab/1 |  | 6.9.4 Handling Input/Output of Characters
| tab/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| tell/1 |  | 6.9.2 Handling Streams and Files
| telling/1 |  | 6.9.2 Handling Streams and Files
| term_expansion/2 |  | 6.14 Grammar Rules
| term_hash/2 |  | 7.23 Utilities On Terms
| term_hash/4 |  | 7.23 Utilities On Terms
| term_to_atom/2 |  | 7.21 Reading From and Writing To Strings
| term_variables/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| time_out/3 |  | 7.26 Calls With Timeout
| tmpnam/1 |  | 7.22 Calling The Operating System from YAP
| told/0 |  | 6.9.2 Handling Streams and Files
| top_sort/2 |  | 7.28 Unweighted Graphs
| top_sort/3 |  | 7.28 Unweighted Graphs
| trace/0 |  | 21.1 Debugging Predicates
| transitive_closure/2 |  | 7.28 Unweighted Graphs
| transpose/3 |  | 7.28 Unweighted Graphs
| tree_size/2 |  | 7.27 Updatable Binary Trees
| tree_to_list/2 |  | 7.27 Updatable Binary Trees
| true/0 |  | 6.1 Control Predicates
| ttyget/1 |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| ttyget0/1 |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| ttynl/0 |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| ttyput/1 |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| ttyskip/1 |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| ttytab/1 |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
U |  |
| undgraph_del_vertices/3 |  | 7.30 Undirected Graphs
| unifiable/3 |  | 7.23 Utilities On Terms
| unify_with_occurs_check/2 |  | 6.4 Predicates on terms
| unknown_predicate_handler/3 |  | 6.2 Handling Undefined Procedures
| update_mutable/2 |  | 6.16 Term Modification
| use_module/1 |  | 5.3 Using Modules
| use_module/2 |  | 5.3 Using Modules
| use_module/3 |  | 5.3 Using Modules
V |  |
| var/1 |  | 6.4 Predicates on terms
| variant/2 |  | 7.23 Utilities On Terms
| verify_attributes/3 |  | 11.2.3 Attributed Unification
| version/1 |  | 6.22 Miscellaneous
| vertices/2 |  | 7.28 Unweighted Graphs
| vertices_edges_to_ugraph/3 |  | 7.28 Unweighted Graphs
W |  |
| wait/2 |  | 7.22 Calling The Operating System from YAP
| when/2 |  | 10.2 Co-routining
| with_output_to_chars/2 |  | 7.21 Reading From and Writing To Strings
| with_output_to_chars/3 |  | 7.21 Reading From and Writing To Strings
| with_output_to_chars/4 |  | 7.21 Reading From and Writing To Strings
| working_directory/2 |  | 7.22 Calling The Operating System from YAP
| write/1 |  | 6.9.3 Handling Input/Output of Terms
| write/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| writeq/1 |  | 6.9.3 Handling Input/Output of Terms
| writeq/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| write_canonical/1 |  | 6.9.5 Input/Output Predicates applied to Streams
| write_canonical/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| write_term/2 |  | 6.9.3 Handling Input/Output of Terms
| write_term/3 |  | 6.9.5 Input/Output Predicates applied to Streams
| write_to_chars/2 |  | 7.21 Reading From and Writing To Strings
| write_to_chars/3 |  | 7.21 Reading From and Writing To Strings

Jump to: | ! , - ; < = > @ \ A B C D E F G H I J K L M N O P Q R S T U V W

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 25.2.3 YAP predicates not strictly compatible with SICStus Prolog

These are YAP built-ins that are also available in SICStus Prolog, but that are not fully compatible:

Jump to: | [ A B C D E F I L N O P R S U V W

| Index Entry |  | Section
[ |  |
| [-]/1 |  | 4.1 Program loading and updating
| []/1 |  | 4.1 Program loading and updating
A |  |
| abolish/1 |  | 6.10.1 Modification of the Data Base
| abolish/2 |  | 6.10.1 Modification of the Data Base
| assert/1 |  | 6.10.1 Modification of the Data Base
| assert/2 |  | 6.10.3 Using Data Base References
| asserta/1 |  | 6.10.1 Modification of the Data Base
| asserta/2 |  | 6.10.3 Using Data Base References
| assertz/1 |  | 6.10.1 Modification of the Data Base
| assertz/2 |  | 6.10.3 Using Data Base References
| atom_chars/2 |  | 6.5 Predicates on Atoms
B |  |
| bagof/3 |  | 6.13 Collecting Solutions to a Goal
C |  |
| clause/2 |  | 6.10.1 Modification of the Data Base
| clause/3 |  | 6.10.1 Modification of the Data Base
| close/2 |  | 6.9.1 Handling Streams and Files
| current_line_number/1 |  | 6.9.1 Handling Streams and Files
| current_line_number/2 |  | 6.9.1 Handling Streams and Files
D |  |
| debug/0 |  | 21.1 Debugging Predicates
| dynamic/1 |  | 6.10 Using the Clausal Data Base
E |  |
| erase/1 |  | 6.11 Internal Data Base
| erased/1 |  | 6.11 Internal Data Base
F |  |
| format/1 |  | 6.9.3 Handling Input/Output of Terms
| format/2 |  | 6.9.3 Handling Input/Output of Terms
| format/3 |  | 6.9.3 Handling Input/Output of Terms
I |  |
| instance/2 |  | 6.11 Internal Data Base
L |  |
| listing/0 |  | 6.10.2 Looking at the Data Base
N |  |
| nth_clause/3 |  | 6.10.1 Modification of the Data Base
| nth_instance/3 |  | 6.11 Internal Data Base
| nth_instance/4 |  | 6.11 Internal Data Base
| number_chars/2 |  | 6.5 Predicates on Atoms
O |  |
| open/4 |  | 6.9.1 Handling Streams and Files
P |  |
| predicate_property/2 |  | 6.10.2 Looking at the Data Base
| prolog_initialization/1 |  | 6.22 Miscellaneous
R |  |
| read_term/2 |  | 6.9.3 Handling Input/Output of Terms
| read_term/3 |  | 6.9.5 Input/Output Predicates applied to Streams
| recorda/3 |  | 6.11 Internal Data Base
| recordaifnot/3 |  | 6.11 Internal Data Base
| recorded/3 |  | 6.11 Internal Data Base
| recordz/3 |  | 6.11 Internal Data Base
| retract/1 |  | 6.10.1 Modification of the Data Base
| retract/2 |  | 6.10.3 Using Data Base References
| retractall/1 |  | 6.10.1 Modification of the Data Base
S |  |
| setof/3 |  | 6.13 Collecting Solutions to a Goal
| statistics/0 |  | 6.22 Miscellaneous
| statistics/2 |  | 6.22 Miscellaneous
U |  |
| unknown/2 |  | 6.2 Handling Undefined Procedures
V |  |
| version/0 |  | 6.22 Miscellaneous
W |  |
| with_output_to/2 |  | 6.9.3 Handling Input/Output of Terms

Jump to: | [ A B C D E F I L N O P R S U V W

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 25.2.4 YAP predicates not available in SICStus Prolog

These are YAP built-ins not available in SICStus Prolog.

Jump to: | - = \ A B C D E F G H I K L M N O P R S T U V W Y

| Index Entry |  | Section
- |  |
| ->*/2 |  | 6.1 Control Predicates
= |  |
| =@=/2 |  | 8 SWI-Prolog Emulation
\ |  |
| \=/2 |  | 6.4 Predicates on terms
A |  |
| abolish_all_tables/0 |  | 18 Tabling
| abolish_table/1 |  | 18 Tabling
| add_to_array_element/4 |  | 6.20 Arrays
| alarm/3 |  | 6.15 Access to Operating System Functionality
| all/3 |  | 6.13 Collecting Solutions to a Goal
| always_prompt_user/0 |  | 6.9.7 Controlling Input/Output
| append/3 |  | 8 SWI-Prolog Emulation
| array/2 |  | 6.20 Arrays
| array_element/3 |  | 6.20 Arrays
| asserta_static/1 |  | 6.10.1 Modification of the Data Base
| assertz_static/1 |  | 6.10.1 Modification of the Data Base
| assert_static/1 |  | 6.10.1 Modification of the Data Base
| atomic_concat/2 |  | 6.5 Predicates on Atoms
| atomic_list_concat/2 |  | 6.5 Predicates on Atoms
| atomic_list_concat/3 |  | 6.5 Predicates on Atoms
| atom_concat/3 |  | 6.5 Predicates on Atoms
| atom_length/2 |  | 6.5 Predicates on Atoms
| attribute_goals/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| attr_portray_hook/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| attr_unify_hook/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| attvar/1 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| attvar/1 |  | 11.2.3 Attributed Unification
| avl_insert/4 |  | 7.4 AVL Trees
| avl_lookup/3 |  | 7.4 AVL Trees
| avl_new/1 |  | 7.4 AVL Trees
B |  |
| between/3 |  | 8 SWI-Prolog Emulation
| b_getval/2 |  | 6.17 Global Variables
| b_getval/2 |  | 9 SWI Global variables
| b_setval/2 |  | 6.17 Global Variables
| b_setval/2 |  | 9 SWI Global variables
C |  |
| call/n |  | 6.1 Control Predicates
| call_count_data/0 |  | 6.19 Counting Calls
| call_count_data/3 |  | 6.19 Counting Calls
| call_count_data/3 |  | 6.19 Counting Calls
| call_shared_object_function/2 |  | 23.11 Loading Object Files
| call_with_args/n |  | 6.1 Control Predicates
| catch/3 |  | 6.1 Control Predicates
| cd/0 |  | 6.15 Access to Operating System Functionality
| cd/1 |  | 6.15 Access to Operating System Functionality
| char_type/2 |  | 6.6 Predicates on Characters
| chdir/1 |  | 8 SWI-Prolog Emulation
| checklist/2 |  | 7.8 Maplist
| checknodes/3 |  | 7.8 Maplist
| close_matlab/0 |  | 7.10 MATLAB Package Interface
| close_shared_object/1 |  | 23.11 Loading Object Files
| close_static_array/1 |  | 6.20 Arrays
| code_type/2 |  | 6.6 Predicates on Characters
| compile/1 (directive) |  | 4.1 Program loading and updating
| compile_expressions/0 |  | 4.2 Changing the Compiler’s Behavior
| concat_atom/2 |  | 8 SWI-Prolog Emulation
| concat_atom/3 |  | 8 SWI-Prolog Emulation
| consult/1 |  | 4.1 Program loading and updating
| convlist/3 |  | 7.8 Maplist
| copy_line/2 |  | 7.7 Line Manipulation Utilities
| copy_line/2 |  | 7.7 Line Manipulation Utilities
| create_prolog_flag/2 |  | 6.22 Miscellaneous
| current_foreign_library/2 |  | 7.19 SWI-Prolog’s shlib library
| current_mutex/3 |  | 16.4 Thread Synchronisation
| current_prolog_flag/2 |  | 6.22 Miscellaneous
| current_thread/2 |  | 16.2 Monitoring Threads
D |  |
| db_assert/1 |  | 15.8 Insertion of Rows
| db_assert/2 |  | 15.8 Insertion of Rows
| db_close/1 |  | 15.4 Connecting to and disconnecting from a Database Server
| db_datalog_describe/1 |  | 15.11 Describing a Relation
| db_datalog_describe/2 |  | 15.11 Describing a Relation
| db_describe/1 |  | 15.11 Describing a Relation
| db_describe/2 |  | 15.11 Describing a Relation
| db_get_attributes_types/2 |  | 15.9 Types of Attributes
| db_get_attributes_types/3 |  | 15.9 Types of Attributes
| db_import/2 |  | 15.5 Accessing a Relation
| db_import/3 |  | 15.5 Accessing a Relation
| db_insert/2 |  | 15.8 Insertion of Rows
| db_insert/3 |  | 15.8 Insertion of Rows
| db_module/1 |  | 15.14 Other MYDDAS Properties
| db_my_result_set/1 |  | 15.14 Other MYDDAS Properties
| db_my_sql_mode/1 |  | 15.14 Other MYDDAS Properties
| db_my_sql_mode/2 |  | 15.14 Other MYDDAS Properties
| db_number_of_fields/2 |  | 15.10 Number of Fields
| db_number_of_fields/3 |  | 15.10 Number of Fields
| db_open/4 |  | 15.4 Connecting to and disconnecting from a Database Server
| db_open/5 |  | 15.4 Connecting to and disconnecting from a Database Server
| db_show_tables/1 |  | 15.12 Enumeration Relations
| db_show_tables/2 |  | 15.12 Enumeration Relations
| db_sql/2 |  | 15.7 Accessing Tables in Data Sources Using SQL
| db_sql/3 |  | 15.7 Accessing Tables in Data Sources Using SQL
| db_top_level/4 |  | 15.13 The MYDDAS MySQL Top Level
| db_top_level/5 |  | 15.13 The MYDDAS MySQL Top Level
| db_view/2 |  | 15.6 View Level Interface
| db_view/3 |  | 15.6 View Level Interface
| del_attr/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| del_attrs/1 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| dgraph_add_edge/4 |  | 7.29 Directed Graphs
| dgraph_add_edges/3 |  | 7.29 Directed Graphs
| dgraph_add_vertex/3 |  | 7.29 Directed Graphs
| dgraph_add_vertices/3 |  | 7.29 Directed Graphs
| dgraph_complement/2 |  | 7.29 Directed Graphs
| dgraph_compose/3 |  | 7.29 Directed Graphs
| dgraph_del_edge/4 |  | 7.29 Directed Graphs
| dgraph_del_edges/3 |  | 7.29 Directed Graphs
| dgraph_edge/2 |  | 7.29 Directed Graphs
| dgraph_edges/2 |  | 7.29 Directed Graphs
| dgraph_isomorphic/4 |  | 7.29 Directed Graphs
| dgraph_max_path/5 |  | 7.29 Directed Graphs
| dgraph_min_path/5 |  | 7.29 Directed Graphs
| dgraph_min_paths/3 |  | 7.29 Directed Graphs
| dgraph_neighbors/3 |  | 7.29 Directed Graphs
| dgraph_neighbours/3 |  | 7.29 Directed Graphs
| dgraph_new/1 |  | 7.29 Directed Graphs
| dgraph_path/3 |  | 7.29 Directed Graphs
| dgraph_path/3 |  | 7.29 Directed Graphs
| dgraph_symmetric_closure/2 |  | 7.29 Directed Graphs
| dgraph_top_sort/2 |  | 7.29 Directed Graphs
| dgraph_top_sort/3 |  | 7.29 Directed Graphs
| dgraph_to_ugraph/2 |  | 7.29 Directed Graphs
| dgraph_to_undgraph/2 |  | 7.30 Undirected Graphs
| dgraph_transitive_closure/2 |  | 7.29 Directed Graphs
| dgraph_transpose/2 |  | 7.29 Directed Graphs
| dgraph_vertices/2 |  | 7.29 Directed Graphs
| do_not_compile_expressions/0 |  | 4.2 Changing the Compiler’s Behavior
| dynamic_predicate/2 |  | 6.10 Using the Clausal Data Base
E |  |
| elif/1 |  | 4.3 Conditional Compilation
| else/0 |  | 4.3 Conditional Compilation
| endif/0 |  | 4.3 Conditional Compilation
| eraseall/1 |  | 6.11 Internal Data Base
| exclude/3 |  | 7.8 Maplist
| exists/1 |  | 6.9.7 Controlling Input/Output
| expand_exprs/2 |  | 4.2 Changing the Compiler’s Behavior
| expand_file_name/2 |  | 4.2 Changing the Compiler’s Behavior
F |  |
| fields/2 |  | 7.7 Line Manipulation Utilities
| fields/3 |  | 7.7 Line Manipulation Utilities
| file_base_name/2 |  | 6.9.1 Handling Streams and Files
| file_filter/3 |  | 7.7 Line Manipulation Utilities
| file_filter_with_init/5 |  | 7.7 Line Manipulation Utilities
| file_name_extension/3 |  | 6.9.1 Handling Streams and Files
| filter/3 |  | 7.7 Line Manipulation Utilities
| forall/2 |  | 6.1 Control Predicates
| forall/2 |  | 8.2 Forall
G |  |
| getcwd/1 |  | 6.15 Access to Operating System Functionality
| get_attr/3 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| get_attrs/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| get_byte/1 |  | 6.9.4 Handling Input/Output of Characters
| get_byte/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| get_char/1 |  | 6.9.4 Handling Input/Output of Characters
| get_char/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| get_code/1 |  | 6.9.4 Handling Input/Output of Characters
| get_code/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| get_value/2 |  | 6.11 Internal Data Base
| glue/3 |  | 7.7 Line Manipulation Utilities
| goal_expansion/3 |  | 6.14 Grammar Rules
| grow_heap/1 |  | 6.1 Control Predicates
| grow_stack/1 |  | 6.1 Control Predicates
H |  |
| hide/1 |  | 4.2 Changing the Compiler’s Behavior
| hide_predicate/1 |  | 4.2 Changing the Compiler’s Behavior
I |  |
| if/1 |  | 4.3 Conditional Compilation
| ignore/1 |  | 6.1 Control Predicates
| include/3 |  | 7.8 Maplist
| initialization/1 (directive) |  | 4.2 Changing the Compiler’s Behavior
| initialization/2 (directive) |  | 4.2 Changing the Compiler’s Behavior
| is_rbtree/1 |  | 7.17 Red-Black Trees
| is_stream/1 |  | 6.9.1 Handling Streams and Files
| is_tabled/1 |  | 18 Tabling
K |  |
| key_statistics/3 |  | 6.11 Internal Data Base
| key_statistics/4 |  | 6.11 Internal Data Base
L |  |
| library_directory/1 |  | 4.2 Changing the Compiler’s Behavior
| library_directory/1 |  | 4.2 Changing the Compiler’s Behavior
| list_concat/2 |  | 7.6 List Manipulation
| list_to_rbtree/2 |  | 7.17 Red-Black Trees
| list_to_rbtree/2 |  | 7.17 Red-Black Trees
| load_foreign_library/1 |  | 7.19 SWI-Prolog’s shlib library
| load_foreign_library/2 |  | 7.19 SWI-Prolog’s shlib library
| ls/0 |  | 6.15 Access to Operating System Functionality
M |  |
| make/0 |  | 4.1 Program loading and updating
| make_diagram/2 |  | 7.33 Block Diagram
| make_diagram/2 |  | 7.33 Block Diagram
| mapargs/3 |  | 7.8 Maplist
| maplist/2 |  | 8.1 Invoking Predicates on all Members of a List
| maplist/3 |  | 7.8 Maplist
| maplist/3 |  | 7.8 Maplist
| maplist/3 |  | 8.1 Invoking Predicates on all Members of a List
| maplist/4 |  | 7.8 Maplist
| maplist/4 |  | 8.1 Invoking Predicates on all Members of a List
| maplist/5 |  | 7.8 Maplist
| mapnodes/3 |  | 7.8 Maplist
| matlab_cells/2 |  | 7.10 MATLAB Package Interface
| matlab_cells/3 |  | 7.10 MATLAB Package Interface
| matlab_eval_string/1 |  | 7.10 MATLAB Package Interface
| matlab_eval_string/2 |  | 7.10 MATLAB Package Interface
| matlab_get_variable/2 |  | 7.10 MATLAB Package Interface
| matlab_initialized_cells/4 |  | 7.10 MATLAB Package Interface
| matlab_item/3 |  | 7.10 MATLAB Package Interface
| matlab_item/3 |  | 7.10 MATLAB Package Interface
| matlab_item/4 |  | 7.10 MATLAB Package Interface
| matlab_item/4 |  | 7.10 MATLAB Package Interface
| matlab_matrix/4 |  | 7.10 MATLAB Package Interface
| matlab_on/0 |  | 7.10 MATLAB Package Interface
| matlab_sequence/3 |  | 7.10 MATLAB Package Interface
| matlab_set/4 |  | 7.10 MATLAB Package Interface
| matlab_vector/4 |  | 7.10 MATLAB Package Interface
| matlab_zeros/2 |  | 7.10 MATLAB Package Interface
| matlab_zeros/3 |  | 7.10 MATLAB Package Interface
| matlab_zeros/4 |  | 7.10 MATLAB Package Interface
| matlab_zeros/4 |  | 7.10 MATLAB Package Interface
| matrix_add/3 |  | 7.9 Matrix Library
| matrix_agg_cols/2 |  | 7.9 Matrix Library
| matrix_agg_lines/2 |  | 7.9 Matrix Library
| matrix_arg_to_offset/3 |  | 7.9 Matrix Library
| matrix_column/3 |  | 7.9 Matrix Library
| matrix_dec/2 |  | 7.9 Matrix Library
| matrix_dec/3 |  | 7.9 Matrix Library
| matrix_dims/2 |  | 7.9 Matrix Library
| matrix_expand/3 |  | 7.9 Matrix Library
| matrix_get/3 |  | 7.9 Matrix Library
| matrix_inc/2 |  | 7.9 Matrix Library
| matrix_inc/3 |  | 7.9 Matrix Library
| matrix_max/2 |  | 7.9 Matrix Library
| matrix_maxarg/2 |  | 7.9 Matrix Library
| matrix_min/2 |  | 7.9 Matrix Library
| matrix_minarg/2 |  | 7.9 Matrix Library
| matrix_ndims/2 |  | 7.9 Matrix Library
| matrix_new/3 |  | 7.9 Matrix Library
| matrix_new/4 |  | 7.9 Matrix Library
| matrix_new_set/4 |  | 7.9 Matrix Library
| matrix_offset_to_arg/3 |  | 7.9 Matrix Library
| matrix_op/4 |  | 7.9 Matrix Library
| matrix_op/4 |  | 7.9 Matrix Library
| matrix_op_to_cols/4 |  | 7.9 Matrix Library
| matrix_op_to_lines/4 |  | 7.9 Matrix Library
| matrix_reorder/3 |  | 7.9 Matrix Library
| matrix_select/4 |  | 7.9 Matrix Library
| matrix_set/3 |  | 7.9 Matrix Library
| matrix_set_all/2 |  | 7.9 Matrix Library
| matrix_shuffle/3 |  | 7.9 Matrix Library
| matrix_size/2 |  | 7.9 Matrix Library
| matrix_sum/2 |  | 7.9 Matrix Library
| matrix_to_list/2 |  | 7.9 Matrix Library
| matrix_type/2 |  | 7.9 Matrix Library
| message_queue_create/1 |  | 16.3.1 Message Queues
| message_queue_destroy/1 |  | 16.3.1 Message Queues
| message_to_string/2 |  | 6.3 Message Handling
| mktime/2 |  | 7.22 Calling The Operating System from YAP
| mpi_barrier/0 |  | 7.32 LAM
| mpi_bcast/2 |  | 7.32 LAM
| mpi_bcast/3 |  | 7.32 LAM
| mpi_bcast/3 |  | 7.32 LAM
| mpi_comm_rank/1 |  | 7.32 LAM
| mpi_comm_size/1 |  | 7.32 LAM
| mpi_finalize/0 |  | 7.32 LAM
| mpi_gc/0 |  | 7.32 LAM
| mpi_init/0 |  | 7.32 LAM
| mpi_irecv/3 |  | 7.32 LAM
| mpi_isend/4 |  | 7.32 LAM
| mpi_recv/3 |  | 7.32 LAM
| mpi_send/3 |  | 7.32 LAM
| mpi_test/2 |  | 7.32 LAM
| mpi_test_recv/3 |  | 7.32 LAM
| mpi_version/2 |  | 7.32 LAM
| mpi_wait/2 |  | 7.32 LAM
| mpi_wait_recv/3 |  | 7.32 LAM
| mutex_create/1 |  | 16.4 Thread Synchronisation
| mutex_destroy/1 |  | 16.4 Thread Synchronisation
| mutex_lock/1 |  | 16.4 Thread Synchronisation
| mutex_statistics/0 |  | 16.2 Monitoring Threads
| mutex_trylock/1 |  | 16.4 Thread Synchronisation
| mutex_unlock/1 |  | 16.4 Thread Synchronisation
| mutex_unlock_all/0 |  | 16.4 Thread Synchronisation
N |  |
| nb_beam/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_beam_add/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_beam_close/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_beam_del/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_beam_empty/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_beam_peek/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_beam_size/2 |  | 7.11 Non-Backtrackable Data Structures
| nb_current/2 |  | 6.17 Global Variables
| nb_current/2 |  | 9 SWI Global variables
| nb_delete/1 |  | 9 SWI Global variables
| nb_delete/2 |  | 6.17 Global Variables
| nb_getval/2 |  | 6.17 Global Variables
| nb_getval/2 |  | 9 SWI Global variables
| nb_heap/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_heap_add/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_heap_close/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_heap_del/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_heap_empty/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_heap_peek/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_heap_size/2 |  | 7.11 Non-Backtrackable Data Structures
| nb_linkval/2 |  | 6.17 Global Variables
| nb_lnkarg/3 |  | 6.17 Global Variables
| nb_queue/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_queue_close/3 |  | 7.11 Non-Backtrackable Data Structures
| nb_queue_dequeue/2 |  | 7.11 Non-Backtrackable Data Structures
| nb_queue_empty/1 |  | 7.11 Non-Backtrackable Data Structures
| nb_queue_enqueue/2 |  | 7.11 Non-Backtrackable Data Structures
| nb_queue_peek/2 |  | 7.11 Non-Backtrackable Data Structures
| nb_queue_size/2 |  | 7.11 Non-Backtrackable Data Structures
| nb_setarg/3 |  | 6.17 Global Variables
| nb_setval/2 |  | 6.17 Global Variables
| nb_setval/2 |  | 9 SWI Global variables
| nb_set_shared_arg/3 |  | 6.17 Global Variables
| nb_set_shared_val/2 |  | 6.17 Global Variables
| new_variables_in_term/3 |  | 7.23 Utilities On Terms
| not/1 |  | 6.1 Control Predicates
| no_source/0 |  | 4.2 Changing the Compiler’s Behavior
| nth1/3 |  | 8 SWI-Prolog Emulation
| number_atom/2 |  | 6.5 Predicates on Atoms
O |  |
| once/1 |  | 6.1 Control Predicates
| on_signal/3 |  | 6.15 Access to Operating System Functionality
| open_shared_object/2 |  | 23.11 Loading Object Files
| open_shared_object/3 |  | 23.11 Loading Object Files
P |  |
| partition/4 |  | 7.8 Maplist
| partition/5 |  | 7.8 Maplist
| path/1 |  | 4.2 Changing the Compiler’s Behavior
| path/1 |  | 4.2 Changing the Compiler’s Behavior
| path/1 |  | 4.2 Changing the Compiler’s Behavior
| peek_byte/1 |  | 6.9.4 Handling Input/Output of Characters
| peek_byte/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| peek_char/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| peek_code/1 |  | 6.9.4 Handling Input/Output of Characters
| peek_code/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| predsort/3 |  | 6.7 Comparing Terms
| process/2 |  | 7.7 Line Manipulation Utilities
| profiled_reset/0 |  | 6.18.1 The Count Profiler
| profile_data/3 |  | 6.18.1 The Count Profiler
| profinit/0 |  | 6.18.2 Tick Profiler
| profoff/0 |  | 6.18.2 Tick Profiler
| profon/0 |  | 6.18.2 Tick Profiler
| prolog_to_os_filename/2 |  | 4.2 Changing the Compiler’s Behavior
| public/1 (directive) |  | 4.2 Changing the Compiler’s Behavior
| putenv/2 |  | 6.15 Access to Operating System Functionality
| put_attr/3 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| put_attrs/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| put_byte/1 |  | 6.9.4 Handling Input/Output of Characters
| put_byte/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| put_char/1 |  | 6.9.4 Handling Input/Output of Characters
| put_char/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| put_code/1 |  | 6.9.4 Handling Input/Output of Characters
| put_code/2 |  | 6.9.5 Input/Output Predicates applied to Streams
| pwd/0 |  | 6.15 Access to Operating System Functionality
R |  |
| rannum/1 |  | 7.13 Pseudo Random Number Integer Generator
| ranstart/0 |  | 7.13 Pseudo Random Number Integer Generator
| ranstart/1 |  | 7.13 Pseudo Random Number Integer Generator
| ranunif/2 |  | 7.13 Pseudo Random Number Integer Generator
| rb_apply/4 |  | 7.17 Red-Black Trees
| rb_clone/3 |  | 7.17 Red-Black Trees
| rb_delete/3 |  | 7.17 Red-Black Trees
| rb_delete/4 |  | 7.17 Red-Black Trees
| rb_del_max/4 |  | 7.17 Red-Black Trees
| rb_del_min/4 |  | 7.17 Red-Black Trees
| rb_empty/1 |  | 7.17 Red-Black Trees
| rb_insert/4 |  | 7.17 Red-Black Trees
| rb_insert_new/4 |  | 7.17 Red-Black Trees
| rb_keys/2 |  | 7.17 Red-Black Trees
| rb_lookup/3 |  | 7.17 Red-Black Trees
| rb_lookupall/3 |  | 7.17 Red-Black Trees
| rb_map/3 |  | 7.17 Red-Black Trees
| rb_max/3 |  | 7.17 Red-Black Trees
| rb_min/3 |  | 7.17 Red-Black Trees
| rb_new/1 |  | 7.17 Red-Black Trees
| rb_next/4 |  | 7.17 Red-Black Trees
| rb_partial_map/4 |  | 7.17 Red-Black Trees
| rb_previous/4 |  | 7.17 Red-Black Trees
| rb_size/2 |  | 7.17 Red-Black Trees
| rb_update/4 |  | 7.17 Red-Black Trees
| rb_visit/2 |  | 7.17 Red-Black Trees
| read_file_to_codes/3 |  | 7.16 Read Utilities
| read_file_to_terms/3 |  | 7.16 Read Utilities
| read_line_to_codes/2 |  | 7.16 Read Utilities
| read_line_to_codes/3 |  | 7.16 Read Utilities
| read_stream_to_codes/3 |  | 7.16 Read Utilities
| read_stream_to_codes/3 |  | 7.16 Read Utilities
| reconsult/1 |  | 4.1 Program loading and updating
| recorda/3 |  | 6.11 Internal Data Base
| recordaifnot/3 |  | 6.11 Internal Data Base
| recorda_at/3 |  | 6.11 Internal Data Base
| recordzifnot/3 |  | 6.11 Internal Data Base
| recordz_at/3 |  | 6.11 Internal Data Base
| reexport/1 |  | 5.5 Re-Exporting Predicates From Other Modules
| reexport/2 |  | 5.5 Re-Exporting Predicates From Other Modules
| regexp/3 |  | 7.18 Regular Expressions
| regexp/4 |  | 7.18 Regular Expressions
| remove_from_path/1 |  | 4.2 Changing the Compiler’s Behavior
| rename/2 |  | 6.15 Access to Operating System Functionality
| reset_op_counters/0 |  | 20 Profiling the Abstract Machine
| reset_static_array/1 |  | 6.20 Arrays
| resize_static_array/3 |  | 6.20 Arrays
S |  |
| save/1 |  | 4.4 Saving and Loading Prolog States
| save/2 |  | 4.4 Saving and Loading Prolog States
| scan_integer/3 |  | 7.7 Line Manipulation Utilities
| scan_natural/3 |  | 7.7 Line Manipulation Utilities
| search_for/2 |  | 7.7 Line Manipulation Utilities
| search_for/2 |  | 7.7 Line Manipulation Utilities
| search_for/2 |  | 7.7 Line Manipulation Utilities
| selectchk/3 |  | 7.6 List Manipulation
| selectlist/3 |  | 7.8 Maplist
| setarg/3n |  | 6.16 Term Modification
| setenv/2 |  | 8 SWI-Prolog Emulation
| setup_call_catcher_cleanup/4 |  | 7.25 Call Cleanup
| setup_call_cleanup/3 |  | 7.25 Call Cleanup
| set_prolog_flag/2 |  | 6.22 Miscellaneous
| set_value/2 |  | 6.11 Internal Data Base
| sh/0 |  | 6.15 Access to Operating System Functionality
| showprofres/0 |  | 6.18.2 Tick Profiler
| showprofres/1 |  | 6.18.2 Tick Profiler
| show_ops_by_group/1 |  | 20 Profiling the Abstract Machine
| show_op_counters/1 |  | 20 Profiling the Abstract Machine
| show_table/1 |  | 18 Tabling
| source/0 |  | 4.2 Changing the Compiler’s Behavior
| source_mode/2 |  | 4.2 Changing the Compiler’s Behavior
| splay_access/5 |  | 7.20 Splay Trees
| splay_delete/4 |  | 7.20 Splay Trees
| splay_init/3 |  | 7.20 Splay Trees
| splay_insert/4 |  | 7.20 Splay Trees
| splay_join/3 |  | 7.20 Splay Trees
| splay_split/5 |  | 7.20 Splay Trees
| split/2 |  | 7.7 Line Manipulation Utilities
| split/3 |  | 7.7 Line Manipulation Utilities
| spy_write/2 |  | 21.1 Debugging Predicates
| srandom/1 |  | 6.8 Arithmetic
| start_low_level_trace/0 |  | 19 Tracing at Low Level
| start_low_level_trace/0 |  | 19 Tracing at Low Level
| start_matlab/1 |  | 7.10 MATLAB Package Interface
| static_array/3 |  | 6.20 Arrays
| static_array/3 |  | 6.20 Arrays
| static_array_location/4 |  | 6.20 Arrays
| static_array_properties/3 |  | 6.20 Arrays
| static_array_to_term/3 |  | 6.20 Arrays
| stream_property/2 |  | 6.9.1 Handling Streams and Files
| style_check/1 |  | 4.2 Changing the Compiler’s Behavior
| style_check/1 |  | 4.2 Changing the Compiler’s Behavior
| sub_atom/5 |  | 6.5 Predicates on Atoms
| sumargs/4 |  | 7.8 Maplist
| sumlist/4 |  | 7.8 Maplist
| sumnodes/4 |  | 7.8 Maplist
| system/1 |  | 6.15 Access to Operating System Functionality
T |  |
| table/1 |  | 18 Tabling
| table_statistics/1 |  | 18 Tabling
| tabling_mode/2 |  | 18 Tabling
| tabling_statistics/0 |  | 18 Tabling
| term_attvars/2 |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| term_to_atom/2 |  | 8 SWI-Prolog Emulation
| threads/0 |  | 16.2 Monitoring Threads
| thread_at_exit/1 |  | 16.1 Creating and Destroying Prolog Threads
| thread_create/1 |  | 16.1 Creating and Destroying Prolog Threads
| thread_create/2 |  | 16.1 Creating and Destroying Prolog Threads
| thread_create/3 |  | 16.1 Creating and Destroying Prolog Threads
| thread_detach/1 |  | 16.1 Creating and Destroying Prolog Threads
| thread_exit/1 |  | 16.1 Creating and Destroying Prolog Threads
| thread_get_message/1 |  | 16.3.1 Message Queues
| thread_get_message/2 |  | 16.3.1 Message Queues
| thread_join/2 |  | 16.1 Creating and Destroying Prolog Threads
| thread_local/1 (directive) |  | 16.3.3 Threads and Dynamic Predicates
| thread_peek_message/1 |  | 16.3.1 Message Queues
| thread_peek_message/2 |  | 16.3.1 Message Queues
| thread_property/2 |  | 16.2 Monitoring Threads
| thread_self/1 |  | 16.1 Creating and Destroying Prolog Threads
| thread_send_message/1 |  | 16.3.1 Message Queues
| thread_send_message/2 |  | 16.3.1 Message Queues
| thread_setconcurrency/2 |  | 16.1 Creating and Destroying Prolog Threads
| thread_signal/2 |  | 16.3.2 Signalling Threads
| thread_sleep/1 |  | 16.1 Creating and Destroying Prolog Threads
| thread_statistics/3 |  | 16.2 Monitoring Threads
| thread_yield/0 |  | 16.1 Creating and Destroying Prolog Threads
| throw/1 |  | 6.1 Control Predicates
| time/1 |  | 6.22 Miscellaneous
| time_file/2 |  | 6.9.1 Handling Streams and Files
| tmp_file/2 |  | 7.22 Calling The Operating System from YAP
| trie_check_entry/3 |  | 7.24 Trie DataStructure
| trie_close/1 |  | 7.24 Trie DataStructure
| trie_close_all/0 |  | 7.24 Trie DataStructure
| trie_get_entry/2 |  | 7.24 Trie DataStructure
| trie_load/2 |  | 7.24 Trie DataStructure
| trie_max_stats/4 |  | 7.24 Trie DataStructure
| trie_mode/1 |  | 7.24 Trie DataStructure
| trie_open/1 |  | 7.24 Trie DataStructure
| trie_print/1 |  | 7.24 Trie DataStructure
| trie_put_entry/3 |  | 7.24 Trie DataStructure
| trie_remove_entry/1 |  | 7.24 Trie DataStructure
| trie_remove_subtree/1 |  | 7.24 Trie DataStructure
| trie_save/2 |  | 7.24 Trie DataStructure
| trie_stats/4 |  | 7.24 Trie DataStructure
| trie_usage/4 |  | 7.24 Trie DataStructure
U |  |
| ugraph_to_dgraph/2 |  | 7.29 Directed Graphs
| undgraph_add_edges/3 |  | 7.30 Undirected Graphs
| undgraph_add_vertices/3 |  | 7.30 Undirected Graphs
| undgraph_complement/2 |  | 7.30 Undirected Graphs
| undgraph_del_edges/3 |  | 7.30 Undirected Graphs
| undgraph_edge/2 |  | 7.30 Undirected Graphs
| undgraph_edges/2 |  | 7.30 Undirected Graphs
| undgraph_neighbors/3 |  | 7.30 Undirected Graphs
| undgraph_neighbours/3 |  | 7.30 Undirected Graphs
| undgraph_new/1 |  | 7.30 Undirected Graphs
| undgraph_vertices/2 |  | 7.30 Undirected Graphs
| unhide/1 |  | 4.2 Changing the Compiler’s Behavior
| unix/1 |  | 6.15 Access to Operating System Functionality
| unload_foreign_library/1 |  | 7.19 SWI-Prolog’s shlib library
| unload_foreign_library/2 |  | 7.19 SWI-Prolog’s shlib library
| update_array/3 |  | 6.20 Arrays
| use_foreign_library/1 |  | 7.19 SWI-Prolog’s shlib library
| use_foreign_library/2 |  | 7.19 SWI-Prolog’s shlib library
V |  |
| variables_within_term/3 |  | 7.23 Utilities On Terms
| variable_in_term/2 |  | 7.23 Utilities On Terms
W |  |
| with_mutex/2 |  | 16.4 Thread Synchronisation
| working_directory/2 |  | 8 SWI-Prolog Emulation
| writeln/1 |  | 6.9.3 Handling Input/Output of Terms
| write_depth/2 |  | 6.9.7 Controlling Input/Output
| write_depth/3 |  | 6.9.7 Controlling Input/Output
Y |  |
| yap_flag/2 |  | 6.22 Miscellaneous

Jump to: | - = \ A B C D E F G H I K L M N O P R S T U V W Y

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 25.3 Compatibility with the ISO Prolog standard

The Prolog standard was developed by ISO/IEC JTC1/SC22/WG17, the international standardization working group for the programming language Prolog. The book "Prolog: The Standard" by Deransart, Ed-Dbali and Cervoni gives a complete description of this standard. Development in YAP from YAP4.1.6 onwards have striven at making YAP compatible with ISO Prolog. As such:

- YAP now supports all of the built-ins required by the ISO-standard, and,
- Error-handling is as required by the standard.

YAP by default is not fully ISO standard compliant. You can set the `language` flag to `iso` to obtain very good compatibility. Setting this flag changes the following:

- By default, YAP uses "immediate update semantics" for its database, and not "logical update semantics", as per the standard, (see section Compatibility with the Quintus and SICStus Prolog systems). This affects `assert/1`, `retract/1`, and friends.

  Calling `set_prolog_flag(update_semantics,logical)` will switch YAP to use logical update semantics.

- By default, YAP implements the `atom_chars/2` (see section Predicates on terms), and `number_chars/2`, (see section Predicates on terms), built-ins as per the original Quintus Prolog definition, and not as per the ISO definition.

  Calling `set_prolog_flag(to_chars_mode,iso)` will switch YAP to use the ISO definition for `atom_chars/2` and `number_chars/2`.

- By default, YAP fails on undefined predicates. To follow the ISO Prolog standard use:

      :- set_prolog_flag(unknown,error).

- By default, YAP allows executable goals in directives. In ISO mode most directives can only be called from top level (the exceptions are `set_prolog_flag/2` and `op/3`).
- Error checking for meta-calls under ISO Prolog mode is stricter than by default.
- The `strict_iso` flag automatically enables the ISO Prolog standard. This feature should disable all features not present in the standard.

The following incompatibilities between YAP and the ISO standard are known to still exist:

- Currently, YAP does not handle overflow errors in integer operations, and handles floating-point errors only in some architectures. Otherwise, YAP follows IEEE arithmetic.

Please inform the authors on other incompatibilities that may still exist.

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# Appendix A Summary of YAP Predefined Operators

The Prolog syntax caters for operators of three main kinds:

- prefix;
- infix;
- postfix.

Each operator has precedence in the range 1 to 1200, and this precedence is used to disambiguate expressions where the structure of the term denoted is not made explicit using brackets. The operator of higher precedence is the main functor.

If there are two operators with the highest precedence, the ambiguity is solved analyzing the types of the operators. The possible infix types are: xfx, xfy, and yfx.

With an operator of type xfx both sub-expressions must have lower precedence than the operator itself, unless they are bracketed (which assigns to them zero precedence). With an operator type xfy only the left-hand sub-expression must have lower precedence. The opposite happens for yfx type.

A prefix operator can be of type fx or fy. A postfix operator can be of type xf or yf. The meaning of the notation is analogous to the above.

    a + b * c

means

    a + (b * c)

as + and * have the following types and precedences:

    :-op(500,yfx,'+').
    :-op(400,yfx,'*').

Now defining

    :-op(700,xfy,'++').
    :-op(700,xfx,'=:=').
    a ++ b =:= c

means

    a ++ (b =:= c)

The following is the list of the declarations of the predefined operators:

    :-op(1200,fx,['?-', ':-']).
    :-op(1200,xfx,[':-','-->']).
    :-op(1150,fx,[block,dynamic,mode,public,multifile,meta_predicate,
                  sequential,table,initialization]).
    :-op(1100,xfy,[';','|']).
    :-op(1050,xfy,->).
    :-op(1000,xfy,',').
    :-op(999,xfy,'.').
    :-op(900,fy,['\+', not]).
    :-op(900,fx,[nospy, spy]).
    :-op(700,xfx,[@>=,@=<,@<,@>,<,=,>,=:=,=\=,\==,>=,=<,==,\=,=..,is]).
    :-op(500,yfx,['\/','/\','+','-']).
    :-op(500,fx,['+','-']).
    :-op(400,yfx,['<<','>>','//','*','/']).
    :-op(300,xfx,mod).
    :-op(200,xfy,['^','**']).
    :-op(50,xfx,same).

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# Predicate Index

Jump to: | ! , - ; < = > @ [ \ A B C D E F G H I J K L M N O P Q R S T U V W Y

| Index Entry |  | Section
! |  |
| `!/0` |  | 6.1 Control Predicates
, |  |
| `,/2` |  | 6.1 Control Predicates
- |  |
| `->*/2` |  | 6.1 Control Predicates
| `->/2` |  | 6.1 Control Predicates
; |  |
| `;/2` |  | 6.1 Control Predicates
< |  |
| `</2` |  | 6.8 Arithmetic
= |  |
| `=../2` |  | 6.4 Predicates on terms
| `=/2` |  | 6.4 Predicates on terms
| `=/=2` |  | 6.4 Predicates on terms
| `=:=/2` |  | 6.8 Arithmetic
| `=</2` |  | 6.8 Arithmetic
| `==/2` |  | 6.7 Comparing Terms
| `=@=/2` |  | 8 SWI-Prolog Emulation
| `=\=/2` |  | 6.8 Arithmetic
> |  |
| `>/2` |  | 6.8 Arithmetic
| `>=/2` |  | 6.8 Arithmetic
@ |  |
| `@</2` |  | 6.7 Comparing Terms
| `@=</2` |  | 6.7 Comparing Terms
| `@>/2` |  | 6.7 Comparing Terms
| `@>=/2` |  | 6.7 Comparing Terms
[ |  |
| `[-]/1` |  | 4.1 Program loading and updating
| `[]/1` |  | 4.1 Program loading and updating
\ |  |
| `\+/1` |  | 6.1 Control Predicates
| `\=/2` |  | 6.4 Predicates on terms
| `\==/2` |  | 6.7 Comparing Terms
A |  |
| `abolish/1` |  | 6.10.1 Modification of the Data Base
| `abolish/2` |  | 6.10.1 Modification of the Data Base
| `abolish_all_tables/0` |  | 18 Tabling
| `abolish_table/1` |  | 18 Tabling
| `abort/0` |  | 6.1 Control Predicates
| `absolute_file_name/2` |  | 6.9.1 Handling Streams and Files
| `absolute_file_name/3` |  | 6.9.1 Handling Streams and Files
| `add_edges/3` |  | 7.28 Unweighted Graphs
| `add_to_array_element/4` |  | 6.20 Arrays
| `add_to_heap/4` |  | 7.5 Heaps
| `add_to_path/1` |  | 4.2 Changing the Compiler’s Behavior
| `add_to_path/2` |  | 4.2 Changing the Compiler’s Behavior
| `add_vertices/3` |  | 7.28 Unweighted Graphs
| `agc_margin (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `aggregate/3` |  | 7.1 Aggregate
| `aggregate/4` |  | 7.1 Aggregate
| `aggregate_all/3` |  | 7.1 Aggregate
| `aggregate_all/4` |  | 7.1 Aggregate
| `alarm/3` |  | 6.15 Access to Operating System Functionality
| `all/3` |  | 6.13 Collecting Solutions to a Goal
| `always_prompt_user/0` |  | 6.9.7 Controlling Input/Output
| `append/2` |  | 7.6 List Manipulation
| `append/3` |  | 7.6 List Manipulation
| `append/3` |  | 8 SWI-Prolog Emulation
| `arg/3` |  | 6.4 Predicates on terms
| `argv (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `array/2` |  | 6.20 Arrays
| `array_element/3` |  | 6.20 Arrays
| `assert/1` |  | 6.10.1 Modification of the Data Base
| `assert/2` |  | 6.10.3 Using Data Base References
| `asserta/1` |  | 6.10.1 Modification of the Data Base
| `asserta/2` |  | 6.10.3 Using Data Base References
| `asserta_static/1` |  | 6.10.1 Modification of the Data Base
| `assertz/1` |  | 6.10.1 Modification of the Data Base
| `assertz/2` |  | 6.10.3 Using Data Base References
| `assertz_static/1` |  | 6.10.1 Modification of the Data Base
| `assert_static/1` |  | 6.10.1 Modification of the Data Base
| `assoc_to_list/2` |  | 7.3 Association Lists
| `atom/1` |  | 6.4 Predicates on terms
| `atomic/1` |  | 6.4 Predicates on terms
| `atomic_concat/2` |  | 6.5 Predicates on Atoms
| `atomic_list_concat/2` |  | 6.5 Predicates on Atoms
| `atomic_list_concat/3` |  | 6.5 Predicates on Atoms
| `atoms (statistics/2 option)` |  | 6.22 Miscellaneous
| `atom_chars/2` |  | 6.5 Predicates on Atoms
| `atom_codes/2` |  | 6.5 Predicates on Atoms
| `atom_concat/2` |  | 6.5 Predicates on Atoms
| `atom_concat/3` |  | 6.5 Predicates on Atoms
| `atom_length/2` |  | 6.5 Predicates on Atoms
| `atom_number/2` |  | 6.5 Predicates on Atoms
| `atom_to_chars/2` |  | 7.21 Reading From and Writing To Strings
| `atom_to_chars/3` |  | 7.21 Reading From and Writing To Strings
| `atom_to_term/3` |  | 7.21 Reading From and Writing To Strings
| `attribute/1 (declaration)` |  | 11.2.1 Attribute Declarations
| `attribute_goal/2` |  | 11.2.4 Displaying Attributes
| `attribute_goals/2` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `attr_portray_hook/2` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `attr_unify_hook/2` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `attvar/1` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `attvar/1` |  | 11.2.3 Attributed Unification
| `at_end_of_stream/0` |  | 6.9.1 Handling Streams and Files
| `at_end_of_stream/1` |  | 6.9.1 Handling Streams and Files
| `avl_insert/4` |  | 7.4 AVL Trees
| `avl_lookup/3` |  | 7.4 AVL Trees
| `avl_new/1` |  | 7.4 AVL Trees
B |  |
| `bagof/3` |  | 6.13 Collecting Solutions to a Goal
| `bb_delete/2` |  | 6.12 The Blackboard
| `bb_get/2` |  | 6.12 The Blackboard
| `bb_put/2` |  | 6.12 The Blackboard
| `bb_update/3` |  | 6.12 The Blackboard
| `between/3` |  | 6.8 Arithmetic
| `between/3` |  | 8 SWI-Prolog Emulation
| `bounded (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `break/0` |  | 6.1 Control Predicates
| `b_getval/2` |  | 6.17 Global Variables
| `b_getval/2` |  | 9 SWI Global variables
| `b_setval/2` |  | 6.17 Global Variables
| `b_setval/2` |  | 9 SWI Global variables
C |  |
| `C/3` |  | 6.14 Grammar Rules
| `call/1` |  | 6.1 Control Predicates
| `call/n` |  | 6.1 Control Predicates
| `callable/1` |  | 6.4 Predicates on terms
| `call_cleanup/1` |  | 7.25 Call Cleanup
| `call_cleanup/2` |  | 7.25 Call Cleanup
| `call_counting (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `call_count_data/0` |  | 6.19 Counting Calls
| `call_count_data/3` |  | 6.19 Counting Calls
| `call_count_data/3` |  | 6.19 Counting Calls
| `call_residue/2` |  | 10.2 Co-routining
| `call_residue_vars/2` |  | 10.2 Co-routining
| `call_shared_object_function/2` |  | 23.11 Loading Object Files
| `call_with_args/n` |  | 6.1 Control Predicates
| `catch/3` |  | 6.1 Control Predicates
| `cd/0` |  | 6.15 Access to Operating System Functionality
| `cd/1` |  | 6.15 Access to Operating System Functionality
| `character_count/2` |  | 6.9.1 Handling Streams and Files
| `character_escapes (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `char_code/2` |  | 6.6 Predicates on Characters
| `char_conversion (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `char_conversion/2` |  | 6.9.3 Handling Input/Output of Terms
| `char_type/2` |  | 6.6 Predicates on Characters
| `chdir/1` |  | 8 SWI-Prolog Emulation
| `checklist/2` |  | 7.8 Maplist
| `checknodes/3` |  | 7.8 Maplist
| `clause/2` |  | 6.10.1 Modification of the Data Base
| `clause/3` |  | 6.10.1 Modification of the Data Base
| `cleanup_all/0` |  | 7.25 Call Cleanup
| `close/1` |  | 6.9.1 Handling Streams and Files
| `close/2` |  | 6.9.1 Handling Streams and Files
| `close_matlab/0` |  | 7.10 MATLAB Package Interface
| `close_shared_object/1` |  | 23.11 Loading Object Files
| `close_static_array/1` |  | 6.20 Arrays
| `code_type/2` |  | 6.6 Predicates on Characters
| `compare/3` |  | 6.7 Comparing Terms
| `compile/1` |  | 4.1 Program loading and updating
| `compile_expressions/0` |  | 4.2 Changing the Compiler’s Behavior
| `complement/2` |  | 7.28 Unweighted Graphs
| `compose/3` |  | 7.28 Unweighted Graphs
| `compound/1` |  | 6.4 Predicates on terms
| `concat_atom/2` |  | 8 SWI-Prolog Emulation
| `concat_atom/3` |  | 8 SWI-Prolog Emulation
| `consult/1` |  | 4.1 Program loading and updating
| `convlist/3` |  | 7.8 Maplist
| `copy_line/2` |  | 7.7 Line Manipulation Utilities
| `copy_line/2` |  | 7.7 Line Manipulation Utilities
| `copy_term/2` |  | 6.4 Predicates on terms
| `copy_term/3` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `copy_term_nat/2` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `cputime (statistics/2 option)` |  | 6.22 Miscellaneous
| `create_mutable/2` |  | 6.16 Term Modification
| `create_prolog_flag/2` |  | 6.22 Miscellaneous
| `current_atom/1` |  | 6.10.2 Looking at the Data Base
| `current_char_conversion/2` |  | 6.9.3 Handling Input/Output of Terms
| `current_foreign_library/2` |  | 7.19 SWI-Prolog’s shlib library
| `current_input/1` |  | 6.9.1 Handling Streams and Files
| `current_key/2` |  | 6.11 Internal Data Base
| `current_line_number/1` |  | 6.9.1 Handling Streams and Files
| `current_line_number/2` |  | 6.9.1 Handling Streams and Files
| `current_module/1` |  | 6.21 Predicate Information
| `current_module/2` |  | 6.21 Predicate Information
| `current_mutex/3` |  | 16.4 Thread Synchronisation
| `current_op/3` |  | 6.22 Miscellaneous
| `current_output/1` |  | 6.9.1 Handling Streams and Files
| `current_predicate/1` |  | 6.10.2 Looking at the Data Base
| `current_predicate/2` |  | 6.10.2 Looking at the Data Base
| `current_prolog_flag/2` |  | 6.22 Miscellaneous
| `current_stream/3` |  | 6.9.1 Handling Streams and Files
| `current_thread/2` |  | 16.2 Monitoring Threads
| `cyclic_term/1` |  | 6.4 Predicates on terms
| `cyclic_term/1` |  | 7.23 Utilities On Terms
D |  |
| `datime/1` |  | 7.22 Calling The Operating System from YAP
| `db_assert/1` |  | 15.8 Insertion of Rows
| `db_assert/2` |  | 15.8 Insertion of Rows
| `db_close/1` |  | 15.4 Connecting to and disconnecting from a Database Server
| `db_datalog_describe/1` |  | 15.11 Describing a Relation
| `db_datalog_describe/2` |  | 15.11 Describing a Relation
| `db_describe/1` |  | 15.11 Describing a Relation
| `db_describe/2` |  | 15.11 Describing a Relation
| `db_get_attributes_types/2` |  | 15.9 Types of Attributes
| `db_get_attributes_types/3` |  | 15.9 Types of Attributes
| `db_import/2` |  | 15.5 Accessing a Relation
| `db_import/3` |  | 15.5 Accessing a Relation
| `db_insert/2` |  | 15.8 Insertion of Rows
| `db_insert/3` |  | 15.8 Insertion of Rows
| `db_module/1` |  | 15.14 Other MYDDAS Properties
| `db_my_result_set/1` |  | 15.14 Other MYDDAS Properties
| `db_my_sql_mode/1` |  | 15.14 Other MYDDAS Properties
| `db_my_sql_mode/2` |  | 15.14 Other MYDDAS Properties
| `db_number_of_fields/2` |  | 15.10 Number of Fields
| `db_number_of_fields/3` |  | 15.10 Number of Fields
| `db_open/4` |  | 15.4 Connecting to and disconnecting from a Database Server
| `db_open/5` |  | 15.4 Connecting to and disconnecting from a Database Server
| `db_reference/1C` |  | 6.4 Predicates on terms
| `db_show_tables/1` |  | 15.12 Enumeration Relations
| `db_show_tables/2` |  | 15.12 Enumeration Relations
| `db_sql/2` |  | 15.7 Accessing Tables in Data Sources Using SQL
| `db_sql/3` |  | 15.7 Accessing Tables in Data Sources Using SQL
| `db_top_level/4` |  | 15.13 The MYDDAS MySQL Top Level
| `db_top_level/5` |  | 15.13 The MYDDAS MySQL Top Level
| `db_view/2` |  | 15.6 View Level Interface
| `db_view/3` |  | 15.6 View Level Interface
| `debug (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `debug/0` |  | 21.1 Debugging Predicates
| `debugger_print_options (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `debugging/0` |  | 21.1 Debugging Predicates
| `delete/3` |  | 7.6 List Manipulation
| `delete_file/1` |  | 7.22 Calling The Operating System from YAP
| `delete_file/2` |  | 7.22 Calling The Operating System from YAP
| `del_assoc/4` |  | 7.3 Association Lists
| `del_attr/2` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `del_attrs/1` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `del_edges/3` |  | 7.28 Unweighted Graphs
| `del_max_assoc/4` |  | 7.3 Association Lists
| `del_min_assoc/4` |  | 7.3 Association Lists
| `del_vertices/3` |  | 7.28 Unweighted Graphs
| `dgraph_add_edge/4` |  | 7.29 Directed Graphs
| `dgraph_add_edges/3` |  | 7.29 Directed Graphs
| `dgraph_add_vertex/3` |  | 7.29 Directed Graphs
| `dgraph_add_vertices/3` |  | 7.29 Directed Graphs
| `dgraph_complement/2` |  | 7.29 Directed Graphs
| `dgraph_compose/3` |  | 7.29 Directed Graphs
| `dgraph_del_edge/4` |  | 7.29 Directed Graphs
| `dgraph_del_edges/3` |  | 7.29 Directed Graphs
| `dgraph_del_vertex/3` |  | 7.29 Directed Graphs
| `dgraph_del_vertices/3` |  | 7.29 Directed Graphs
| `dgraph_edge/2` |  | 7.29 Directed Graphs
| `dgraph_edges/2` |  | 7.29 Directed Graphs
| `dgraph_isomorphic/4` |  | 7.29 Directed Graphs
| `dgraph_max_path/5` |  | 7.29 Directed Graphs
| `dgraph_min_path/5` |  | 7.29 Directed Graphs
| `dgraph_min_paths/3` |  | 7.29 Directed Graphs
| `dgraph_neighbors/3` |  | 7.29 Directed Graphs
| `dgraph_neighbours/3` |  | 7.29 Directed Graphs
| `dgraph_new/1` |  | 7.29 Directed Graphs
| `dgraph_path/3` |  | 7.29 Directed Graphs
| `dgraph_path/3` |  | 7.29 Directed Graphs
| `dgraph_symmetric_closure/2` |  | 7.29 Directed Graphs
| `dgraph_top_sort/2` |  | 7.29 Directed Graphs
| `dgraph_top_sort/3` |  | 7.29 Directed Graphs
| `dgraph_to_ugraph/2` |  | 7.29 Directed Graphs
| `dgraph_to_undgraph/2` |  | 7.30 Undirected Graphs
| `dgraph_transitive_closure/2` |  | 7.29 Directed Graphs
| `dgraph_transpose/2` |  | 7.29 Directed Graphs
| `dgraph_vertices/2` |  | 7.29 Directed Graphs
| `dialect (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `dif/2` |  | 10.2 Co-routining
| `directory (prolog_load_context/2 option)` |  | 6.22 Miscellaneous
| `directory_files/2` |  | 7.22 Calling The Operating System from YAP
| `discontiguous/1 (directive)` |  | 4.2 Changing the Compiler’s Behavior
| `discontiguous_warnings (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `discontiguous_warnings (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `display/1` |  | 6.9.3 Handling Input/Output of Terms
| `display/1` |  | 6.9.3 Handling Input/Output of Terms
| `display/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `dollar_as_lower_case (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `double_quotes (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `do_not_compile_expressions/0` |  | 4.2 Changing the Compiler’s Behavior
| `duplicate_term/2` |  | 6.4 Predicates on terms
| `dynamic/1` |  | 6.10 Using the Clausal Data Base
| `dynamic_code (statistics/2 option)` |  | 6.22 Miscellaneous
| `dynamic_predicate/2` |  | 6.10 Using the Clausal Data Base
E |  |
| `edges/2` |  | 7.28 Unweighted Graphs
| `elif/1 directive` |  | 4.3 Conditional Compilation
| `else/0 directive` |  | 4.3 Conditional Compilation
| `empty_assoc/1` |  | 7.3 Association Lists
| `empty_heap/1` |  | 7.5 Heaps
| `empty_queue/1` |  | 7.14 Queues
| `endif/0 directive` |  | 4.3 Conditional Compilation
| `ensure_loaded/1` |  | 4.1 Program loading and updating
| `environ/2` |  | 6.15 Access to Operating System Functionality
| `environ/2` |  | 7.22 Calling The Operating System from YAP
| `erase/1` |  | 6.11 Internal Data Base
| `eraseall/1` |  | 6.11 Internal Data Base
| `erased/1` |  | 6.11 Internal Data Base
| `exception/3` |  | 6.2 Handling Undefined Procedures
| `exclude/3` |  | 7.8 Maplist
| `exec/3` |  | 7.22 Calling The Operating System from YAP
| `executable(yap_flag/2 option)` |  | 6.22 Miscellaneous
| `exists/1` |  | 6.9.7 Controlling Input/Output
| `expand_exprs/2` |  | 4.2 Changing the Compiler’s Behavior
| `expand_file_name/2` |  | 4.2 Changing the Compiler’s Behavior
| `expand_term/2` |  | 6.14 Grammar Rules
F |  |
| `fail/0` |  | 6.1 Control Predicates
| `false/0` |  | 6.1 Control Predicates
| `fast (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `fields/2` |  | 7.7 Line Manipulation Utilities
| `fields/3` |  | 7.7 Line Manipulation Utilities
| `file (prolog_load_context/2 option)` |  | 6.22 Miscellaneous
| `file (prolog_load_context/2 option)` |  | 6.22 Miscellaneous
| `file (prolog_load_context/2 option)` |  | 6.22 Miscellaneous
| `file (prolog_load_context/2 option)` |  | 6.22 Miscellaneous
| `fileerrors (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `fileerrors/0` |  | 6.9.7 Controlling Input/Output
| `file_base_name/2` |  | 6.9.1 Handling Streams and Files
| `file_exists/1` |  | 7.22 Calling The Operating System from YAP
| `file_exists/2` |  | 7.22 Calling The Operating System from YAP
| `file_filter/3` |  | 7.7 Line Manipulation Utilities
| `file_filter_with_init/5` |  | 7.7 Line Manipulation Utilities
| `file_name_extension/3` |  | 6.9.1 Handling Streams and Files
| `file_property/2` |  | 7.22 Calling The Operating System from YAP
| `file_search_path/2` |  | 4.2 Changing the Compiler’s Behavior
| `filter/3` |  | 7.7 Line Manipulation Utilities
| `findall/3` |  | 6.13 Collecting Solutions to a Goal
| `findall/4` |  | 6.13 Collecting Solutions to a Goal
| `flatten/2` |  | 7.6 List Manipulation
| `float/1` |  | 6.4 Predicates on terms
| `float_format (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `flush_output/0` |  | 6.9.1 Handling Streams and Files
| `flush_output/1` |  | 6.9.1 Handling Streams and Files
| `forall/2` |  | 6.1 Control Predicates
| `forall/2` |  | 8.2 Forall
| `foreach/2` |  | 7.1 Aggregate
| `format/1` |  | 6.9.3 Handling Input/Output of Terms
| `format/2` |  | 6.9.3 Handling Input/Output of Terms
| `format/3` |  | 6.9.3 Handling Input/Output of Terms
| `format_to_chars/3` |  | 7.21 Reading From and Writing To Strings
| `format_to_chars/4` |  | 7.21 Reading From and Writing To Strings
| `fragile` |  | 7.25 Call Cleanup
| `freeze/2` |  | 10.2 Co-routining
| `free_variables/4` |  | 7.1 Aggregate
| `frozen/2` |  | 10.2 Co-routining
| `functor/3` |  | 6.4 Predicates on terms
G |  |
| `garbage_collect/0` |  | 6.1 Control Predicates
| `garbage_collection (statistics/2 option)` |  | 6.22 Miscellaneous
| `garbage_collect_atoms/0` |  | 6.1 Control Predicates
| `gc (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `gc/0` |  | 6.1 Control Predicates
| `gc_margin (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `gc_trace (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `generate_debugging_info (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `gen_assoc/3` |  | 7.3 Association Lists
| `get/1` |  | 6.9.4 Handling Input/Output of Characters
| `get/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `get0/1` |  | 6.9.4 Handling Input/Output of Characters
| `get0/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `getcwd/1` |  | 6.15 Access to Operating System Functionality
| `getrand/1` |  | 7.15 Random Number Generator
| `get_assoc/3` |  | 7.3 Association Lists
| `get_assoc/5` |  | 7.3 Association Lists
| `get_attr/3` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `get_attrs/2` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `get_atts/2` |  | 11.2.2 Attribute Manipulation
| `get_byte/1` |  | 6.9.4 Handling Input/Output of Characters
| `get_byte/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `get_char/1` |  | 6.9.4 Handling Input/Output of Characters
| `get_char/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `get_code/1` |  | 6.9.4 Handling Input/Output of Characters
| `get_code/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `get_from_heap/4` |  | 7.5 Heaps
| `get_label/3` |  | 7.27 Updatable Binary Trees
| `get_mutable/2` |  | 6.16 Term Modification
| `get_mutable/2` |  | 6.16 Term Modification
| `get_next_assoc/4` |  | 7.3 Association Lists
| `get_prev_assoc/4` |  | 7.3 Association Lists
| `get_value/2` |  | 6.11 Internal Data Base
| `global_stack (statistics/2 option)` |  | 6.22 Miscellaneous
| `glue/3` |  | 7.7 Line Manipulation Utilities
| `goal_expansion/3` |  | 6.14 Grammar Rules
| `ground/1` |  | 6.4 Predicates on terms
| `grow_stack/1` |  | 6.1 Control Predicates
H |  |
| `halt/0` |  | 6.1 Control Predicates
| `halt/1` |  | 6.1 Control Predicates
| `head_queue/2` |  | 7.14 Queues
| `heap (statistics/2 option)` |  | 6.22 Miscellaneous
| `heap_size/2` |  | 7.5 Heaps
| `heap_to_list/2` |  | 7.5 Heaps
| `hide/1` |  | 4.2 Changing the Compiler’s Behavior
| `hide_predicate/1` |  | 4.2 Changing the Compiler’s Behavior
| `host_id/1` |  | 7.22 Calling The Operating System from YAP
| `host_name/1` |  | 7.22 Calling The Operating System from YAP
| `host_type (yap_flag/2 option)` |  | 6.22 Miscellaneous
I |  |
| `if/1 directive` |  | 4.3 Conditional Compilation
| `if/3` |  | 6.1 Control Predicates
| `ignore/1` |  | 6.1 Control Predicates
| `include/1 (directive)` |  | 4.1 Program loading and updating
| `include/3` |  | 7.8 Maplist
| `incore/1` |  | 6.1 Control Predicates
| `index (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `informational_messages (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `initialization/0` |  | 6.22 Miscellaneous
| `initialization/1 (directive)` |  | 4.2 Changing the Compiler’s Behavior
| `initialization/2 (directive)` |  | 4.2 Changing the Compiler’s Behavior
| `instance/2` |  | 6.11 Internal Data Base
| `integer/1` |  | 6.4 Predicates on terms
| `integer_rounding_function (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `intersection/3` |  | 7.6 List Manipulation
| `is/2` |  | 6.8 Arithmetic
| `is_assoc/1` |  | 7.3 Association Lists
| `is_list/1` |  | 6.4 Predicates on terms
| `is_mutable/1` |  | 6.16 Term Modification
| `is_rbtree/1` |  | 7.17 Red-Black Trees
| `is_stream/1` |  | 6.9.1 Handling Streams and Files
| `is_tabled/1` |  | 18 Tabling
J |  |
| `join_queue/3` |  | 7.14 Queues
| `jump_queue/3` |  | 7.14 Queues
K |  |
| `keysort/2` |  | 6.7 Comparing Terms
| `key_statistics/3` |  | 6.11 Internal Data Base
| `key_statistics/4` |  | 6.11 Internal Data Base
| `kill/2` |  | 7.22 Calling The Operating System from YAP
L |  |
| `language (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `last/2` |  | 7.6 List Manipulation
| `leash/1` |  | 21.1 Debugging Predicates
| `length/2` |  | 6.7 Comparing Terms
| `length_queue/2` |  | 7.14 Queues
| `library_directory/1` |  | 4.2 Changing the Compiler’s Behavior
| `library_directory/1` |  | 4.2 Changing the Compiler’s Behavior
| `line_count/2` |  | 6.9.1 Handling Streams and Files
| `line_position/2` |  | 6.9.1 Handling Streams and Files
| `listing/0` |  | 6.10.2 Looking at the Data Base
| `listing/1` |  | 6.10.2 Looking at the Data Base
| `list_concat/2` |  | 7.6 List Manipulation
| `list_join_queue/3` |  | 7.14 Queues
| `list_jump_queue/3` |  | 7.14 Queues
| `list_to_assoc/2` |  | 7.3 Association Lists
| `list_to_heap/2` |  | 7.5 Heaps
| `list_to_ord_set/2` |  | 7.12 Ordered Sets
| `list_to_queue/2` |  | 7.14 Queues
| `list_to_rbtree/2` |  | 7.17 Red-Black Trees
| `list_to_rbtree/2` |  | 7.17 Red-Black Trees
| `list_to_tree/2` |  | 7.27 Updatable Binary Trees
| `load_files/2` |  | 4.1 Program loading and updating
| `load_foreign_library/1` |  | 7.19 SWI-Prolog’s shlib library
| `load_foreign_library/2` |  | 7.19 SWI-Prolog’s shlib library
| `local_stack (statistics/2 option)` |  | 6.22 Miscellaneous
| `ls/0` |  | 6.15 Access to Operating System Functionality
M |  |
| `make/0` |  | 4.1 Program loading and updating
| `make_diagram/2` |  | 7.33 Block Diagram
| `make_diagram/2` |  | 7.33 Block Diagram
| `make_directory/2` |  | 7.22 Calling The Operating System from YAP
| `make_queue/1` |  | 7.14 Queues
| `mapargs/3` |  | 7.8 Maplist
| `maplist/2` |  | 8.1 Invoking Predicates on all Members of a List
| `maplist/3` |  | 7.8 Maplist
| `maplist/3` |  | 7.8 Maplist
| `maplist/3` |  | 8.1 Invoking Predicates on all Members of a List
| `maplist/4` |  | 7.8 Maplist
| `maplist/4` |  | 8.1 Invoking Predicates on all Members of a List
| `maplist/5` |  | 7.8 Maplist
| `mapnodes/3` |  | 7.8 Maplist
| `map_assoc/2` |  | 7.3 Association Lists
| `map_assoc/3` |  | 7.3 Association Lists
| `map_tree/3` |  | 7.27 Updatable Binary Trees
| `matlab_cells/2` |  | 7.10 MATLAB Package Interface
| `matlab_cells/3` |  | 7.10 MATLAB Package Interface
| `matlab_eval_string/1` |  | 7.10 MATLAB Package Interface
| `matlab_eval_string/2` |  | 7.10 MATLAB Package Interface
| `matlab_get_variable/2` |  | 7.10 MATLAB Package Interface
| `matlab_initialized_cells/4` |  | 7.10 MATLAB Package Interface
| `matlab_item/3` |  | 7.10 MATLAB Package Interface
| `matlab_item/3` |  | 7.10 MATLAB Package Interface
| `matlab_item/4` |  | 7.10 MATLAB Package Interface
| `matlab_item/4` |  | 7.10 MATLAB Package Interface
| `matlab_matrix/4` |  | 7.10 MATLAB Package Interface
| `matlab_on/0` |  | 7.10 MATLAB Package Interface
| `matlab_sequence/3` |  | 7.10 MATLAB Package Interface
| `matlab_set/4` |  | 7.10 MATLAB Package Interface
| `matlab_vector/4` |  | 7.10 MATLAB Package Interface
| `matlab_zeros/2` |  | 7.10 MATLAB Package Interface
| `matlab_zeros/3` |  | 7.10 MATLAB Package Interface
| `matlab_zeros/4` |  | 7.10 MATLAB Package Interface
| `matlab_zeros/4` |  | 7.10 MATLAB Package Interface
| `matrix_add/3` |  | 7.9 Matrix Library
| `matrix_agg_cols/2` |  | 7.9 Matrix Library
| `matrix_agg_lines/2` |  | 7.9 Matrix Library
| `matrix_arg_to_offset/3` |  | 7.9 Matrix Library
| `matrix_column/3` |  | 7.9 Matrix Library
| `matrix_dec/2` |  | 7.9 Matrix Library
| `matrix_dec/3` |  | 7.9 Matrix Library
| `matrix_dims/2` |  | 7.9 Matrix Library
| `matrix_expand/3` |  | 7.9 Matrix Library
| `matrix_get/3` |  | 7.9 Matrix Library
| `matrix_inc/2` |  | 7.9 Matrix Library
| `matrix_inc/3` |  | 7.9 Matrix Library
| `matrix_max/2` |  | 7.9 Matrix Library
| `matrix_maxarg/2` |  | 7.9 Matrix Library
| `matrix_min/2` |  | 7.9 Matrix Library
| `matrix_minarg/2` |  | 7.9 Matrix Library
| `matrix_ndims/2` |  | 7.9 Matrix Library
| `matrix_new/3` |  | 7.9 Matrix Library
| `matrix_new/4` |  | 7.9 Matrix Library
| `matrix_new_set/4` |  | 7.9 Matrix Library
| `matrix_offset_to_arg/3` |  | 7.9 Matrix Library
| `matrix_op/4` |  | 7.9 Matrix Library
| `matrix_op/4` |  | 7.9 Matrix Library
| `matrix_op_to_cols/4` |  | 7.9 Matrix Library
| `matrix_op_to_lines/4` |  | 7.9 Matrix Library
| `matrix_reorder/3` |  | 7.9 Matrix Library
| `matrix_select/4` |  | 7.9 Matrix Library
| `matrix_set/3` |  | 7.9 Matrix Library
| `matrix_set_all/2` |  | 7.9 Matrix Library
| `matrix_shuffle/3` |  | 7.9 Matrix Library
| `matrix_size/2` |  | 7.9 Matrix Library
| `matrix_sum/2` |  | 7.9 Matrix Library
| `matrix_to_list/2` |  | 7.9 Matrix Library
| `matrix_type/2` |  | 7.9 Matrix Library
| `max_arity (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `max_assoc/3` |  | 7.3 Association Lists
| `max_integer (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `max_list/2` |  | 7.6 List Manipulation
| `max_tagged_integer (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `max_tagged_integer (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `max_threads (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `max_workers (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `member/2` |  | 7.6 List Manipulation
| `memberchk/2` |  | 7.6 List Manipulation
| `merge/3` |  | 7.12 Ordered Sets
| `message_hook/3` |  | 6.3 Message Handling
| `message_queue_create/1` |  | 16.3.1 Message Queues
| `message_queue_destroy/1` |  | 16.3.1 Message Queues
| `message_to_string/2` |  | 6.3 Message Handling
| `meta_predicate/1 (directive)` |  | 5.4 Meta-Predicates in Modules
| `min_assoc/3` |  | 7.3 Association Lists
| `min_integer (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `min_list/2` |  | 7.6 List Manipulation
| `min_of_heap/3` |  | 7.5 Heaps
| `min_of_heap/5` |  | 7.5 Heaps
| `mktemp/2` |  | 7.22 Calling The Operating System from YAP
| `mktime/2` |  | 7.22 Calling The Operating System from YAP
| `module (prolog_load_context/2 option)` |  | 6.22 Miscellaneous
| `module/1` |  | 5.2 Defining a New Module
| `module/2 (directive)` |  | 5.2 Defining a New Module
| `module/3 (directive)` |  | 5.2 Defining a New Module
| `module_transparent/1 (directive)` |  | 5.4 Meta-Predicates in Modules
| `mpi_barrier/0` |  | 7.32 LAM
| `mpi_bcast/2` |  | 7.32 LAM
| `mpi_bcast/3` |  | 7.32 LAM
| `mpi_bcast/3` |  | 7.32 LAM
| `mpi_comm_rank/1` |  | 7.32 LAM
| `mpi_comm_size/1` |  | 7.32 LAM
| `mpi_finalize/0` |  | 7.32 LAM
| `mpi_gc/0` |  | 7.32 LAM
| `mpi_init/0` |  | 7.32 LAM
| `mpi_irecv/3` |  | 7.32 LAM
| `mpi_isend/4` |  | 7.32 LAM
| `mpi_recv/3` |  | 7.32 LAM
| `mpi_send/3` |  | 7.32 LAM
| `mpi_test/2` |  | 7.32 LAM
| `mpi_test_recv/3` |  | 7.32 LAM
| `mpi_version/2` |  | 7.32 LAM
| `mpi_wait/2` |  | 7.32 LAM
| `mpi_wait_recv/3` |  | 7.32 LAM
| `multifile/1 (directive)` |  | 4.2 Changing the Compiler’s Behavior
| `mutex_create/1` |  | 16.4 Thread Synchronisation
| `mutex_destroy/1` |  | 16.4 Thread Synchronisation
| `mutex_lock/1` |  | 16.4 Thread Synchronisation
| `mutex_statistics/0` |  | 16.2 Monitoring Threads
| `mutex_trylock/1` |  | 16.4 Thread Synchronisation
| `mutex_unlock/1` |  | 16.4 Thread Synchronisation
| `mutex_unlock_all/0` |  | 16.4 Thread Synchronisation
N |  |
| `name/2` |  | 6.5 Predicates on Atoms
| `nb_beam/1` |  | 7.11 Non-Backtrackable Data Structures
| `nb_beam_add/3` |  | 7.11 Non-Backtrackable Data Structures
| `nb_beam_close/1` |  | 7.11 Non-Backtrackable Data Structures
| `nb_beam_del/3` |  | 7.11 Non-Backtrackable Data Structures
| `nb_beam_empty/1` |  | 7.11 Non-Backtrackable Data Structures
| `nb_beam_peek/3` |  | 7.11 Non-Backtrackable Data Structures
| `nb_beam_size/2` |  | 7.11 Non-Backtrackable Data Structures
| `nb_current/2` |  | 6.17 Global Variables
| `nb_current/2` |  | 9 SWI Global variables
| `nb_delete/1` |  | 9 SWI Global variables
| `nb_delete/2` |  | 6.17 Global Variables
| `nb_getval/2` |  | 6.17 Global Variables
| `nb_getval/2` |  | 9 SWI Global variables
| `nb_heap/1` |  | 7.11 Non-Backtrackable Data Structures
| `nb_heap_add/3` |  | 7.11 Non-Backtrackable Data Structures
| `nb_heap_close/1` |  | 7.11 Non-Backtrackable Data Structures
| `nb_heap_del/3` |  | 7.11 Non-Backtrackable Data Structures
| `nb_heap_empty/1` |  | 7.11 Non-Backtrackable Data Structures
| `nb_heap_peek/3` |  | 7.11 Non-Backtrackable Data Structures
| `nb_heap_size/2` |  | 7.11 Non-Backtrackable Data Structures
| `nb_linkarg/3` |  | 6.17 Global Variables
| `nb_linkval/2` |  | 6.17 Global Variables
| `nb_queue/1` |  | 7.11 Non-Backtrackable Data Structures
| `nb_queue_close/3` |  | 7.11 Non-Backtrackable Data Structures
| `nb_queue_dequeue/2` |  | 7.11 Non-Backtrackable Data Structures
| `nb_queue_empty/1` |  | 7.11 Non-Backtrackable Data Structures
| `nb_queue_enqueue/2` |  | 7.11 Non-Backtrackable Data Structures
| `nb_queue_peek/2` |  | 7.11 Non-Backtrackable Data Structures
| `nb_queue_size/2` |  | 7.11 Non-Backtrackable Data Structures
| `nb_setarg/3` |  | 6.17 Global Variables
| `nb_setval/2` |  | 6.17 Global Variables
| `nb_setval/2` |  | 9 SWI Global variables
| `nb_set_shared_arg/3` |  | 6.17 Global Variables
| `nb_set_shared_val/2` |  | 6.17 Global Variables
| `neighbors/3` |  | 7.28 Unweighted Graphs
| `neighbours/3` |  | 7.28 Unweighted Graphs
| `new_variables_in_term/3` |  | 7.23 Utilities On Terms
| `nl/0` |  | 6.9.4 Handling Input/Output of Characters
| `nl/1` |  | 6.9.5 Input/Output Predicates applied to Streams
| `nodebug/0` |  | 21.1 Debugging Predicates
| `nofileerrors/0` |  | 6.9.7 Controlling Input/Output
| `nogc/0` |  | 6.1 Control Predicates
| `nonvar/1` |  | 6.4 Predicates on terms
| `nospy/1` |  | 21.1 Debugging Predicates
| `nospyall/0` |  | 21.1 Debugging Predicates
| `not/1` |  | 6.1 Control Predicates
| `notrace/0` |  | 21.1 Debugging Predicates
| `no_source/0` |  | 4.2 Changing the Compiler’s Behavior
| `no_style_check/1` |  | 4.2 Changing the Compiler’s Behavior
| `nth/3` |  | 7.6 List Manipulation
| `nth/4` |  | 7.6 List Manipulation
| `nth0/3` |  | 7.6 List Manipulation
| `nth0/4` |  | 7.6 List Manipulation
| `nth1/3` |  | 7.6 List Manipulation
| `nth1/3` |  | 8 SWI-Prolog Emulation
| `nth1/4` |  | 7.6 List Manipulation
| `nth_clause/3` |  | 6.10.1 Modification of the Data Base
| `nth_instance/3` |  | 6.11 Internal Data Base
| `nth_instance/4` |  | 6.11 Internal Data Base
| `number/1` |  | 6.4 Predicates on terms
| `numbervars/3` |  | 6.4 Predicates on terms
| `number_atom/2` |  | 6.5 Predicates on Atoms
| `number_chars/2` |  | 6.5 Predicates on Atoms
| `number_codes/2` |  | 6.5 Predicates on Atoms
| `number_to_chars/2` |  | 7.21 Reading From and Writing To Strings
| `number_to_chars/3` |  | 7.21 Reading From and Writing To Strings
| `numlist/3` |  | 7.6 List Manipulation
| `n_of_integer_keys_in_bb (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `n_of_integer_keys_in_db (yap_flag/2 option)` |  | 6.22 Miscellaneous
O |  |
| `once/1` |  | 6.1 Control Predicates
| `on_cleanup/1` |  | 7.25 Call Cleanup
| `on_signal/3` |  | 6.15 Access to Operating System Functionality
| `op/3` |  | 6.22 Miscellaneous
| `open/3` |  | 6.9.1 Handling Streams and Files
| `open/4` |  | 6.9.1 Handling Streams and Files
| `open_chars_stream/2` |  | 7.21 Reading From and Writing To Strings
| `open_expands_filename (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `open_shared_object (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `open_shared_object/2` |  | 23.11 Loading Object Files
| `open_shared_object/3` |  | 23.11 Loading Object Files
| `ordsubset/2` |  | 7.12 Ordered Sets
| `ord_add_element/3` |  | 7.12 Ordered Sets
| `ord_del_element/3` |  | 7.12 Ordered Sets
| `ord_disjoint/2` |  | 7.12 Ordered Sets
| `ord_insert/3` |  | 7.12 Ordered Sets
| `ord_intersect/2` |  | 7.12 Ordered Sets
| `ord_intersect/3` |  | 7.12 Ordered Sets
| `ord_intersect/4` |  | 7.12 Ordered Sets
| `ord_list_to_assoc/2` |  | 7.3 Association Lists
| `ord_member/2` |  | 7.12 Ordered Sets
| `ord_seteq/2` |  | 7.12 Ordered Sets
| `ord_setproduct/3` |  | 7.12 Ordered Sets
| `ord_subtract/3` |  | 7.12 Ordered Sets
| `ord_symdiff/3` |  | 7.12 Ordered Sets
| `ord_union/2` |  | 7.12 Ordered Sets
| `ord_union/3` |  | 7.12 Ordered Sets
| `ord_union/4` |  | 7.12 Ordered Sets
P |  |
| `partition/4` |  | 7.8 Maplist
| `partition/5` |  | 7.8 Maplist
| `path/1` |  | 4.2 Changing the Compiler’s Behavior
| `peek_byte/1` |  | 6.9.4 Handling Input/Output of Characters
| `peek_byte/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `peek_char/1` |  | 6.9.4 Handling Input/Output of Characters
| `peek_char/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `peek_code/1` |  | 6.9.4 Handling Input/Output of Characters
| `peek_code/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `permutation/2` |  | 7.6 List Manipulation
| `phrase/2` |  | 6.14 Grammar Rules
| `phrase/3` |  | 6.14 Grammar Rules
| `pid/1` |  | 7.22 Calling The Operating System from YAP
| `plus/3` |  | 6.8 Arithmetic
| `popen/3` |  | 7.22 Calling The Operating System from YAP
| `portray_clause/1` |  | 6.10.2 Looking at the Data Base
| `portray_clause/2` |  | 6.10.2 Looking at the Data Base
| `predicate_property/2` |  | 6.10.2 Looking at the Data Base
| `predicate_statistics/4` |  | 6.10.2 Looking at the Data Base
| `predicate_statistics/4` |  | 6.10.2 Looking at the Data Base
| `predsort/3` |  | 6.7 Comparing Terms
| `primitive/1` |  | 6.4 Predicates on terms
| `print/1` |  | 6.9.3 Handling Input/Output of Terms
| `print/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `print_message/2` |  | 6.3 Message Handling
| `print_message_lines/3` |  | 6.3 Message Handling
| `process/2` |  | 7.7 Line Manipulation Utilities
| `profiled_reset/0` |  | 6.18.1 The Count Profiler
| `profile_data/3` |  | 6.18.1 The Count Profiler
| `profiling (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `profinit/0` |  | 6.18.2 Tick Profiler
| `profoff/0` |  | 6.18.2 Tick Profiler
| `profon/0` |  | 6.18.2 Tick Profiler
| `program (statistics/2 option)` |  | 6.22 Miscellaneous
| `project_attributes/2` |  | 11.2.4 Displaying Attributes
| `project_attributes/2` |  | 11.2.5 Projecting Attributes
| `prolog_file_name/2` |  | 4.2 Changing the Compiler’s Behavior
| `prolog_flag/3` |  | 6.22 Miscellaneous
| `prolog_initialization/1` |  | 6.22 Miscellaneous
| `prolog_load_context/2` |  | 6.22 Miscellaneous
| `prolog_to_os_filename/2` |  | 4.2 Changing the Compiler’s Behavior
| `prompt/2` |  | 6.22 Miscellaneous
| `prompt_alternatives_on (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `public/1 (directive)` |  | 4.2 Changing the Compiler’s Behavior
| `put/1` |  | 6.9.4 Handling Input/Output of Characters
| `put/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `putenv/2` |  | 6.15 Access to Operating System Functionality
| `put_assoc/4` |  | 7.3 Association Lists
| `put_attr/3` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `put_attrs/2` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `put_atts/2` |  | 11.2.2 Attribute Manipulation
| `put_byte/1` |  | 6.9.4 Handling Input/Output of Characters
| `put_byte/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `put_char/1` |  | 6.9.4 Handling Input/Output of Characters
| `put_char/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `put_code/1` |  | 6.9.4 Handling Input/Output of Characters
| `put_code/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `put_label/4` |  | 7.27 Updatable Binary Trees
| `pwd/0` |  | 6.15 Access to Operating System Functionality
Q |  |
| `queue_to_list/2` |  | 7.14 Queues
R |  |
| `random/1` |  | 7.15 Random Number Generator
| `random/3` |  | 7.15 Random Number Generator
| `randseq/3` |  | 7.15 Random Number Generator
| `randset/3` |  | 7.15 Random Number Generator
| `rannum/1` |  | 7.13 Pseudo Random Number Integer Generator
| `ranstart/0` |  | 7.13 Pseudo Random Number Integer Generator
| `ranstart/1` |  | 7.13 Pseudo Random Number Integer Generator
| `ranunif/2` |  | 7.13 Pseudo Random Number Integer Generator
| `rational/1` |  | 6.4 Predicates on terms
| `rb_apply/4` |  | 7.17 Red-Black Trees
| `rb_clone/3` |  | 7.17 Red-Black Trees
| `rb_delete/3` |  | 7.17 Red-Black Trees
| `rb_delete/4` |  | 7.17 Red-Black Trees
| `rb_del_max/4` |  | 7.17 Red-Black Trees
| `rb_del_min/4` |  | 7.17 Red-Black Trees
| `rb_empty/1` |  | 7.17 Red-Black Trees
| `rb_insert/4` |  | 7.17 Red-Black Trees
| `rb_keys/2` |  | 7.17 Red-Black Trees
| `rb_lookup/3` |  | 7.17 Red-Black Trees
| `rb_lookupall/3` |  | 7.17 Red-Black Trees
| `rb_map/3` |  | 7.17 Red-Black Trees
| `rb_max/3` |  | 7.17 Red-Black Trees
| `rb_min/3` |  | 7.17 Red-Black Trees
| `rb_new/1` |  | 7.17 Red-Black Trees
| `rb_next/4` |  | 7.17 Red-Black Trees
| `rb_partial_map/4` |  | 7.17 Red-Black Trees
| `rb_previous/4` |  | 7.17 Red-Black Trees
| `rb_size/2` |  | 7.17 Red-Black Trees
| `rb_update/4` |  | 7.17 Red-Black Trees
| `rb_visit/2` |  | 7.17 Red-Black Trees
| `reachable/3` |  | 7.28 Unweighted Graphs
| `read/1` |  | 6.9.3 Handling Input/Output of Terms
| `read/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `read_file_to_codes/3` |  | 7.16 Read Utilities
| `read_file_to_terms/3` |  | 7.16 Read Utilities
| `read_from_chars/2` |  | 7.21 Reading From and Writing To Strings
| `read_line_to_codes/2` |  | 7.16 Read Utilities
| `read_line_to_codes/3` |  | 7.16 Read Utilities
| `read_stream_to_codes/3` |  | 7.16 Read Utilities
| `read_stream_to_codes/3` |  | 7.16 Read Utilities
| `read_term/2` |  | 6.9.3 Handling Input/Output of Terms
| `read_term/3` |  | 6.9.5 Input/Output Predicates applied to Streams
| `reconsult/1` |  | 4.1 Program loading and updating
| `recorda/3` |  | 6.11 Internal Data Base
| `recorda/3` |  | 6.11 Internal Data Base
| `recordaifnot/3` |  | 6.11 Internal Data Base
| `recordaifnot/3` |  | 6.11 Internal Data Base
| `recorda_at/3` |  | 6.11 Internal Data Base
| `recorded/3` |  | 6.11 Internal Data Base
| `recordz/3` |  | 6.11 Internal Data Base
| `recordzifnot/3` |  | 6.11 Internal Data Base
| `recordz_at/3` |  | 6.11 Internal Data Base
| `reexport/1` |  | 5.5 Re-Exporting Predicates From Other Modules
| `reexport/2` |  | 5.5 Re-Exporting Predicates From Other Modules
| `regexp/3` |  | 7.18 Regular Expressions
| `regexp/4` |  | 7.18 Regular Expressions
| `remove_duplicates/2` |  | 7.6 List Manipulation
| `remove_from_path/1` |  | 4.2 Changing the Compiler’s Behavior
| `rename/2` |  | 6.15 Access to Operating System Functionality
| `rename_file/2` |  | 7.22 Calling The Operating System from YAP
| `repeat/0` |  | 6.1 Control Predicates
| `reset_op_counters/0` |  | 20 Profiling the Abstract Machine
| `reset_static_array/1` |  | 6.20 Arrays
| `resize_static_array/3` |  | 6.20 Arrays
| `restore/1` |  | 4.4 Saving and Loading Prolog States
| `retract/1` |  | 6.10.1 Modification of the Data Base
| `retract/2` |  | 6.10.3 Using Data Base References
| `retractall/1` |  | 6.10.1 Modification of the Data Base
| `reverse/2` |  | 7.6 List Manipulation
| `runtime (statistics/2 option)` |  | 6.22 Miscellaneous
S |  |
| `same_length/2` |  | 7.6 List Manipulation
| `save/1` |  | 4.4 Saving and Loading Prolog States
| `save/2` |  | 4.4 Saving and Loading Prolog States
| `save_program/1` |  | 4.4 Saving and Loading Prolog States
| `save_program/2` |  | 4.4 Saving and Loading Prolog States
| `scan_integer/3` |  | 7.7 Line Manipulation Utilities
| `scan_natural/3` |  | 7.7 Line Manipulation Utilities
| `search_for/2` |  | 7.7 Line Manipulation Utilities
| `search_for/2` |  | 7.7 Line Manipulation Utilities
| `search_for/2` |  | 7.7 Line Manipulation Utilities
| `see/1` |  | 6.9.2 Handling Streams and Files
| `seeing/1` |  | 6.9.2 Handling Streams and Files
| `seen/0` |  | 6.9.2 Handling Streams and Files
| `select/3` |  | 7.6 List Manipulation
| `selectchk/3` |  | 7.6 List Manipulation
| `selectlist/3` |  | 7.8 Maplist
| `serve_queue/3` |  | 7.14 Queues
| `setarg/3n` |  | 6.16 Term Modification
| `setenv/2` |  | 8 SWI-Prolog Emulation
| `setof/3` |  | 6.13 Collecting Solutions to a Goal
| `setrand/1` |  | 7.15 Random Number Generator
| `setup_call_catcher_cleanup/4` |  | 7.25 Call Cleanup
| `setup_call_cleanup/3` |  | 7.25 Call Cleanup
| `set_input/1` |  | 6.9.1 Handling Streams and Files
| `set_output/1` |  | 6.9.1 Handling Streams and Files
| `set_prolog_flag/2` |  | 6.22 Miscellaneous
| `set_stream_position/2` |  | 6.9.1 Handling Streams and Files
| `set_value/2` |  | 6.11 Internal Data Base
| `sh/0` |  | 6.15 Access to Operating System Functionality
| `shared_object_search_path (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `shell/0` |  | 7.22 Calling The Operating System from YAP
| `shell/1` |  | 7.22 Calling The Operating System from YAP
| `shell/1` |  | 7.22 Calling The Operating System from YAP
| `showprofres/0` |  | 6.18.2 Tick Profiler
| `showprofres/1` |  | 6.18.2 Tick Profiler
| `show_ops_by_group/1` |  | 20 Profiling the Abstract Machine
| `show_op_counters/1` |  | 20 Profiling the Abstract Machine
| `show_table/1` |  | 18 Tabling
| `simple/1` |  | 6.4 Predicates on terms
| `singletons/1 (read_term/2 option)` |  | 6.9.3 Handling Input/Output of Terms
| `single_var_warnings (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `skip/1` |  | 6.9.4 Handling Input/Output of Characters
| `skip/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `sleep/1` |  | 7.22 Calling The Operating System from YAP
| `socket/2` |  | 6.9.8 Using Sockets From YAP
| `socket/4` |  | 6.9.8 Using Sockets From YAP
| `socket_accept/2` |  | 6.9.8 Using Sockets From YAP
| `socket_accept/2` |  | 6.9.8 Using Sockets From YAP
| `socket_accept/3` |  | 6.9.8 Using Sockets From YAP
| `socket_bind/2` |  | 6.9.8 Using Sockets From YAP
| `socket_buffering/4` |  | 6.9.8 Using Sockets From YAP
| `socket_close/1` |  | 6.9.8 Using Sockets From YAP
| `socket_connect/3` |  | 6.9.8 Using Sockets From YAP
| `socket_listen/2` |  | 6.9.8 Using Sockets From YAP
| `socket_select/5` |  | 6.9.8 Using Sockets From YAP
| `sort/2` |  | 6.7 Comparing Terms
| `source/0` |  | 4.2 Changing the Compiler’s Behavior
| `source_file/1` |  | 6.22 Miscellaneous
| `source_file/2` |  | 6.22 Miscellaneous
| `source_location/2` |  | 6.22 Miscellaneous
| `source_mode/2` |  | 4.2 Changing the Compiler’s Behavior
| `splay_access/5` |  | 7.20 Splay Trees
| `splay_delete/4` |  | 7.20 Splay Trees
| `splay_init/3` |  | 7.20 Splay Trees
| `splay_insert/4` |  | 7.20 Splay Trees
| `splay_join/3` |  | 7.20 Splay Trees
| `splay_split/5` |  | 7.20 Splay Trees
| `split/2` |  | 7.7 Line Manipulation Utilities
| `split/3` |  | 7.7 Line Manipulation Utilities
| `spy/1` |  | 21.1 Debugging Predicates
| `spy_write/2` |  | 21.1 Debugging Predicates
| `srandom/1` |  | 6.8 Arithmetic
| `stack_dump_on_error (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `stack_shifts (statistics/2 option)` |  | 6.22 Miscellaneous
| `start_low_level_trace/0` |  | 19 Tracing at Low Level
| `start_low_level_trace/0` |  | 19 Tracing at Low Level
| `start_matlab/1` |  | 7.10 MATLAB Package Interface
| `static_array/3` |  | 6.20 Arrays
| `static_array/3` |  | 6.20 Arrays
| `static_array_location/4` |  | 6.20 Arrays
| `static_array_properties/3` |  | 6.20 Arrays
| `static_array_to_term/3` |  | 6.20 Arrays
| `static_code (statistics/2 option)` |  | 6.22 Miscellaneous
| `statistics/0` |  | 6.22 Miscellaneous
| `statistics/2` |  | 6.22 Miscellaneous
| `stream_position/2` |  | 6.9.1 Handling Streams and Files
| `stream_position_data/3` |  | 6.9.1 Handling Streams and Files
| `stream_property/2` |  | 6.9.1 Handling Streams and Files
| `stream_select/3` |  | 6.9.1 Handling Streams and Files
| `strict_iso (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `style_check/1` |  | 4.2 Changing the Compiler’s Behavior
| `sublist/2` |  | 7.6 List Manipulation
| `subsumes/2` |  | 7.23 Utilities On Terms
| `subsumes_chk/2` |  | 7.23 Utilities On Terms
| `subsumes_term/2` |  | 6.4 Predicates on terms
| `subtract/3` |  | 7.6 List Manipulation
| `sub_atom/5` |  | 6.5 Predicates on Atoms
| `succ/3` |  | 6.8 Arithmetic
| `suffix/2` |  | 7.6 List Manipulation
| `sumargs/4` |  | 7.8 Maplist
| `sumlist/2` |  | 7.6 List Manipulation
| `sumlist/4` |  | 7.8 Maplist
| `sumnodes/4` |  | 7.8 Maplist
| `sum_list/2` |  | 7.6 List Manipulation
| `sum_list/3` |  | 7.6 List Manipulation
| `syntax_errors (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `syntax_errors/1 (read_term/2 option)` |  | 6.9.3 Handling Input/Output of Terms
| `system/0` |  | 7.22 Calling The Operating System from YAP
| `system/1` |  | 6.15 Access to Operating System Functionality
| `system/2` |  | 7.22 Calling The Operating System from YAP
| `system_options (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `system_predicate/2` |  | 6.10.2 Looking at the Data Base
T |  |
| `tab/1` |  | 6.9.4 Handling Input/Output of Characters
| `tab/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `table/1` |  | 18 Tabling
| `table_statistics/1` |  | 18 Tabling
| `tabling_mode (yap_flag/2 option)` |  | 18 Tabling
| `tabling_mode/2` |  | 18 Tabling
| `tabling_statistics/0` |  | 18 Tabling
| `tell/1` |  | 6.9.2 Handling Streams and Files
| `telling/1` |  | 6.9.2 Handling Streams and Files
| `term_attvars/2` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `term_expansion/2` |  | 6.14 Grammar Rules
| `term_hash/2` |  | 7.23 Utilities On Terms
| `term_hash/4` |  | 7.23 Utilities On Terms
| `term_position/1 (read_term/2 option)` |  | 6.9.3 Handling Input/Output of Terms
| `term_to_atom/2` |  | 7.21 Reading From and Writing To Strings
| `term_to_atom/2` |  | 8 SWI-Prolog Emulation
| `term_variables/2` |  | 11.1 hProlog and SWI-Prolog style Attribute Declarations
| `threads/0` |  | 16.2 Monitoring Threads
| `thread_at_exit/1` |  | 16.1 Creating and Destroying Prolog Threads
| `thread_create/1` |  | 16.1 Creating and Destroying Prolog Threads
| `thread_create/2` |  | 16.1 Creating and Destroying Prolog Threads
| `thread_create/3` |  | 16.1 Creating and Destroying Prolog Threads
| `thread_detach/1` |  | 16.1 Creating and Destroying Prolog Threads
| `thread_exit/1` |  | 16.1 Creating and Destroying Prolog Threads
| `thread_get_message/1` |  | 16.3.1 Message Queues
| `thread_get_message/2` |  | 16.3.1 Message Queues
| `thread_join/2` |  | 16.1 Creating and Destroying Prolog Threads
| `thread_local/1 (directive)` |  | 16.3.3 Threads and Dynamic Predicates
| `thread_peek_message/1` |  | 16.3.1 Message Queues
| `thread_peek_message/2` |  | 16.3.1 Message Queues
| `thread_property/2` |  | 16.2 Monitoring Threads
| `thread_self/1` |  | 16.1 Creating and Destroying Prolog Threads
| `thread_send_message/1` |  | 16.3.1 Message Queues
| `thread_send_message/2` |  | 16.3.1 Message Queues
| `thread_setconcurrency/2` |  | 16.1 Creating and Destroying Prolog Threads
| `thread_signal/2` |  | 16.3.2 Signalling Threads
| `thread_sleep/1` |  | 16.1 Creating and Destroying Prolog Threads
| `thread_statistics/3` |  | 16.2 Monitoring Threads
| `thread_yield/0` |  | 16.1 Creating and Destroying Prolog Threads
| `throw/1` |  | 6.1 Control Predicates
| `time/1` |  | 6.22 Miscellaneous
| `time_file/2` |  | 6.9.1 Handling Streams and Files
| `time_out/3` |  | 7.26 Calls With Timeout
| `tmpnam/1` |  | 7.22 Calling The Operating System from YAP
| `tmp_file/2` |  | 7.22 Calling The Operating System from YAP
| `told/0` |  | 6.9.2 Handling Streams and Files
| `toplevel_hook (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `toplevel_print_options (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `top_sort/2` |  | 7.28 Unweighted Graphs
| `top_sort/3` |  | 7.28 Unweighted Graphs
| `to_chars_modes (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `trace/0` |  | 21.1 Debugging Predicates
| `trail (statistics/2 option)` |  | 6.22 Miscellaneous
| `transitive_closure/2` |  | 7.28 Unweighted Graphs
| `transpose/3` |  | 7.28 Unweighted Graphs
| `tree_size/2` |  | 7.27 Updatable Binary Trees
| `tree_to_list/2` |  | 7.27 Updatable Binary Trees
| `trie_check_entry/3` |  | 7.24 Trie DataStructure
| `trie_close/1` |  | 7.24 Trie DataStructure
| `trie_close_all/0` |  | 7.24 Trie DataStructure
| `trie_get_entry/2` |  | 7.24 Trie DataStructure
| `trie_load/2` |  | 7.24 Trie DataStructure
| `trie_max_stats/4` |  | 7.24 Trie DataStructure
| `trie_mode/1` |  | 7.24 Trie DataStructure
| `trie_open/1` |  | 7.24 Trie DataStructure
| `trie_print/1` |  | 7.24 Trie DataStructure
| `trie_put_entry/3` |  | 7.24 Trie DataStructure
| `trie_remove_entry/1` |  | 7.24 Trie DataStructure
| `trie_remove_subtree/1` |  | 7.24 Trie DataStructure
| `trie_save/2` |  | 7.24 Trie DataStructure
| `trie_stats/4` |  | 7.24 Trie DataStructure
| `trie_usage/4` |  | 7.24 Trie DataStructure
| `true/0` |  | 6.1 Control Predicates
| `ttyget/1` |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| `ttyget0/1` |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| `ttynl/0` |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| `ttyput/1` |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| `ttyskip/1` |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| `ttytab/1` |  | 6.9.6 Compatible C-Prolog predicates for Terminal I/O
| `typein_module (yap_flag/2 option)` |  | 6.22 Miscellaneous
U |  |
| `ugraph_to_dgraph/2` |  | 7.29 Directed Graphs
| `undgraph_add_edges/3` |  | 7.30 Undirected Graphs
| `undgraph_add_vertices/3` |  | 7.30 Undirected Graphs
| `undgraph_complement/2` |  | 7.30 Undirected Graphs
| `undgraph_del_edges/3` |  | 7.30 Undirected Graphs
| `undgraph_del_vertices/3` |  | 7.30 Undirected Graphs
| `undgraph_edge/2` |  | 7.30 Undirected Graphs
| `undgraph_edges/2` |  | 7.30 Undirected Graphs
| `undgraph_neighbors/3` |  | 7.30 Undirected Graphs
| `undgraph_neighbours/3` |  | 7.30 Undirected Graphs
| `undgraph_new/1` |  | 7.30 Undirected Graphs
| `undgraph_vertices/2` |  | 7.30 Undirected Graphs
| `unhide/1` |  | 4.2 Changing the Compiler’s Behavior
| `unifiable/3` |  | 7.23 Utilities On Terms
| `unify_with_occurs_check/2` |  | 6.4 Predicates on terms
| `unix (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `unix/1` |  | 6.15 Access to Operating System Functionality
| `unknown (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `unknown/2` |  | 6.2 Handling Undefined Procedures
| `unknown_predicate_handler/3` |  | 6.2 Handling Undefined Procedures
| `unload_foreign_library/1` |  | 7.19 SWI-Prolog’s shlib library
| `unload_foreign_library/2` |  | 7.19 SWI-Prolog’s shlib library
| `update_array/3` |  | 6.20 Arrays
| `update_mutable/2` |  | 6.16 Term Modification
| `update_semantics (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `user_error (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `user_flags (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `user_input (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `user_output (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `use_foreign_library/1` |  | 7.19 SWI-Prolog’s shlib library
| `use_foreign_library/2` |  | 7.19 SWI-Prolog’s shlib library
| `use_module/1` |  | 5.3 Using Modules
| `use_module/2` |  | 5.3 Using Modules
| `use_module/3` |  | 5.3 Using Modules
V |  |
| `var/1` |  | 6.4 Predicates on terms
| `variables/1 (read_term/2 option)` |  | 6.9.3 Handling Input/Output of Terms
| `variables_within_term/3` |  | 7.23 Utilities On Terms
| `variable_in_term/2` |  | 7.23 Utilities On Terms
| `variable_names/1 (read_term/2 option)` |  | 6.9.3 Handling Input/Output of Terms
| `variant/2` |  | 7.23 Utilities On Terms
| `verbose (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `verbose_load (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `verify_attributes/3` |  | 11.2.3 Attributed Unification
| `version (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `version/0` |  | 6.22 Miscellaneous
| `version/1` |  | 6.22 Miscellaneous
| `version_data (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `vertices/2` |  | 7.28 Unweighted Graphs
| `vertices_edges_to_ugraph/3` |  | 7.28 Unweighted Graphs
W |  |
| `wait/2` |  | 7.22 Calling The Operating System from YAP
| `walltime (statistics/2 option)` |  | 6.22 Miscellaneous
| `when/2` |  | 10.2 Co-routining
| `windoes (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `with_mutex/2` |  | 16.4 Thread Synchronisation
| `with_output_to/2` |  | 6.9.3 Handling Input/Output of Terms
| `with_output_to_chars/2` |  | 7.21 Reading From and Writing To Strings
| `with_output_to_chars/3` |  | 7.21 Reading From and Writing To Strings
| `with_output_to_chars/4` |  | 7.21 Reading From and Writing To Strings
| `working_directory/2` |  | 7.22 Calling The Operating System from YAP
| `working_directory/2` |  | 8 SWI-Prolog Emulation
| `write/1` |  | 6.9.3 Handling Input/Output of Terms
| `write/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `writeln/1` |  | 6.9.3 Handling Input/Output of Terms
| `writeq/1` |  | 6.9.3 Handling Input/Output of Terms
| `writeq/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `write_canonical/1` |  | 6.9.5 Input/Output Predicates applied to Streams
| `write_canonical/2` |  | 6.9.5 Input/Output Predicates applied to Streams
| `write_depth/2` |  | 6.9.7 Controlling Input/Output
| `write_depth/3` |  | 6.9.7 Controlling Input/Output
| `write_strings (yap_flag/2 option)` |  | 6.22 Miscellaneous
| `write_term/2` |  | 6.9.3 Handling Input/Output of Terms
| `write_term/3` |  | 6.9.5 Input/Output Predicates applied to Streams
| `write_to_chars/2` |  | 7.21 Reading From and Writing To Strings
| `write_to_chars/3` |  | 7.21 Reading From and Writing To Strings
Y |  |
| `YAPBINDIR` |  | 2.1 Running YAP Interactively
| `YAPLIBDIR` |  | 2.1 Running YAP Interactively
| `YAPSHAREDIR` |  | 2.1 Running YAP Interactively
| `YAP_AddressFromSlot (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_AGCHook (C-Interface function)` |  | 23.1 Terms
| `YAP_AllocSpaceFromYAP (C-Interface function)` |  | 23.4 Memory Allocation
| `YAP_ArgOfTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_ArgsOfTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_ArgsToSlots (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_ArityOfFunctor (C-Interface function)` |  | 23.1 Terms
| `YAP_AsyncThrow (C-Interface function)` |  | 23.9 Miscellaneous C Functions
| `YAP_AtomGetHold (C-Interface function)` |  | 23.1 Terms
| `YAP_AtomName (C-Interface function)` |  | 23.1 Terms
| `YAP_AtomNameLength (C-Interface function)` |  | 23.1 Terms
| `YAP_AtomOfTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_AtomReleaseHold (C-Interface function)` |  | 23.1 Terms
| `YAP_AtomToPred (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_BigNumOfTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_BufferToAtomList (C-Interface function)` |  | 23.3 Strings
| `YAP_BufferToDiffList (C-Interface function)` |  | 23.3 Strings
| `YAP_BufferToString (C-Interface function)` |  | 23.3 Strings
| `YAP_CallProlog (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_ClearExceptions (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_CloseAllOpenStreams (C-Interface function)` |  | 23.5 Controlling YAP Streams from `C`
| `YAP_CompileClause/1` |  | 24 Using YAP as a Library
| `YAP_ContinueGoal/0` |  | 24 Using YAP as a Library
| `YAP_CopyTerm/1` |  | 24 Using YAP as a Library
| `YAP_CurrentSlot (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_cutfail (C-Interface function)` |  | 23.10 Writing predicates in C
| `YAP_cutsucceed (C-Interface function)` |  | 23.10 Writing predicates in C
| `YAP_EndConsult/0` |  | 24 Using YAP as a Library
| `YAP_EnterGoal (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_Erase (C-Interface function)` |  | 23.6 Utility Functions in `C`
| `YAP_Error/1` |  | 24 Using YAP as a Library
| `YAP_ExactlyEqual (C-Interface function)` |  | 23.6 Utility Functions in `C`
| `YAP_Exit/1` |  | 24 Using YAP as a Library
| `YAP_FastInit/1` |  | 24 Using YAP as a Library
| `yap_flag/2` |  | 6.22 Miscellaneous
| `YAP_FloatOfTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_FlushAllStreams (C-Interface function)` |  | 23.5 Controlling YAP Streams from `C`
| `YAP_FreeSpaceFromYAP (C-Interface function)` |  | 23.4 Memory Allocation
| `YAP_FullLookupAtom (C-Interface function)` |  | 23.1 Terms
| `YAP_FunctorOfTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_FunctorToPred (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_GetValue/1` |  | 24 Using YAP as a Library
| `YAP_HaltRegisterHook (C-Interface function)` |  | 23.9 Miscellaneous C Functions
| `YAP_HeadOfTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_Init/1` |  | 24 Using YAP as a Library
| `YAP_InitConsult/2` |  | 24 Using YAP as a Library
| `YAP_InitSlot (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_IntOfTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_IsApplTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_IsAtomTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_IsBigNumTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_IsDBRefTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_IsFloatTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_IsIntTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_IsIsWideAtom (C-Interface function)` |  | 23.1 Terms
| `YAP_IsNonVarTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_IsPairTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_IsVarTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_IsWideAtom (C-Interface function)` |  | 23.1 Terms
| `YAP_LeaveGoal (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_LookupAtom (C-Interface function)` |  | 23.1 Terms
| `YAP_LookupWideAtom (C-Interface function)` |  | 23.1 Terms
| `YAP_MkApplTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_MkAtomTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_MkBigNumTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_MkFloatTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_MkFunctor (C-Interface function)` |  | 23.1 Terms
| `YAP_MkIntTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_MkNewApplTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_MkNewPairTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_MkPairTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_NameOfFunctor (C-Interface function)` |  | 23.1 Terms
| `YAP_NBufferToAtomList (C-Interface function)` |  | 23.3 Strings
| `YAP_NBufferToDiffList (C-Interface function)` |  | 23.3 Strings
| `YAP_NBufferToString (C-Interface function)` |  | 23.3 Strings
| `YAP_NewSlots (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_NWideBufferToAtomList (C-Interface function)` |  | 23.3 Strings
| `YAP_NWideBufferToDiffList (C-Interface function)` |  | 23.3 Strings
| `YAP_NWideBufferToString (C-Interface function)` |  | 23.3 Strings
| `YAP_OpenStream (C-Interface function)` |  | 23.5 Controlling YAP Streams from `C`
| `YAP_PRESERVED_DATA (C-Interface function)` |  | 23.10 Writing predicates in C
| `YAP_PRESERVED_DATA_CUT (C-Interface function)` |  | 23.10 Writing predicates in C
| `YAP_PRESERVE_DATA (C-Interface function)` |  | 23.10 Writing predicates in C
| `YAP_PutInSlot (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_PutValue/2` |  | 24 Using YAP as a Library
| `YAP_Read/1` |  | 24 Using YAP as a Library
| `YAP_ReadBuffer (C-Interface function)` |  | 23.3 Strings
| `YAP_Record (C-Interface function)` |  | 23.6 Utility Functions in `C`
| `YAP_Recorded (C-Interface function)` |  | 23.6 Utility Functions in `C`
| `YAP_RecoverSlots (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_Reset (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_RestartGoal (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_RestartGoal (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_RetryGoal (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_RunGoal (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_SetYAPFlag (C-Interface function)` |  | 23.9 Miscellaneous C Functions
| `YAP_ShutdownGoal (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_SlotsToArgs (C-Interface function)` |  | 23.7 From `C` back to Prolog
| `YAP_StreamToFileNo (C-Interface function)` |  | 23.5 Controlling YAP Streams from `C`
| `YAP_StringToBuffer (C-Interface function)` |  | 23.3 Strings
| `YAP_TailOfTerm (C-Interface function)` |  | 23.1 Terms
| `YAP_Throw (C-Interface function)` |  | 23.9 Miscellaneous C Functions
| `YAP_Unify (C-Interface function)` |  | 23.2 Unification
| `YAP_UserBackCPredicate (C-Interface function, deprecated)` |  | 23.10 Writing predicates in C
| `YAP_UserBackCutCPredicate (C-Interface function)` |  | 23.10 Writing predicates in C
| `YAP_UserCPredicate (C-Interface function)` |  | 23.10 Writing predicates in C
| `YAP_WideAtomName (C-Interface function)` |  | 23.1 Terms
| `YAP_WideBufferToAtomList (C-Interface function)` |  | 23.3 Strings
| `YAP_WideBufferToDiffList (C-Interface function)` |  | 23.3 Strings
| `YAP_WideBufferToString (C-Interface function)` |  | 23.3 Strings
| `YAP_Write/3` |  | 24 Using YAP as a Library
| `YAP_WriteBuffer/4` |  | 24 Using YAP as a Library

Jump to: | ! , - ; < = > @ [ \ A B C D E F G H I J K L M N O P Q R S T U V W Y

[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# Concept Index

Jump to: | A B C D E F G H I L M N O P Q R S T U V

| Index Entry |  | Section
A |  |
| aggregate |  | 7.1 Aggregate
| anonymous variable |  | 3.2.4 Variables
| apply |  | 7.2 Apply Macros
| association list |  | 7.3 Association Lists
| atom |  | 3.2.3 Atoms
| attribute declaration |  | 11.2.1 Attribute Declarations
| attributed variables |  | 11 Attributed Variables
| AVL trees |  | 7.4 AVL Trees
B |  |
| Block Diagram |  | 7.33 Block Diagram
| BOM |  | 3.3.2 BOM: Byte Order Mark
| booting |  | 2 Running YAP
| Byte Order Mark |  | 3.3.2 BOM: Byte Order Mark
C |  |
| cleanup |  | 7.25 Call Cleanup
| CLPQ |  | 12 Constraint Logic Programming over Reals
| CLPR |  | 12 Constraint Logic Programming over Reals
| comment |  | 3.2.6 Layout
| Counting Calls |  | 6.19 Counting Calls
D |  |
| declaration, attribute |  | 11.2.1 Attribute Declarations
E |  |
| Efficient Directed Graphs |  | 7.29 Directed Graphs
| encodings |  | 3.3 Wide Character Support
| end of term |  | 3.1 Syntax of Terms
| environment variables |  | 2.1 Running YAP Interactively
F |  |
| floating-point number |  | 3.2.1.2 Floating-point Numbers
G |  |
| global variables |  | 6.17 Global Variables
H |  |
| heap |  | 7.5 Heaps
I |  |
| installation |  | 1 Installing YAP
| integer |  | 3.2.1.1 Integers
| internationalization |  | 3.3 Wide Character Support
L |  |
| lam |  | 7.32 LAM
| Lambda Expressions |  | 7.31 Lambda Expressions
| Line Utilities Library |  | 7.7 Line Manipulation Utilities
| list manipulation |  | 7.6 List Manipulation
| Logtalk |  | 14 Logtalk
M |  |
| machine optimizations |  | 1.2 Tuning YAP for a Particular Machine and Compiler
| macros |  | 7.8 Maplist
| Matlab Interface |  | 7.10 MATLAB Package Interface
| Matrix Library |  | 7.9 Matrix Library
| mutable variables |  | 6.16 Term Modification
| MYDDAS |  | 15 MYDDAS
N |  |
| number |  | 3.2.1 Numbers
O |  |
| Operating System Utilities |  | 7.22 Calling The Operating System from YAP
| or-parallelism |  | 17 Parallelism
| ordered set |  | 7.12 Ordered Sets
P |  |
| parallelism |  | 17 Parallelism
| profiling |  | 6.18 Profiling Prolog Programs
| pseudo random |  | 7.13 Pseudo Random Number Integer Generator
| punctuation token |  | 3.2.5 Punctuation Tokens
Q |  |
| queue |  | 7.14 Queues
| queue |  | 7.15 Random Number Generator
R |  |
| Red-Black Trees |  | 7.17 Red-Black Trees
| regular expressions |  | 7.18 Regular Expressions
S |  |
| splay trees |  | 7.20 Splay Trees
| string |  | 3.2.2 Character Strings
| string I/O |  | 7.21 Reading From and Writing To Strings
| SWI-Compatible foreign file loading |  | 7.19 SWI-Prolog’s shlib library
| SWI-Prolog |  | 8 SWI-Prolog Emulation
| syntax |  | 1.1 Tuning the Functionality of YAP
| syntax |  | 3.1 Syntax of Terms
T |  |
| tabling |  | 18 Tabling
| timeout |  | 7.26 Calls With Timeout
| token |  | 3.2 Prolog Tokens
| tries |  | 7.24 Trie DataStructure
U |  |
| UCS |  | 3.3 Wide Character Support
| undirected graphs |  | 7.30 Undirected Graphs
| Unicode |  | 3.3 Wide Character Support
| unweighted graphs |  | 7.28 Unweighted Graphs
| updatable tree |  | 7.27 Updatable Binary Trees
| update semantics |  | 25.2.1 Major Differences between YAP and SICStus Prolog.
| updating terms |  | 6.16 Term Modification
| UTF-8 |  | 3.3 Wide Character Support
| utilities on terms |  | 7.23 Utilities On Terms
V |  |
| variable |  | 3.2.4 Variables

Jump to: | A B C D E F G H I L M N O P Q R S T U V

[Top] | [Contents] | [Index] | [ ? ]

# About This Document

This document was generated on August 13, 2013 using texi2html 5.0.

The buttons in the navigation panels have the following meaning:

Button | Name | Go to | From 1.2.3 go to
--- | --- | --- | ---
[ << ] | FastBack | Beginning of this chapter or previous chapter | 1
[ < ] | Back | Previous section in reading order | 1.2.2
[ Up ] | Up | Up section | 1.2
[ > ] | Forward | Next section in reading order | 1.2.4
[ >> ] | FastForward | Next chapter | 2
[Top] | Top | Cover (top) of document |
[Contents] | Contents | Table of contents |
[Index] | Index | Index |
[ ? ] | About | About (help) |

where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure:

- 1. Section One
  - 1.1 Subsection One-One
    - ...
  - 1.2 Subsection One-Two
    - 1.2.1 Subsubsection One-Two-One
    - 1.2.2 Subsubsection One-Two-Two
    - 1.2.3 Subsubsection One-Two-Three <== Current Position
    - 1.2.4 Subsubsection One-Two-Four
  - 1.3 Subsection One-Three
    - ...
  - 1.4 Subsection One-Four

This document was generated on August 13, 2013 using texi2html 5.0.