SWI-Prolog 7.3.18：综合编程语言手册

需积分: 9 140 浏览量更新于2024-07-20 收藏 2.14MB PDF 举报

"SWI-Prolog-7.3.18 手册，是VU University Amsterdam和University of Amsterdam发布的关于SWI-Prolog编程语言的参考手册，适用于版本7.3.18，更新于2016年3月。手册作者为Jan Wielemaker，提供了对SWI-Prolog的全面介绍和详细文档。" SWI-Prolog是一种广泛使用的、可移植的Prolog编程语言实现。其目标是构建一个强大且可扩展的系统，支持各种应用领域。SWI-Prolog的特点在于它包含了一系列接口库，可以与其他语言、数据库、图形和网络进行交互。特别值得一提的是，它为处理HTML/SGML/XML和RDF文档提供了丰富的支持，这使得该系统非常适合服务器应用程序，因为它具备稳定的多线程支持和HTTP服务器库。 SWI-Prolog遵循“爱丁堡传统”，即在ISO Prolog标准的基础上，与Quintus、SICStus和YAP Prolog保持高度兼容。为了确保兼容性，SWI-Prolog提供了一个框架，该框架是在与YAP合作开发的基础上，针对YAP、SICStus和IF/Prolog进行了实例化。 SWI-Prolog致力于提供良好的开发环境，包括调试工具、性能分析器、代码优化器和模块系统。它还支持现代编程实践，如动态加载、模块间导入和导出以及对异常处理的支持。此外，SWI-Prolog有强大的交互式shell，允许用户方便地测试和调试代码。手册中详细阐述了Prolog的基本语法和控制结构，如规则、查询、模式匹配、递归等。同时，它还介绍了SWI-Prolog特有的高级特性，如数据库事实、过程表、原子、列表、字符流、二进制数据、时间戳等。在系统调用部分，手册会涵盖如何使用内置的库函数来处理文件、目录、进程控制和系统资源。对于开发人员，手册提供了关于编译和链接Prolog程序的信息，以及如何使用SWI-Prolog的打包系统（Pack）来管理和分发软件包。此外，还涵盖了如何利用SWI-Prolog的多线程功能以及如何构建HTTP服务器应用。 "SWI-Prolog-7.3.18 手册"是一份详尽的参考资料，对于学习和使用SWI-Prolog进行软件开发的人员来说，是不可或缺的工具，可以帮助他们充分利用这个强大的逻辑编程系统来解决实际问题。

14 CHAPTER 1. INTRODUCTION

1.5 Implementation history

SWI-Prolog started back in 1986 with the requirement for a Prolog that could handle recursive inter-

action with the C-language: Prolog calling C and C calling Prolog recursively. In those days Prolog

systems were not very aware of their environment and we needed such a system to support interactive

applications. Since then, SWI-Prolog’s development has been guided by requests from the user com-

munity, especially focussing on (in arbitrary order) interaction with the environment, scalability, (I/O)

performance, standard compliance, teaching and the program development environment.

SWI-Prolog is based on a simple Prolog virtual machine called ZIP [Bowen et al., 1983,

Neumerkel, 1993] which deﬁnes only 7 instructions. Prolog can easily be compiled into this lan-

guage, and the abstract machine code is easily decompiled back into Prolog. As it is also possible

to wire a standard 4-port debugger in the virtual machine, there is no need for a distinction between

compiled and interpreted code. Besides simplifying the design of the Prolog system itself, this ap-

proach has advantages for program development: the compiler is simple and fast, the user does not

have to decide in advance whether debugging is required, and the system only runs slightly slower in

debug mode compared to normal execution. The price we have to pay is some performance degra-

dation (taking out the debugger from the VM interpreter improves performance by about 20%) and

somewhat additional memory usage to help the decompiler and debugger.

SWI-Prolog extends the minimal set of instructions described in [Bowen et al., 1983] to improve

performance. While extending this set, care has been taken to maintain the advantages of decompi-

lation and tracing of compiled code. The extensions include specialised instructions for uniﬁcation,

predicate invocation, some frequently used built-in predicates, arithmetic, and control (;/2, |/2),

if-then (->/2) and negation-by-failure (\+/1).

1.6 Acknowledgements

Some small parts of the Prolog code of SWI-Prolog are modiﬁed versions of the corresponding Edin-

burgh C-Prolog code: grammar rule compilation and writef/2. Also some of the C-code originates

from C-Prolog: ﬁnding the path of the currently running executable and some of the code underlying

absolute

file name/2. Ideas on programming style and techniques originate from C-Prolog

and Richard O’Keefe’s thief editor. An important source of inspiration are the programming tech-

niques introduced by Anjo Anjewierden in PCE version 1 and 2.

Our special thanks go to those who had the fate of using the early versions of this system, sug-

gested extensions or reported bugs. Among them are Anjo Anjewierden, Huub Knops, Bob Wielinga,

Wouter Jansweijer, Luc Peerdeman, Eric Nombden, Frank van Harmelen, Bert Rengel.

Martin Jansche (jansche@novell1.gs.uni-heidelberg.de) has been so kind to reor-

ganise the sources for version 2.1.3 of this manual. Horst von Brand has been so kind to ﬁx many

typos in the 2.7.14 manual. Thanks! Randy Sharp ﬁxed many issues in the 6.0.x version of the manual.

Bart Demoen and Tom Schrijvers have helped me adding coroutining, constraints, global variables

and support for cyclic terms to the kernel. Tom Schrijvers has provided a ﬁrst clp(fd) constraint solver,

the CHR compiler and some of the coroutining predicates. Markus Triska contributed the current

