Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tree: 9140cd6932
Fetching contributors…

Cannot retrieve contributors at this time

107 lines (78 sloc) 4.191 kb
================================================================
Logtalk - Open source object-oriented logic programming language
Release 2.44.1
Copyright (c) 1998-2012 Paulo Moura. All Rights Reserved.
Logtalk is free software. You can redistribute it and/or modify
it under the terms of the "Artistic License 2.0" as published by
The Perl Foundation. Consult the "LICENSE.txt" file for details.
================================================================
Quick start
===========
Starting up Logtalk
-------------------
1. Install Logtalk by using either the installer provided for your
operating-system (when available) or by following the instructions
on the "INSTALL.txt" file.
On POSIX operating-systems, the following shell scripts are installed
by default for running Logtalk with selected back-end Prolog compilers
(which must be up-to-date and properly installed before running these
scripts!):
* B-Prolog: bplgt
* CxProlog: cxlgt
* ECLiPSe: eclipselgt
* GNU Prolog: gplgt
* Lean Prolog: lplgt
* Qu-Prolog: qplgt
* SICStus Prolog: sicstuslgt
* SWI-Prolog: swilgt
* XSB: xsblgt (first run must use sudo)
* XSB 64 bits: xsb64lgt (first run must use sudo)
* XSB MT: xsbmtlgt (first run must use sudo)
* XSB MT 64 bits: xsbmt64lgt (first run must use sudo)
* YAP: yaplgt
If you get an unexpected failure when using one of the Prolog integration
scripts, consult the "configs/NOTES.txt" file in the Logtalk installation
folder for compatibility notes or consult the integration script man page.
On MacOS X systems, "/opt/local/bin" must be in your PATH to run the scripts.
Terminal command files for running Logtalk with selected back-end Prolog
compilers are also available on the Logtalk installation folder (by default,
"/opt/local/share/logtalk/scripts/macosx/command_files"; for easy access, the
installer creates an alias to the Logtalk folder in the Applications folder.
On Windows systems, shortcuts for running Logtalk with selected back-end
Prolog compilers are created on the "Start Menu/Programs/Logtalk" menu.
If you get an unexpected failure when using one of the Prolog integration
shortcuts, consult the "configs/NOTES.txt" file in the Logtalk installation
folder for compatibility notes.
2. Open the "manuals/index.html" file with a web browser.
3. Select the "Tutorial" link. This will provide you with a basic
understanding of some of the main Logtalk concepts.
4. Go back to the "index.html" file, select the "User Manual" link, then
the "Installing Logtalk" and "Writing, Running, and Debugging Logtalk
Programs" links. This will provide you with a basic understanding of
how to start Logtalk as well as how to compile and load Logtalk code.
Running the examples
--------------------
You may now try some of the provided examples:
1. Open the "examples" sub-directory. There you find several sub-directories
with ready to run examples and a "NOTES.txt" file containing general
instructions and a brief description of each example. Select and open one
of the examples sub-directory.
2. Read the example "NOTES.txt" file for a description of the example.
3. Open the "SCRIPT.txt" file for instructions on how to load the example
and for sample queries that you may try by copying-and-pasting them to
your Prolog interpreter top-level.
Writing your own programs
_________________________
Ready to start writing your own programs?
1. Read the User Manual sections on "Programming in Logtalk" and "Running
and debugging Logtalk programs".
2. Take a look at the "wenv" sub-directory. There you will find syntax
configuration files for popular text editors which enable syntax coloring
and other text services when editing Logtalk source files.
3. Create a sub-directory with a suitable name to hold all the files of
your application. You may want to define the application directory path
in a "settings.lgt" file in order to easily load your application (see
the file "CUSTOMIZE.txt" for details).
4. Copy to this sub-directory a loader file from one of the example
directories and modify it to load your own source files.
5. Have fun!
Jump to Line
Something went wrong with that request. Please try again.