XSB Prolog 3.5开发者手册：SLG-WAM核心引擎与逻辑模拟指南

需积分: 9 132 浏览量更新于2024-07-22 收藏 2.49MB PDF 举报

XSB Prolog用户手册是针对TheXSBSystem的详细文档，版本为3.5.x，专注于程序开发人员。XSB是一个基于Prolog的实现，它扩展了WAM（ Warren Abstract Machine）架构，旨在让程序员在解决问题时更加专注于逻辑模拟，而非底层细节。该系统由一群核心开发者共同构建和维护，其中主要包括Terrance Swift、David S. Warren、Konstantinos Sagonas、Prasad Rao、Juliana Freire、Ernie Johnson等人。 David Warren和Terrance Swift负责日常的维护工作，包括修复bug、移植到不同的平台以及配置管理，他们的贡献对于系统的稳定性和性能至关重要。在3.5版本中，SLG-WAM的核心引擎开发工作占据了主导地位，Terrance Swift主要负责编写最初的表格化引擎、SLG-WAM以及内置功能，并引领当前表格子系统的发展。Prasad Rao则实现了引擎的表格子系统，利用尝试机制支持基于变种的表格访问，这一改进使得系统在处理复杂逻辑时更为高效。 Ernie Johnson在此基础上对这些模块进行了扩展和重构，优化了代码结构和性能。其他开发者如Kostis Sagonas、Juliana Freire、Luis de Castro、Rui F. Marques、Baoqiu Cui、Steve Dawson、Michael Kifer也分别在各自领域做出了重要贡献。整个团队的合作使得XSB Prolog成为一个强大且灵活的工具，不仅适合逻辑编程，而且具有高效的执行性能，适用于各种复杂的推理任务。通过阅读这份手册，开发者可以了解到XSB Prolog的内部工作机制、API使用方法、高级特性以及如何充分利用其进行逻辑建模和问题求解。同时，它还提供了丰富的教程和示例，有助于新用户快速上手并深入学习。这是一本深入了解和掌握XSB Prolog的强大指南，对于从事人工智能、逻辑编程或相关领域的专业人士来说，是不可或缺的参考资料。

CHAPTER 1. INTRODUCTION 6

XSB Packages Based on these features, a number of sophisticated packages have been

implemented using XSB. For instance, XSB supports a sophisticated object-oriented inter-

