DOCSLIB.ORG

Local Copy of the SWI Prolog Manual, Version 7.2.3 (August 2015)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Local Copy of the SWI Prolog Manual, Version 7.2.3 (August 2015) VU University Amsterdam University of Amsterdam De Boelelaan 1081a, 1081 HV Amsterdam Kruislaan 419, 1098 VA Amsterdam The Netherlands The Netherlands ˜ Reference Manual Updated for version 7.2.3, August 2015 Jan Wielemaker [email protected] http://www.swi-prolog.org SWI-Prolog is a comprehensive and portable implementation of the Prolog programming language. SWI-Prolog aims to be a robust and scalable implementation supporting a wide range of applications. In particular, it ships with a wide range of interface libraries, providing interfaces to other languages, databases, graphics and networking. It provides extensive support for managing HTML/SGML/XML and RDF documents. The system is particularly suited for server applications due to robust support for multithreading and HTTP server libraries. SWI-Prolog is designed in the ‘Edinburgh tradition’. In addition to the ISO Prolog stan- dard it is largely compatible to Quintus, SICStus and YAP Prolog. SWI-Prolog provides a compatibility framework developed in cooperation with YAP and instantiated for YAP, SICStus and IF/Prolog. SWI-Prolog aims at providing a good development environment, including extensive ed- itor support, graphical source-level debugger, autoloading and ‘make’ facility and much more. SWI-Prolog editor and the PDT plugin for Eclipse provide alternative environ- ments. This document gives an overview of the features, system limits and built-in predicates. ˜ This work is licensed under the Creative Commons Attribution- ShareAlike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/ or send a let- ter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. Contents 1 Introduction 10 1.1 Positioning SWI-Prolog................................. 10 1.2 Status and releases................................... 11 1.3 Should I be using SWI-Prolog?............................. 11 1.4 Support the SWI-Prolog project............................ 12 1.5 Implementation history................................. 13 1.6 Acknowledgements................................... 13 2 Overview 15 2.1 Getting started quickly................................. 15 2.1.1 Starting SWI-Prolog.............................. 15 2.1.2 Executing a query............................... 16 2.2 The user’s initialisation file............................... 16 2.3 Initialisation files and goals............................... 17 2.4 Command line options................................. 17 2.4.1 Informational command line options...................... 18 2.4.2 Command line options for running Prolog................... 18 2.4.3 Controlling the stack sizes........................... 20 2.4.4 Running goals from the command line..................... 21 2.4.5 Compilation options.............................. 21 2.4.6 Maintenance options.............................. 21 2.5 GNU Emacs Interface.................................. 21 2.6 Online Help....................................... 22 2.7 Command line history.................................. 23 2.8 Reuse of top-level bindings............................... 23 2.9 Overview of the Debugger............................... 24 2.10 Compilation....................................... 27 2.10.1 During program development......................... 27 2.10.2 For running the result.............................. 28 2.11 Environment Control (Prolog flags).......................... 30 2.12 An overview of hook predicates............................ 42 2.13 Automatic loading of libraries............................. 44 2.14 Garbage Collection................................... 45 2.15 The SWI-Prolog syntax................................. 45 2.15.1 ISO Syntax Support.............................. 46 2.15.2 Nested comments................................ 46 2.16 Rational trees (cyclic terms).............................. 51 2.17 Just-in-time clause indexing.............................. 51 2.17.1 Future directions................................ 52 2.17.2 Indexing and portability............................ 52 SWI-Prolog 7.2 Reference Manual 2 2.18 Wide character support................................. 53 2.18.1 Wide character encodings on streams..................... 53 2.19 System limits...................................... 54 2.19.1 Limits on memory areas............................ 54 2.19.2 Other Limits.................................. 55 2.19.3 Reserved Names................................ 57 2.20 SWI-Prolog and 64-bit machines............................ 57 2.20.1 Supported platforms.............................. 57 2.20.2 Comparing 32- and 64-bits Prolog....................... 57 2.20.3 Choosing between 32- and 64-bit Prolog.................... 58 3 Initialising and Managing a Prolog Project 59 3.1 The project source files................................. 59 3.1.1 File Names and Locations........................... 59 3.1.2 Project Special Files.............................. 60 3.1.3 International source files............................ 61 3.2 Using modules..................................... 61 3.3 The test-edit-reload cycle................................ 62 3.3.1 Locating things to edit............................. 62 3.3.2 Editing and incremental compilation...................... 63 3.4 Using the PceEmacs built-in editor........................... 63 3.4.1 Activating PceEmacs.............................. 63 3.4.2 Bluffing through PceEmacs.......................... 64 3.4.3 Prolog Mode.................................. 66 3.5 The Graphical Debugger................................ 68 3.5.1 Invoking the window-based debugger..................... 68 3.6 The Prolog Navigator.................................. 69 3.7 Cross-referencer..................................... 69 3.8 Accessing the IDE from your program......................... 71 3.9 Summary of the IDE.................................. 72 4 Built-in Predicates 73 4.1 Notation of Predicate Descriptions........................... 73 4.2 Character representation................................ 74 4.3 Loading Prolog source files............................... 75 4.3.1 Conditional compilation and program transformation............. 85 4.3.2 Loading files, active code and threads..................... 88 4.3.3 Quick load files................................. 90 4.4 Editor Interface..................................... 91 4.4.1 Customizing the editor interface........................ 91 4.5 List the program, predicates or clauses......................... 92 4.6 Verify Type of a Term.................................. 93 4.7 Comparison and Unification of Terms......................... 95 4.7.1 Standard Order of Terms............................ 95 4.7.2 Special unification and comparison predicates................. 96 4.8 Control Predicates.................................... 98 4.9 Meta-Call Predicates.................................. 100 SWI-Prolog 7.2 Reference Manual Contents 3 4.10 ISO compliant Exception handling........................... 104 4.10.1 Debugging and exceptions........................... 105 4.10.2 The exception term............................... 105 4.10.3 Printing messages............................... 105 4.11 Handling signals.................................... 110 4.11.1 Notes on signal handling............................ 111 4.12 DCG Grammar rules.................................. 111 4.13 Database......................................... 114 4.13.1 Update view.................................. 117 4.13.2 Indexing databases............................... 117 4.14 Declaring predicate properties............................. 118 4.15 Examining the program................................. 119 4.16 Input and output..................................... 124 4.16.1 Predefined stream aliases............................ 124 4.16.2 ISO Input and Output Streams......................... 125 4.16.3 Edinburgh-style I/O............................... 133 4.16.4 Switching between Edinburgh and ISO I/O.................. 135 4.16.5 Write onto atoms, code-lists, etc......................... 135 4.17 Status of streams.................................... 136 4.18 Primitive character I/O................................. 137 4.19 Term reading and writing................................ 140 4.20 Analysing and Constructing Terms........................... 148 4.20.1 Non-logical operations on terms........................ 151 4.21 Analysing and Constructing Atoms........................... 152 4.22 Localization (locale) support.............................. 155 4.23 Character properties................................... 157 4.23.1 Case conversion................................ 159 4.23.2 White space normalization........................... 159 4.23.3 Language-specific comparison......................... 159 4.24 Operators........................................ 160 4.25 Character Conversion.................................. 161 4.26 Arithmetic........................................ 162 4.26.1 Special purpose integer arithmetic....................... 162 4.26.2 General purpose arithmetic........................... 163 4.27 Misc arithmetic support predicates........................... 172 4.28 Built-in list operations................................. 173 4.29 Finding all Solutions to a Goal............................. 176 4.30 Forall.......................................... 177 4.31 Formatted Write..................................... 178 4.31.1 Writef...................................... 178 4.31.2 Format....................................
Load more