clp(fd) implementation.

Paul Singleton has integrated Fred Dushin’s Java-calls-Prolog side with his Prolog-calls-Java side

into the current bidirectional JPL interface package.

Richard O’Keefe is gratefully acknowledged for his efforts to educate beginners as well as valu-

able comments on proposed new developments.

SWI-Prolog 7.3 Reference Manual

2.2. THE USER’S INITIALISATION FILE 17

• The ﬁle extension .pl is associated with the program swipl-win.exe. Opening a .pl

ﬁle will cause swipl-win.exe to start, change directory to the directory in which the ﬁle to

open resides, and load this ﬁle.

The normal way to start the likes.pl ﬁle mentioned in section 2.1.1 is by simply double-

clicking this ﬁle in the Windows explorer.

2.1.2 Executing a query

After loading a program, one can ask Prolog queries about the program. The query below asks Prolog

what food ‘sam’ likes. The system responds with X = hvaluei if it can prove the goal for a certain

X. The user can type the semi-colon (;) or spacebar

if (s)he wants another solution. Use the RETURN

key if you do not want to see the more answers. Prolog completes the output with a full stop (.) if

the user uses the RETURN key or Prolog knows there are no more answers. If Prolog cannot ﬁnd

(more) answers, it writes false. Finally, Prolog answers using an error message to indicate the query

or program contains an error.

?- likes(sam, X).

X = dahl ;

X = tandoori ;

...

X = chips.

Note that the answer written by Prolog is a valid Prolog program that, when executed, produces the

same set of answers as the original program.

2.2 The user’s initialisation ﬁle

After the system initialisation, the system consults (see consult/1) the user’s startup ﬁle. The base-

name of this ﬁle follows conventions of the operating system. On MS-Windows, it is the ﬁle swipl.

ini and on Unix systems .swiplrc. The ﬁle is searched using the file search path/2

clauses for user profile.

The table below shows the default value for this search path. The

phrase happdatai refers to the Windows CSIDL name for the folder. The actual name depends on the

Windows language. English versions typically use ApplicationData. See also win folder/2

Unix Windows

home ˜ happdatai/SWI-Prolog

After the ﬁrst startup ﬁle is found it is loaded and Prolog stops looking for further startup ﬁles. The

name of the startup ﬁle can be changed with the ‘-f file’ option. If File denotes an absolute path,

On most installations, single-character commands are executed without waiting for the RETURN key.

The SWI-Prolog top level differs in several ways from traditional Prolog top level. The current top level was designed

in cooperation with Ulrich Neumerkel.

Older versions ﬁrst searched in the current working directory. This feature has been removed for security reasons.

Users can implement loading a setup ﬁle from the working directory in their global preference ﬁle.

SWI-Prolog 7.3 Reference Manual

18 CHAPTER 2. OVERVIEW

this ﬁle is loaded, otherwise the ﬁle is searched for using the same conventions as for the default

startup ﬁle. Finally, if ﬁle is none, no ﬁle is loaded.

The installation provides a ﬁle customize/dotswiplrc with (commented) commands that

are often used to customize the behaviour of Prolog, such as interfacing to the editor, color selection

or history parameters. Many of the development tools provide menu entries for editing the startup ﬁle

and starting a fresh startup ﬁle from the system skeleton.

See also the -s (script) and -F (system-wide initialisation) in section 2.4 and section 2.3.

2.3 Initialisation ﬁles and goals

Using command line arguments (see section 2.4), SWI-Prolog can be forced to load ﬁles and execute

queries for initialisation purposes or non-interactive operation. The most commonly used options are

-f file or -s file to make Prolog load a ﬁle, -g goal to deﬁne an initialisation goal and

-t goal to deﬁne the top-level goal. The following is a typical example for starting an application

directly from the command line.

machine% swipl -s load.pl -g go -t halt

It tells SWI-Prolog to load load.pl, start the application using the entry point go/0 and —instead

of entering the interactive top level— exit after completing go/0. The -q may be used to suppress

all informational messages.

In MS-Windows, the same can be achieved using a short-cut with appropriately deﬁned command

line arguments. A typically seen alternative is to write a ﬁle run.pl with content as illustrated below.

Double-clicking run.pl will start the application.

:- [load]. % load program

:- go. % run it

:- halt. % and exit

Section 2.10.2 discusses further scripting options, and chapter 11 discusses the generation of runtime

executables. Runtime executables are a means to deliver executables that do not require the Prolog

system.

2.4 Command line options

SWI-Prolog can be executed in one of the following modes:

swipl --help

swipl --version

swipl --arch

swipl --dump-runtime-variables

These options must appear as only option. They cause Prolog to print an informational message

and exit. See section 2.4.1.

SWI-Prolog 7.3 Reference Manual

剩余546页未读，继续阅读

bluesss

粉丝: 0
资源: 2

SWI-Prolog 7.3.18：综合编程语言手册

Yap Prolog的LAMMPI库在SWI-Prolog中的移植

SWI-Prolog 6.3.7官方手册：全面编程语言与应用支持

SWI-Prolog 6.4.1官方手册：进阶编程指南

SWI-Prolog-9.3.10-1.x64.exe.cab

setup-swi-prolog:设置 SWI-Prolog 操作

swi-prolog-wasm:SWI-Prolog移植到WebAssembly

swi-prolog-on-dotcloud:dotCloud 上的 SWI-Prolog 作为自定义服务

SWI-Prolog7.7.23手册

swi-web-prolog:Web Prolog 的概念验证 SWI-Prolog 实现

SWI-Prolog 手册 6.4.1版

最新资源