|Did you know ...||Search Documentation:|
|Pack logtalk -- logtalk-3.14.0/QUICK_START.md|
This file is part of Logtalk http://logtalk.org/ Copyright 1998-2018 Paulo Moura <firstname.lastname@example.org>
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ________________________________________________________________________
Install Logtalk by using either the installer provided for your
operating-system (when available) or by following the instructions
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!):
jiplgt(first run may require
xsblgt(first run may require
xsbmtlgt(first run may require
yaplgtOn 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. The first run of the XSB integration shortcuts may require administrator privileges depending on the XSB installation (right-click on the shortcut and select the "Run as administrator" option).
If you get an unexpected failure when using one of the Prolog integration
scripts or shortcuts, consult the
adapters/NOTES.md file in the Logtalk
installation folder for compatibility notes. For the integration scripts,
see also the integration script man page.
manuals/index.html file with a web browser and select the
Tutorial link. This will provide you with a basic understanding of
some of the main Logtalk concepts. You can then go back to the
file, select the `User Manual` link, then the `Installing Logtalk
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.
You may now try some of the provided examples:
examplessub-directory. There you find several sub-directories with ready to run examples and a
NOTES.mdfile containing general instructions and a brief description of each example. Select and open one of the examples sub-directory.
NOTES.mdfile for a description of the example.
SCRIPT.txtfile 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.
Ready to start writing your own programs?
andRunning and debugging Logtalk programs`.
adapters/NOTES.mdfile for important compatibility information about your chosen backend Prolog compiler and for any defined shorthands for commonly used load and make predicates.
codingsub-directory. There you will find syntax support files for popular text editors which enable syntax coloring and other text services when editing Logtalk source files. There's also support for syntax highlighters used for publishing source code.
toolsdirectory contains a comprehensive set of developer tools to help you test, debug, analyze, and document your applications.
settings.lgt, and modify it to define a library alias for your application directory and for defining default compiler flags (see the file
loader-sample.lgtfile, rename it to
loader.lgt, and modify it to load your application source files. You may also copy the
tests-sample.lgtfiles, renaming them to
tests.lgt, and editing them to define and run your application unit tests.