Recommended publications
  • From Plain Prolog to Logtalk Objects: Effective Code Encapsulation and Reuse
    From Plain Prolog to Logtalk Objects: Effective Code Encapsulation and Reuse Paulo Moura Dep. of Computer Science, Univ. of Beira Interior, Portugal Center for Research in Advanced Computing Systems INESC Porto, Portugal http://logtalk.org/ [email protected] ICLP 2009 Inivited Talk Someone said I need one... 2 Spoilers • Objects in a Prolog world • Logtalk design goals • Logtalk architecture • Logtalk versus Prolog and Prolog modules • Logtalk overview and quick tour • Some demos (if time allows) • Logtalk as a portable Prolog application • Logtalk programming support 3 A warning... • I have a laser and I’m not afraid to use it ... Beware of asking embarrassing questions! • But please feel free to interrupt and ask nice ones that make the speaker shine! 4 A bit of history... • Project started in January 1998 • First version for registered users in July 1998 • First public beta in October 1998 • First stable version in February 1999 5 Logtalk in numbers • Compiler + runtime: ~11000 lines of Prolog code • 37 major releases, 122 including minor ones • Current version: Logtalk 2.37.2 minor release number major release number second generation of Logtalk • ~1500 downloads/month (so many earthlings, so little time) 6 Logtalk distribution • Full sources (compiler/runtime, Prolog config files, libraries) • MacOS X (pkg), Linux (rpm), Debian (deb), and Windows (exe) installers XHTML and PDF User and Reference Manuals • (121 + 144 pages) • +90 programming examples • Support for several text editors and syntax highlighters (text services and code publishing) 7 Objects in Prolog?!? We’re being invaded! 8 Objects have identifiers and dynamic state! • It seems Prolog modules are there first: Identifier! :- module(broadcast, [...]).
    [Show full text]
  • Utgåvenoteringar För Fedora 11
    Fedora 11 Utgåvenoteringar Utgåvenoteringar för Fedora 11 Dale Bewley Paul Frields Chitlesh Goorah Kevin Kofler Rüdiger Landmann Ryan Lerch John McDonough Dominik Mierzejewski David Nalley Zachary Oglesby Jens Petersen Rahul Sundaram Miloslav Trmac Karsten Wade Copyright © 2009 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. 1 Utgåvenoteringar For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
    [Show full text]
  • Translingual Obfuscation
    Translingual Obfuscation Pei Wang, Shuai Wang, Jiang Ming, Yufei Jiang, and Dinghao Wu College of Information Sciences and Technology The Pennsylvania State University fpxw172, szw175, jum310, yzj107, [email protected] Abstract—Program obfuscation is an important software pro- Currently the state-of-the-art obfuscation technique is to tection technique that prevents attackers from revealing the incorporate with process-level virtualization. For example, programming logic and design of the software. We introduce obfuscators such as VMProtect [10] and Code Virtualizer [4] translingual obfuscation, a new software obfuscation scheme replace the original binary code with new bytecode, and a which makes programs obscure by “misusing” the unique custom interpreter is attached to interpret and execute the features of certain programming languages. Translingual ob- bytecode. The result is that the original binary code does fuscation translates part of a program from its original lan- not exist anymore, leaving only the bytecode and interpreter, guage to another language which has a different program- making it difficult to directly reverse engineer [39]. How- ming paradigm and execution model, thus increasing program ever, recent work has shown that the decode-and-dispatch complexity and impeding reverse engineering. In this paper, execution pattern of virtualization-based obfuscation can we investigate the feasibility and effectiveness of translingual be a severe vulnerability leading to effective deobfusca- obfuscation with Prolog, a logic programming language. We tion [24], [66], implying that we are in need of obfuscation implement translingual obfuscation in a tool called BABEL, techniques based on new schemes. which can selectively translate C functions into Prolog pred- We propose a novel and practical obfuscation method icates.
    [Show full text]
  • On the Implementation of a Cloud-Based Computing Test Bench Environment for Prolog Systems †
    information Article On the Implementation of a Cloud-Based Computing Test Bench Environment for Prolog Systems † Ricardo Gonçalves, Miguel Areias * ID and Ricardo Rocha ID CRACS & INESC TEC and Faculty of Sciences, University of Porto, Rua do Campo Alegre, 1021/1055, 4169-007 Porto, Portugal; [email protected] (R.G.); [email protected] (R.R.) * Correspondence: [email protected] † This paper is an extended version of our paper published in the Symposium on Languages, Applications and Technologies 2017. Received: 13 September 2017; Accepted: 13 October 2017; Published: 19 October 2017 Abstract: Software testing and benchmarking are key components of the software development process. Nowadays, a good practice in large software projects is the continuous integration (CI) software development technique. The key idea of CI is to let developers integrate their work as they produce it, instead of performing the integration at the end of each software module. In this paper, we extend a previous work on a benchmark suite for the YAP Prolog system, and we propose a fully automated test bench environment for Prolog systems, named Yet Another Prolog Test Bench Environment (YAPTBE), aimed to assist developers in the development and CI of Prolog systems. YAPTBE is based on a cloud computing architecture and relies on the Jenkins framework as well as a new Jenkins plugin to manage the underlying infrastructure. We present the key design and implementation aspects of YAPTBE and show its most important features, such as its graphical user interface (GUI) and the automated process that builds and runs Prolog systems and benchmarks.
    [Show full text]
  • Distributed Multi-Threading in GNU Prolog Nuno Eduardo Quaresma Morgadinho
    §' Departamento de hrformática Distributed Multi-Threading in GNU Prolog Nuno Eduardo Quaresma Morgadinho <[email protected]> Supervisor: Salvador Abreu (Ur,iversidade de Évora DI) This thesis does not include aVpreciation nor suggestions madeby the iury. Esta dissertaçã.o não inclui as críticas e sugestões feitas pelo iúri, Évora 2007 § Departamento de Lrformática Distributed Multi-Threading in GNU Prolog Nuno Eduardo Quaresma Morgadinho <[email protected]> ..--# Jü3 3?Y Supervisor: Salvador Abreu (Universidade de Évora, DI) This thesis does not include appreciation nor suggestions madeby tlrc jury. Esta dissertação não inclui as críticas e sugestões feitas pelo júri. Évora 2007 Abstract Although parallel computing has been widely researdred, the process of bringrng concurrency and parallel programming to the mainstream has just be- gun. Combining a distributed multi-threading environment like PM2 with Pro- log, opens the way to exploit concurrency and parallel computing using logic programming. Tlo achieve suú a pu{pose, we developed PM2-Prolog, a Prolog interface to the PM2 system. It allows multithreaded Prolog applications to run in multiple GNU Prolog engines in a distributed environment, thus taking advan- tage of the resources available on a computer network. This is especially useful for computationally intensive problems, where performance is an important fac- tor. The system API offers thread management primitives, as well as explicit communication between threads. Preliminary test results show an almost linear speedup, when compared to a sequential version. Keywords: Distributed, Multi-Threading, Prolog, Logic Programming, Concurrency, Parallel, High-PerformÉulce Computing 1 Resumo Multi-Threading Distribuído no GNU Prolog Embora a computação paralela já tenha sido alvo de inúmeros estudos, o processo de a tomar acessível às massas ainda mal começou.
    [Show full text]
  • Improving the Compilation of Prolog to C Using Type and Determinism Information: Preliminary Results*
    Improving the Compilation of Prolog to C Using Type and Determinism Information: Preliminary Results* J. Morales1, M. Carro1' M. Hermenegildo* * [email protected] [email protected] [email protected] Abstract We describe the current status of and provide preliminary performance results for a compiler of Prolog to C. The compiler is novel in that it is designed to accept different kinds of high-level information (typically ob- tained via an analysis of the initial Prolog program and expressed in a standardized language of assertions) and use this information to optimize the resulting C code, which is then further processed by an off-the-shelf C compiler. The basic translation process used essentially mimics an unfolding of a C-coded bytecode emú- lator with respect to the particular bytecode corresponding to the Prolog program. Optimizations are then applied to this unfolded program. This is facilitated by a more flexible design of the bytecode instructions and their lower-level components. This approach allows reusing a sizable amount of the machinery of the bytecode emulator: ancillary pieces of C code, data definitions, memory management routines and áreas, etc., as well as mixing bytecode emulated code with natively compiled code in a relatively straightforward way We report on the performance of programs compiled by the current versión of the system, both with and without analysis information. 1 Introduction Several techniques for implementing Prolog have been devised since the original interpreter developed by Colmerauer and Roussel [5], many of them aimed at achieving more speed. An excellent survey of a sig- nifícant part of this work can be found in [26].
    [Show full text]
  • Bousi-Prolog Ver
    UNIVERSIDAD DE CASTILLA-LA MANCHA ESCUELA SUPERIOR DE INFORMÁTICA Dpto. de Tecnologías y Sistemas de Información Bousi∼Prolog ver. 2.0: Implementation, User Manual and Applications Autors: Pascual Julián-Iranzo and Juan Gallardo-Casero Other contributors: Fernando Sáenz-Pérez (U. Complutense de Madrid) Bousi∼Prolog ver. 2.0: Implementation, User Manual and Applications © Pascual Julián-Iranzo & Juan Gallardo-Casero, 2008-2017. Pascual Julián-Iranzo, Juan Gallardo- Casero & Fernando Sáenz-Pérez, 2017-2019. Bousi∼Prolog is licensed for research and educational purposes only and it’s distributed with NO WARRANTY OF ANY KIND. You are freely allowed to use, copy and distribute Bousi Prolog provided that you make no modifications to any of its files and give credit to its original authors. This documentation was written and formatted with LATEX. All the figures and diagrams that appear in it were designed with Gimp, Inkscape or ArgoUML. The shield of the cover is work of D. Villa, I. Díez, F. Moya, Xavigivax and G. Paula and is distributed under the Creative Commons Attribution 3.0 license. ii ABSTRACT Logic Programming is a programming paradigm based on first order logic that, in recent decades, has been used in fields such as knowledge representation, artificial intelligence or deductive databases. However, Logic Programming presents an important limitation when dealing with real-world problems where precise information is not available, since it does not have the tools to explicitly handle uncertainty and vagueness. One of the related frameworks to this paradigm is Fuzzy Logic Programming, which integrates concepts coming from Fuzzy Logic into Logic Programming to solve the disad- vantages of traditional logic languages when dealing with uncertainty and ambiguity.
    [Show full text]
  • IN112 Mathematical Logic Lab Session on Prolog
    Institut Supérieur de l’Aéronautique et de l’Espace IN112 Mathematical Logic Lab session on Prolog Christophe Garion DMIA – ISAE Christophe Garion IN112 IN112 Mathematical Logic 1/ 31 License CC BY-NC-SA 3.0 This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported license (CC BY-NC-SA 3.0) You are free to Share (copy, distribute and transmite) and to Remix (adapt) this work under the following conditions: Attribution – You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). Noncommercial – You may not use this work for commercial purposes. Share Alike – If you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. See http://creativecommons.org/licenses/by-nc-sa/3.0/. Christophe Garion IN112 IN112 Mathematical Logic 2/ 31 Outline 1 Prolog: getting started! 2 Interpreting and querying 3 Unification and assignement 4 Lists 5 Negation by failure 6 Misc. Christophe Garion IN112 IN112 Mathematical Logic 3/ 31 Outline 1 Prolog: getting started! 2 Interpreting and querying 3 Unification and assignement 4 Lists 5 Negation by failure 6 Misc. Christophe Garion IN112 IN112 Mathematical Logic 4/ 31 Prolog interpreter Prolog is an interpreted language: no executable is created (even if it is possible) a Prolog program is loaded into the interpreter queries are executed on this program through the interpreter We will use the GNU Prolog interpreter.
    [Show full text]
  • Introducción a Linux Equivalencias Windows En Linux Ivalencias
    No has iniciado sesión Discusión Contribuciones Crear una cuenta Acceder Página discusión Leer Editar Ver historial Buscar Introducción a Linux Equivalencias Windows en Linux Portada < Introducción a Linux Categorías de libros Equivalencias Windows en GNU/Linux es una lista de equivalencias, reemplazos y software Cam bios recientes Libro aleatorio análogo a Windows en GNU/Linux y viceversa. Ayuda Contenido [ocultar] Donaciones 1 Algunas diferencias entre los programas para Windows y GNU/Linux Comunidad 2 Redes y Conectividad Café 3 Trabajando con archivos Portal de la comunidad 4 Software de escritorio Subproyectos 5 Multimedia Recetario 5.1 Audio y reproductores de CD Wikichicos 5.2 Gráficos 5.3 Video y otros Imprimir/exportar 6 Ofimática/negocios Crear un libro 7 Juegos Descargar como PDF Versión para im primir 8 Programación y Desarrollo 9 Software para Servidores Herramientas 10 Científicos y Prog s Especiales 11 Otros Cambios relacionados 12 Enlaces externos Subir archivo 12.1 Notas Páginas especiales Enlace permanente Información de la Algunas diferencias entre los programas para Windows y y página Enlace corto GNU/Linux [ editar ] Citar esta página La mayoría de los programas de Windows son hechos con el principio de "Todo en uno" (cada Idiomas desarrollador agrega todo a su producto). De la misma forma, a este principio le llaman el Añadir enlaces "Estilo-Windows". Redes y Conectividad [ editar ] Descripción del programa, Windows GNU/Linux tareas ejecutadas Firefox (Iceweasel) Opera [NL] Internet Explorer Konqueror Netscape /
    [Show full text]
  • GNU/Linux AI & Alife HOWTO
    GNU/Linux AI & Alife HOWTO GNU/Linux AI & Alife HOWTO Table of Contents GNU/Linux AI & Alife HOWTO......................................................................................................................1 by John Eikenberry..................................................................................................................................1 1. Introduction..........................................................................................................................................1 2. Traditional Artificial Intelligence........................................................................................................1 3. Connectionism.....................................................................................................................................1 4. Evolutionary Computing......................................................................................................................1 5. Alife & Complex Systems...................................................................................................................1 6. Agents & Robotics...............................................................................................................................1 7. Programming languages.......................................................................................................................2 8. Missing & Dead...................................................................................................................................2 1. Introduction.........................................................................................................................................2
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • An Empirical Study of Constraint Logic Programming and Answer Set Programming Solutions of Combinatorial Problems∗
    An Empirical Study of Constraint Logic Programming and Answer Set Programming Solutions of Combinatorial Problems∗ Agostino Dovier† Andrea Formisano‡ Enrico Pontelli§ Abstract This paper presents experimental comparisons between the declarative encod- ings of various computationally hard problems in both Answer Set Programming (ASP) and Constraint Logic Programming over finite domains (CLP(FD)). The objective is to investigate how the solvers in the two domains respond to differ- ent problems, highlighting strengths and weaknesses of their implementations and suggesting criteria for choosing one approach versus the other. Ultimately, the work in this paper is expected to lay the foundations for transfer of technology between the two domains, e.g., suggesting ways to use CLP(FD) in the execution of ASP. Keywords. Declarative Programming, Constraint Logic Programming, An- swer Set Programming, Solvers, Benchmarking. 1 Introduction The objective of this work is to experimentally compare the use of two distinct logic- based paradigms, traditionally recognized as excellent tools to tackle computationally hard problems. The two paradigms considered are Answer Set Programming (ASP) [2] and Constraint Logic Programming over Finite Domains (CLP(FD)) [27]. The moti- vation for this investigation arises from the successful use of both paradigms in dealing with various classes of combinatorial problems, and the need to better understand their respective strengths and weaknesses. Ultimately, we hope this work will indicate meth- ods for integration and cooperation between the two paradigms (e.g., along the lines of [10, 11]). ∗A preliminary version of this paper appeared in the Proceedings of the International Conference on Logic Programming, LNCS 3668, pp. 67–82, Springer Verlag, 2005.
    [Show full text]