face called Flora. Flora (http://flora.sourceforge.net) is available as an XSB package

and is described in its own manual, available from the same site from which XS B was down-

loaded. Another package, XMC http://www.cs.sun nysb.edu/~lmc depends on XSB to

perform sophisticated mo del-checking of concurrent systems. Within the XSB project, the

Cold Dead Fish package supports maintenance of, and reasoning over ontologies; xsbdoc

supports literate programming in XSB, and XASP provides an interface to Smodels to sup-

port Answer Set programming. XSB packages also support Perl-style pattern matching and

POSIX-style pattern matching. In addition, experimental preprocessing libraries currently

supported are Extended logic programs (under the well-founded semantics), and Annotated

Logic Programs. These latter libraries are described in Volume 2 of this manual.

1.1 Using This Manual

We adopt some standard notational conventions , such as the name/arity convention for

describing predicates and functors, + to denote input arguments, - to denote output ar-

guments, ? for arguments that may be either input or output and # for arguments that

are both input and output (can be changed by the procedure). See Section

3.10.5 for more

details. . Also, the manual uses UNIX syntax for ﬁles and directories except when it

speciﬁcally addresses other operating systems such as Windows.

Finally, we note that XSB is under continuous development, and this document —

intended to be the user manual— reﬂects the current status (Version 3.5) of our system.

While we have taken great eﬀort to create a r obust and eﬃcient system, we would like to

emphasize that XSB is also a r esearch system and is to some degree experimental. When

the research features of XSB — tabling, HiLog, and Indexing Techniques — are discussed in

this manual, we also cite documents where they are fully explained. All of these docum ents

can be found without diﬃculty on the web.

While some of Version 3.5 is subject to change in future releases, we will try to be as

upward-compatible as possible. We would also like to hear from experienced users of our

system about features they would like us to include. We do try to accommodate serious

users of XSB whenever we can. Finally, we must mention that the use of undocumented

features is not supported, and at the user’s own risk.

CHAPTER 2. GETTING STARTED WITH XSB 9

Type of Machine. Th e conﬁguration script automatically detects your machine and OS

type, and b uilds XSB accordingly. On 64-bit platforms, the default compilation of

XSB will reﬂect the default for the C compiler (e.g. gcc) on that platform. More-

over, you can b uild XSB for diﬀerent architectures while using the same tree and the

same installation directory provided, of course, that these machines are sharing th is

directory, say using NFS or Samba. All you will have to d o is to login to a diﬀerent

machine with a diﬀerent architecture or OS type, and repeat the above sequence of

commands – or conﬁgure with diﬀerent parameters.

The conﬁguration ﬁles for diﬀerent architectures reside in diﬀerent directories, and

there is no danger of an architecture conﬂict. In fact, you can keep using the same

./bin/xsb script regardless of the architecture. It will detect your conﬁguration and

will use the right ﬁles for the right architecture!

If XSB is being built on a machine running Windows in which Cygwin is installed,

Cygwin and Windows are treated as separate operating systems, as their APIs are

completely diﬀerent. If no previous conﬁguration has been made, the conﬁgure script

will attempt to use gcc and other Unix facilities, and therefore will compile the system

under Cygwin. If this behavior is not d esired, the option –with -wind (equivalently,

–with-os=wind) us es a Window compiler and API. If a user wants to en s ure the

Cygwin compiler is used (say after a previous conﬁguration for Windows), the option

-without-wind can be used. S ee Section

2.2.2 for more details.

Choice of the C Compiler and compiler-related options On Unix s y s tems, XSB is

developed and tested mainly using gcc. Accordingly, the configure script will at-

tempt to us e gcc, if it is available. Otherwise, it will revert to cc or acc. Some ver-

sions of gcc are broken for particular platforms or gcc may not have been installed;

in which case you would have to give config ure an add itional directive –with -cc (or

–with-acc). If you must use some special compiler, use –with-cc=your-own-com piler.

You can also us e the –with-optimization option to change the default C compiler op-

timization level. (or –disable-optimization to disable all compiler optimizations).

–enable-debug is mainly a devlopment option that allows XSB to be debugged using

gdb – there are m any other compiler-based options options. Type configure –help

to see them all. Also see the ﬁle $XSB_DIR /INSTALL for more details.

Word Size XSB’s conﬁguration script checks whether the d efault compilation mode of a

platform is 32- or 64-bits, and will build a version of XSB accoringly. Some platforms,

however, support both 32-bit and 64-bit compilation. On such a platform, a user

can explicitly s pecify the type of compilation using the options wit h-bits32 and

with-bits64.

XSB and Site-speciﬁc Information Using the option –prefix=PREFIX installs architecture-

independent ﬁles in the directory PREFIX, e.g. /usr/local, which can be useful if

XSB is to be shared at a site. Using th e option –site-prefix=DIR installs site-

speciﬁc libraries in DIR/ site. Other options indicate directories in which to search

CHAPTER 2. GETTING STARTED WITH XSB 10

for site-speciﬁc static and dynamic libraries, and for include ﬁles.

Multi-threading Version 3.0 of XSB was the ﬁrst version that sup ports multi-threading.

On some platforms, the multi-threaded engine is slightly s lower than the single-

threaded engine, mostly due to its need for concurrency control. To obtain the beneﬁts

of multiple threads on a platform that supports either POSIX or Windows threads (i.e.

nearly all platforms) users must conﬁgure XSB with the directive enable-mt (see Sec-

tion 7.8 for instructions speciﬁc to Windows. The multi-threaded engine works with

other conﬁgur ation options, multi-threading can be compiled with batched or local

scheduling, with the ODBC or Interprolog interfaces, and so on.

Interfaces Certain interfaces must be designated at conﬁguration time, including those to

Oracle, ODBC, Smodels, Tck/Tk, and Libww w. However, the XSB-calling-C interface

interface does not need to be speciﬁed at conﬁguration time. If you wish to use the

InterProlog Java interface that is based on JNI, you must specify this at conﬁguration

time; otherwise if you wish to use the sockets-based I nterprolog interface, it does not

need to be speciﬁed at conﬁguration time. See Volume 2 an d the InterProlog site

www.declarativa.com for details of speciﬁc interfaces

While th e XSB conﬁguration mechanism can detect most include and library paths,

use of certain interfaces may require information about particular directories. In

particular the –with-st atic-lib raries option might be needed if compiling with

support for statically linked packages (such as Oracle) or if your standard C libraries

are in odd places. Alternately, dynamic libraries on odd places may need to be

speciﬁed at conﬁguration time using the –w ith-dyna mic-libr aries option. and

ﬁnally, the –with-in cludes option might be needed if your standard header ﬁles (or

your j ni.h ﬁle) are in odd places, or if XSB is compiled with ODBC support. Typ e

configure –help for more details.

Type of Scheduling Strategy. The ordering of operations within a tabled evaluation can

drastically aﬀect its performance. XSB provides two scheduling s trategies: Batched

Evaluation and Local Evaluation. Local Evaluation ensures that, whenever possib le,

subgoals are fully evaluated before there answers are returned , and provides s upe-

rior behavior for programs in which tabled negation is used. Batched Evaluation

evaluates queries to reduce the time to the ﬁrs t answer of a query. Both evaluation

methods can be usefu l for diﬀerent p rograms. Sin ce Version 2.4, Local Evaluation

has been the default evaluation method for XSB. Batched Evaluation can be chosen

via the – enable-b atched-s cheduling conﬁgure option. Detailed explanations of the

scheduling strategies can be found in [

28], and further experimentation in [11].

Other options are of interest to advanced users who wish to experiment with XSB, or

to use XSB for large-scale projects. In general, however users need not concern themselves

with these options.

剩余470页未读，继续阅读

fodeluo

粉丝: 0
资源: 1

XSB Prolog 3.5开发者手册：SLG-WAM核心引擎与逻辑模拟指南

turbo prolog 使用手册

SWI-Prolog 手册 6.4.1版

turbo prolog使用手册

SWI-Prolog用户手册

prolog2.0手册

SWI-Prolog 用户手册 8.0.3版本 英文(pdf)

Visual Prolog语言手册

swi-prolog参考手册

swi prolog 中文手册

Turbo Prolog2.0用户手册

最新资源

SWI-Prolog 用户手册 8.0.3版本英文(pdf)