The XSB System Version 2.4 Volume 1: Programmer's Manual

Total Page:16

File Type:pdf, Size:1020Kb

The XSB System Version 2.4 Volume 1: Programmer's Manual The XSB System Version 2.4 Volume 1: Programmer’s Manual Konstantinos Sagonas Terrance Swift David S. Warren Juliana Freire Prasad Rao Baoqiu Cui Ernie Johnson with contributions from Steve Dawson Michael Kifer July 13, 2001 Credits Day-to-day care and feeding of XSB including bug fixes, ports, and configuration man- agement has been done by Kostis Sagonas, David Warren, Terrance Swift, Prasad Rao, Steve Dawson, Juliana Freire, Ernie Johnson, Baoqiu Cui, Michael Kifer, and Bart Demoen. In Version 2.4, the core engine development of the SLG-WAM has been mainly imple- mented by Terrance Swift, Kostis Sagonas, Prasad Rao, and Juliana Freire. The break- down, roughly, was that Terrance Swift wrote the initial tabling engine and builtins. Prasad Rao reimplemented the engine’s tabling subsystem to use tries for variant-based table access while Kostis Sagonas implemented most of tabled negation. Juliana Freire revised the table scheduling mechanism starting from Version 1.5.0 to create a more efficient engine, and implemented the engine for local evaluation. Starting from XSB Version 2.0, XSB includes another tabling engine, CHAT, which was designed and developed by Kostis Sagonas and Bart Demoen. CHAT supports heap garbage collection (both based on a mark&slide and on a mark&copy algorithm) which was developed and implemented by Bart Demoen and Kostis Sagonas. Memory expansion code for WAM stacks was written by Ernie Johnson and Bart De- moen, while memory management code for CHAT areas was written by Bart Demoen and Kostis Sagonas. Rui Marques improved the trailing of the SLG-WAM and rewrote much of the engine to make it compliant with 64-bit architectures. Assert and retract code was based on code written by Jiyang Xu and significantly revised by David S. Warren and Rui Marques. Trie assert and retract code was written by Prasad Rao. The current version of findall/3 was re-written from scratch by Bart Demoen. In Version 2.3, the tabling subsystem and its interface to the engine have been extended for the support of subsumption-based tabling. This extension was developed and im- plemented by Ernie Johnson. In the XSB complier, Kostis Sagonas was responsible for HiLog compilation and associ- ated builtins. Steve Dawson implemented Unification Factoring. The auto table and suppl table directives were written by Kostis Sagonas. The DCG expansion module was written by Kostis Sagonas. The handling of the multifile directive was written by Baoqiu Cui. C.R. Ramakrishnan wrote the mode analyzer for XSB. The safety check for tabling within the scope of cuts was written by Kate Dvortsova. Michael Kifer rewrote parts of the XSB code to make XSB configurable with GNU’s Autoconf. Harald Schroepfer helped the XSB group with the Solaris port, and Yiorgos Adamopoulos suggested the bits to use for the HP-700 series port. Steven Dawson, Larry B. Daniel and Franklin Chen were responsible for the MkLinux and Solaris x86 ports. GPP, the source code preprocessor used by XSB, was written by Denis Auroux. He also wrote the GPP manual reproduced in Appendix A. The starting point of XSB (in 1990) was PSB-Prolog 2.0 by Jiyang Xu. PSB-Prolog in its turn was based on SB-Prolog, primarily designed and written by Saumya Debray, David S. Warren, and Jiyang Xu. Thanks are also due to Weidong Chen for his work 2 on Prolog clause indexing for SB-Prolog and to Richard O’Keefe, who contributed the Prolog code for the Prolog reader and the C code for the tokenizer. Contents 1 Introduction 1 2 Getting Started with XSB 5 2.1 Installing XSB under UNIX ................................ 5 2.1.1 Possible Installation Problems ........................... 7 2.2 Installing XSB under Windows .............................. 8 2.2.1 Using Cygnus Software’s CygWin32 ....................... 8 2.2.2 Using Microsoft Visual C++ ........................... 8 2.3 Invoking XSB ........................................ 9 2.4 Compiling XSB programs ................................. 10 2.5 Sample XSB Programs ................................... 10 2.6 Exiting XSB ........................................ 11 3 System Description 12 3.1 Entering and Exiting XSB ................................. 12 3.2 The System and its Directories .............................. 13 3.3 The Module System of XSB ................................ 13 3.4 The Dynamic Loader and its Search Path ........................ 16 3.4.1 Changing the Default Search Path and the Packaging System ......... 16 3.4.2 Dynamically loading predicates in the interpreter ................ 18 3.5 Command Line Arguments ................................ 18 3.6 Memory Management ................................... 22 3.7 Compiling and Consulting ................................. 22 3.8 The Compiler ........................................ 24 3.8.1 Invoking the Compiler ............................... 24 i CONTENTS ii 3.8.2 Compiler Options ................................. 25 3.8.3 Specialization .................................... 29 3.8.4 Compiler Directives ................................ 31 3.8.5 Inline Predicates .................................. 36 4 Syntax 37 4.1 Terms ............................................ 37 4.1.1 Integers ....................................... 37 4.1.2 Floating-point Numbers .............................. 38 4.1.3 Atoms ........................................ 38 4.1.4 Variables ...................................... 39 4.1.5 Compound Terms ................................. 39 4.1.6 Lists ......................................... 40 4.2 From HiLog to Prolog ................................... 42 4.3 Operators .......................................... 43 5 Using Tabling in XSB: A Tutorial Introduction 47 5.1 XSB as a Prolog System .................................. 47 5.2 Definite Programs ..................................... 48 5.2.1 Tabling Strategies ................................. 49 5.2.2 Tabling Directives and Declarations ....................... 50 5.2.3 Interaction Between Prolog Constructs and Tabling .............. 53 5.2.4 Potential Pitfalls in Tabling ............................ 55 5.3 Normal Programs ...................................... 56 5.3.1 Stratified Normal Programs ............................ 56 5.3.2 Non-stratified Programs .............................. 58 5.3.3 On Beyond Zebra: Implementing Other Semantics for Non-stratified Programs 62 5.4 Tabled Aggregation ..................................... 64 5.4.1 Local Evaluation .................................. 66 6 Standard Predicates 67 6.1 Input and Output ..................................... 67 6.1.1 File Handling .................................... 67 CONTENTS iii 6.1.2 Character I/O ................................... 69 6.1.3 Term I/O ...................................... 70 6.2 Convenience ......................................... 74 6.3 Negation and Control ................................... 74 6.4 Meta-Logical ........................................ 76 6.5 All Solutions and Aggregate Predicates .......................... 90 6.5.1 Tabling Aggregate Predicates ........................... 92 6.6 Comparison ......................................... 96 6.7 Meta-Predicates ...................................... 98 6.8 Information about the State of the Program ....................... 99 6.9 Modification of the Database ............................... 110 6.9.1 The storage Module: Associative Arrays and Backtrackable Updates .... 113 6.10 Execution State ....................................... 115 6.11 Exception Handling .................................... 119 6.12 Tabled Predicate Manipulations .............................. 120 6.12.1 Operators for Declaring and Modifying Tabled Predicates ........... 122 6.12.2 Predicates for Table Inspection .......................... 122 6.12.3 Deleting Tables and Table Components ..................... 130 7 Hooks 131 7.1 Adding and Removing Hooks ............................... 131 7.2 Hooks Supported by XSB ................................. 132 8 Debugging 135 8.1 High-Level Tracing ..................................... 135 8.2 Low-Level Tracing ..................................... 138 9 Definite Clause Grammars 140 9.1 General Description .................................... 140 9.2 Translation of Definite Clause Grammar rules ...................... 141 9.2.1 Definite Clause Grammars and Tabling ..................... 143 9.3 Definite Clause Grammar predicates ........................... 144 9.4 Two differences with other Prologs ............................ 146 CONTENTS iv 10 Restrictions and Current Known Bugs 148 10.1 Current Restrictions .................................... 148 10.2 Known Bugs ........................................ 149 A GPP - Generic Preprocessor 151 A.1 Description ......................................... 151 A.2 Syntax ............................................ 152 A.3 Options ........................................... 152 A.4 Syntax Specification .................................... 155 A.5 Evaluation Rules ...................................... 158 A.6 Meta-macros ........................................ 159 A.7 Examples .......................................... 162 A.8 Advanced Examples .................................... 167 A.9 Author ............................................ 169 Chapter 1 Introduction XSB is a research-oriented Logic Programming system for Unix and Windows-based systems. In addition to providing all the functionality of Prolog, XSB contains several features not usually found in Logic Programming systems, including • Evaluation according
Recommended publications
  • Intercepting Functions for Memoization Arjun Suresh
    Intercepting Functions for Memoization Arjun Suresh To cite this version: Arjun Suresh. Intercepting Functions for Memoization. Other [cs.OH]. Université de Rennes 1, 2016. English. tel-01410539v1 HAL Id: tel-01410539 https://hal.inria.fr/tel-01410539v1 Submitted on 6 Dec 2016 (v1), last revised 11 May 2017 (v2) HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. ANNEE´ 2016 THESE` / UNIVERSITE´ DE RENNES 1 sous le sceau de l’Universite´ Bretagne Loire En Cotutelle Internationale avec pour le grade de DOCTEUR DE L’UNIVERSITE´ DE RENNES 1 Mention : Informatique Ecole´ doctorale Matisse present´ ee´ par Arjun SURESH prepar´ ee´ a` l’unite´ de recherche INRIA Institut National de Recherche en Informatique et Automatique Universite´ de Rennes 1 These` soutenue a` Rennes Intercepting le 10 Mai, 2016 devant le jury compose´ de : Functions Fabrice RASTELLO Charge´ de recherche Inria / Rapporteur Jean-Michel MULLER for Directeur de recherche CNRS / Rapporteur Sandrine BLAZY Memoization Professeur a` l’Universite´ de Rennes 1 / Examinateur Vincent LOECHNER Maˆıtre de conferences,´ Universite´ Louis Pasteur, Stras- bourg / Examinateur Erven ROHOU Directeur de recherche INRIA / Directeur de these` Andre´ SEZNEC Directeur de recherche INRIA / Co-directeur de these` If you save now you might benefit later.
    [Show full text]
  • Bbedit 13.5 User Manual
    User Manual BBEdit™ Professional Code and Text Editor for the Macintosh Bare Bones Software, Inc. ™ BBEdit 13.5 Product Design Jim Correia, Rich Siegel, Steve Kalkwarf, Patrick Woolsey Product Engineering Jim Correia, Seth Dillingham, Matt Henderson, Jon Hueras, Steve Kalkwarf, Rich Siegel, Steve Sisak Engineers Emeritus Chris Borton, Tom Emerson, Pete Gontier, Jamie McCarthy, John Norstad, Jon Pugh, Mark Romano, Eric Slosser, Rob Vaterlaus Documentation Fritz Anderson, Philip Borenstein, Stephen Chernicoff, John Gruber, Jeff Mattson, Jerry Kindall, Caroline Rose, Allan Rouselle, Rich Siegel, Vicky Wong, Patrick Woolsey Additional Engineering Polaschek Computing Icon Design Bryan Bell Factory Color Schemes Luke Andrews Additional Color Schemes Toothpaste by Cat Noon, and Xcode Dark by Andrew Carter. Used by permission. Additional Icons By icons8. Used under license Additional Artwork By Jonathan Hunt PHP keyword lists Contributed by Ted Stresen-Reuter. Previous versions by Carsten Blüm Published by: Bare Bones Software, Inc. 73 Princeton Street, Suite 206 North Chelmsford, MA 01863 USA (978) 251-0500 main (978) 251-0525 fax https://www.barebones.com/ Sales & customer service: [email protected] Technical support: [email protected] BBEdit and the BBEdit User Manual are copyright ©1992-2020 Bare Bones Software, Inc. All rights reserved. Produced/published in USA. Copyrights, Licenses & Trademarks cmark ©2014 by John MacFarlane. Used under license; part of the CommonMark project LibNcFTP Used under license from and copyright © 1996-2010 Mike Gleason & NcFTP Software Exuberant ctags ©1996-2004 Darren Hiebert (source code here) PCRE2 Library Written by Philip Hazel and Zoltán Herczeg ©1997-2018 University of Cambridge, England Info-ZIP Library ©1990-2009 Info-ZIP.
    [Show full text]
  • DFDL WG Stephen M Hanson, IBM [email protected] September 2014
    GFD-P-R.207 (OBSOLETED by GFD-P-R.240) Michael J Beckerle, Tresys Technology OGF DFDL WG Stephen M Hanson, IBM [email protected] September 2014 Data Format Description Language (DFDL) v1.0 Specification Status of This Document Grid Final Draft (GFD) Obsoletes This document obsoletes GFD-P-R.174 dated January 2011 [OBSOLETE_DFDL]. Copyright Notice Copyright © Global Grid Forum (2004-2006). Some Rights Reserved. Distribution is unlimited. Copyright © Open Grid Forum (2006-2014). Some Rights Reserved. Distribution is unlimited Abstract This document is OBSOLETE. It is superceded by GFD-P-R.240. This document provides a definition of a standard Data Format Description Language (DFDL). This language allows description of text, dense binary, and legacy data formats in a vendor- neutral declarative manner. DFDL is an extension to the XML Schema Description Language (XSDL). GFD-P-R.207 (OBSOLETED by GFD-P-R.240) September 2014 Contents Data Format Description Language (DFDL) v1.0 Specification ...................................................... 1 1. Introduction ............................................................................................................................... 9 1.1 Why is DFDL Needed? ................................................................................................... 10 1.2 What is DFDL? ................................................................................................................ 10 Simple Example ......................................................................................................
    [Show full text]
  • Intercepting Functions for Memoization Arjun Suresh
    Intercepting functions for memoization Arjun Suresh To cite this version: Arjun Suresh. Intercepting functions for memoization. Programming Languages [cs.PL]. Université Rennes 1, 2016. English. NNT : 2016REN1S106. tel-01410539v2 HAL Id: tel-01410539 https://tel.archives-ouvertes.fr/tel-01410539v2 Submitted on 11 May 2017 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. ANNEE´ 2016 THESE` / UNIVERSITE´ DE RENNES 1 sous le sceau de l’Universite´ Bretagne Loire En Cotutelle Internationale avec pour le grade de DOCTEUR DE L’UNIVERSITE´ DE RENNES 1 Mention : Informatique Ecole´ doctorale Matisse present´ ee´ par Arjun SURESH prepar´ ee´ a` l’unite´ de recherche INRIA Institut National de Recherche en Informatique et Automatique Universite´ de Rennes 1 These` soutenue a` Rennes Intercepting le 10 Mai, 2016 devant le jury compose´ de : Functions Fabrice RASTELLO Charge´ de recherche Inria / Rapporteur Jean-Michel MULLER for Directeur de recherche CNRS / Rapporteur Sandrine BLAZY Memoization Professeur a` l’Universite´ de Rennes 1 / Examinateur Vincent LOECHNER Maˆıtre de conferences,´ Universite´ Louis Pasteur, Stras- bourg / Examinateur Erven ROHOU Directeur de recherche INRIA / Directeur de these` Andre´ SEZNEC Directeur de recherche INRIA / Co-directeur de these` If you save now you might benefit later.
    [Show full text]
  • Notetab User Manual
    NoteTab User Manual Copyright © 1995-2016, FOOKES Holding Ltd, Switzerland NoteTab® Tame Your Text with NoteTab by FOOKES Holding Ltd A leading-edge text and HTML editor. Handle a stack of huge files with ease, format text, use a spell-checker, and perform system-wide searches and multi-line global replacements. Build document templates, convert text to HTML on the fly, and take charge of your code with a bunch of handy HTML tools. Use a power-packed scripting language to create anything from a text macro to a mini-application. Winner of top industry awards since 1998. “NoteTab” and “Fookes” are registered trademarks of Fookes Holding Ltd. All other trademarks and service marks, both marked and not marked, are the property of their respective ow ners. NoteTab® Copyright © 1995-2016, FOOKES Holding Ltd, Switzerland All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the written permission of the publisher. “NoteTab” and “Fookes” are registered trademarks of Fookes Holding Ltd. All other trademarks and service marks, both marked and not marked, are the property of their respective owners. While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for errors or omissions, or for damages resulting from the use of information contained in this document or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or indirectly by this document.
    [Show full text]
  • Sample Chapter 3
    108_GILLAM.ch03.fm Page 61 Monday, August 19, 2002 1:58 PM 3 Architecture: Not Just a Pile of Code Charts f you’re used to working with ASCII or other similar encodings designed I for European languages, you’ll find Unicode noticeably different from those other standards. You’ll also find that when you’re dealing with Unicode text, various assumptions you may have made in the past about how you deal with text don’t hold. If you’ve worked with encodings for other languages, at least some characteristics of Unicode will be familiar to you, but even then, some pieces of Unicode will be unfamiliar. Unicode is more than just a big pile of code charts. To be sure, it includes a big pile of code charts, but Unicode goes much further. It doesn’t just take a bunch of character forms and assign numbers to them; it adds a wealth of infor- mation on what those characters mean and how they are used. Unlike virtually all other character encoding standards, Unicode isn’t de- signed for the encoding of a single language or a family of closely related lan- guages. Rather, Unicode is designed for the encoding of all written languages. The current version doesn’t give you a way to encode all written languages (and in fact, this concept is such a slippery thing to define that it probably never will), but it does provide a way to encode an extremely wide variety of lan- guages. The languages vary tremendously in how they are written, so Unicode must be flexible enough to accommodate all of them.
    [Show full text]
  • Pdflib API Reference 9.0.1
    ABC PDFlib, PDFlib+PDI, PPS A library for generating PDF on the fly PDFlib 9.0.1 API Reference For use with C, C++, Cobol, COM, Java, .NET, Objective-C, Perl, PHP, Python, REALbasic/Xojo, RPG, Ruby Copyright © 1997–2013 PDFlib GmbH and Thomas Merz. All rights reserved. PDFlib users are granted permission to reproduce printed or digital copies of this manual for internal use. PDFlib GmbH Franziska-Bilek-Weg 9, 80339 München, Germany www.pdflib.com phone +49 • 89 • 452 33 84-0 fax +49 • 89 • 452 33 84-99 If you have questions check the PDFlib mailing list and archive at tech.groups.yahoo.com/group/pdflib Licensing contact: [email protected] Support for commercial PDFlib licensees: [email protected] (please include your license number) This publication and the information herein is furnished as is, is subject to change without notice, and should not be construed as a commitment by PDFlib GmbH. PDFlib GmbH assumes no responsibility or lia- bility for any errors or inaccuracies, makes no warranty of any kind (express, implied or statutory) with re- spect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for par- ticular purposes and noninfringement of third party rights. PDFlib and the PDFlib logo are registered trademarks of PDFlib GmbH. PDFlib licensees are granted the right to use the PDFlib name and logo in their product documentation. However, this is not required. Adobe, Acrobat, PostScript, and XMP are trademarks of Adobe Systems Inc. AIX, IBM, OS/390, WebSphere, iSeries, and zSeries are trademarks of International Business Machines Corporation.
    [Show full text]
  • Locale Database
    International Language Environments Guide Part No: 817–2521–11 November 2010 Copyright © 2005, 2010, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related software documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are “commercial computer software” or “commercial technical data” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
    [Show full text]
  • A Simple Interface for Non Standard Knowledge Systems (SINKS)
    A Simple Interface for Non Standard Knowledge Systems (SINKS) A Writing Project Presented to The Faculty of the Department of Computer Science San Jose State University In Partial Fulfillment of the Requirement for the Degree Master of Science By Harini Rao December 2003 1 © December 2003 Harini Rao [email protected] ALL RIGHTS RESERVED 2 APPROVED FOR THE DEPARTMENT OF COMPUTER SCIENCE Dr. Christopher Pollett Dr. Archana Sathaye Dr. Suneuy Kim APPROVED FOR THE UNIVERSITY 3 Abstract Deductive database systems combine a declarative style for formulating queries and constraints with efficient and reliable database technology for mass-memory data storage. They have the ability to use a logic programming style for expressing deductions concerning the contents of a database. Currently, most of the deductive-style databases such as NAIL!, LDL, CORAL, XSB, etc. usually act as front-ends to a more traditional relational database. It might make it easier to deploy a deductive database system as a back end for a relational database since, then only, the designer of the database needs to understand the non-standard knowledge system and the application programmers can use the SQL they know and love. The purpose of this project is to develop an interface system whereby non-standard knowledge systems such as XSB can make their resources available as a backend to a more traditional relational database, Oracle. 4 Table of contents Page 1. Introduction …………………………………………………………....6 2. Deductive Databases …………………………………………………..8 3. XSB ……………………………………………………………………26 4. Oracle–XSB Interface …………………………………………………29 5. Design ………………………………………………………….………31 6. Implementation ………………………………………………………...36 7. Applications …………………………………………………….……..56 8. Future Enhancements …………………………………………………58 9. Conclusion …………………………………………………………….60 Bibliography ……………………………………………………………62 5 1.Introduction The relational data model is the most well-known and widely used data model.
    [Show full text]
  • C++ Reading a Line of Text
    C++ Reading a Line of Text Because there are times when you do not want to skip whitespace before inputting a character, there is a function to input the next character in the stream regardless of what it is. The function is named get and is applied as shown. cin.get(character); The next character in the input stream is returned in char variable character. If the previous input was a numeric value, character contains whatever character ended the inputting of the value. There are also times when you want to skip the rest of the values on a line and go to the beginning of the next line. A function named ignore defined in file <iostream> allows you to do this. It has two parameters. The first is an int expression and the second is a character. This function skips the number of characters specified in the first parameter or all the characters up to and including the character specified in the second parameter, whichever comes first. For example, cin.ignore(80, '\n'); skips 80 characters or skips to the beginning of the next line depending on whether a newline character is encountered before 80 characters are skipped (read and discarded). As another example, consider: cin.ignore(4,’g’); cin.get(c); cout << c << endl; If the input to this program is “agdfg” then the input is ignored up to and including the ‘g’ so the next character read is ‘d’. The letter “d” is then output. If the input to this program is “abcdef” then the input is ignored for the first four characters, so the next character read is ‘e’.
    [Show full text]
  • Comparative Programming Languages CM20253
    We have briefly covered many aspects of language design And there are many more factors we could talk about in making choices of language The End There are many languages out there, both general purpose and specialist And there are many more factors we could talk about in making choices of language The End There are many languages out there, both general purpose and specialist We have briefly covered many aspects of language design The End There are many languages out there, both general purpose and specialist We have briefly covered many aspects of language design And there are many more factors we could talk about in making choices of language Often a single project can use several languages, each suited to its part of the project And then the interopability of languages becomes important For example, can you easily join together code written in Java and C? The End Or languages And then the interopability of languages becomes important For example, can you easily join together code written in Java and C? The End Or languages Often a single project can use several languages, each suited to its part of the project For example, can you easily join together code written in Java and C? The End Or languages Often a single project can use several languages, each suited to its part of the project And then the interopability of languages becomes important The End Or languages Often a single project can use several languages, each suited to its part of the project And then the interopability of languages becomes important For example, can you easily
    [Show full text]
  • The XSB System Version 3.7 Volume 2: Interfaces and Packages
    The XSB System Version 3.7 Volume 2: Interfaces and Packages July 6, 2016 Credits Packages and interfaces have become an increasingly important part of XSB. They are an important way to incorporate code from other systems into XSB, and to interface XSB to databases and other stores. Most of the packages had significant contributions by people other than the core XSB developers, for which we are grateful. As a result most chapters have information about its authors. Contents 1 XSB-ODBC Interface1 1.1 Introduction....................................1 1.2 Using the Interface................................2 1.2.1 Connecting to and Disconnecting from Data Sources.........2 1.2.2 Accessing Tables in Data Sources Using SQL..............3 1.2.3 Cursor Management...........................5 1.2.4 Accessing Tables in Data Sources through the Relation Level.....6 1.2.5 Using the Relation Level Interface....................6 1.2.6 Handling NULL values..........................8 1.2.7 The View Level Interface......................... 10 1.2.8 Insertions and Deletions of Rows through the Relational Level.... 13 1.2.9 Access to Data Dictionaries....................... 14 1.2.10 Other Database Operations....................... 15 1.2.11 Transaction Management......................... 15 1.2.12 Interface Flags.............................. 16 1.2.13 Datalog.................................. 17 1.3 Error messages.................................. 17 1.4 Notes on specific ODBC drivers......................... 18 2 The New XSB-Database Interface 19 2.1 Introduction.................................... 19 2.2 Configuring the Interface............................. 19 2.3 Using the Interface................................ 22 i CONTENTS ii 2.3.1 Connecting to and Disconnecting from Databases........... 22 2.3.2 Querying Databases........................... 24 2.4 Error Handling.................................
    [Show full text]