root/tags/lgt2311/libpaths/NOTES.txt

Revision 4000, 2.4 KB (checked in by pmoura, 12 months ago)

Updated copyright string.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1================================================================
2Logtalk - Open source object-oriented logic programming language
3Release 2.31.1
4
5Copyright (c) 1998-2008 Paulo Moura.  All Rights Reserved.
6================================================================
7
8This folder contains a Prolog file, "libpaths.pl", which, when loaded,
9defines the library paths for the Logtalk standard library and for all
10the supplied examples. You may customize this file by adding the paths
11to your own "libraries" in order to easily load your own source code.
12
13In order to easily compile and load library and example source files using
14the notation <library>(<entity>), you will need to load the "libpaths.pl"
15into your Prolog compiler after loading the Logtalk compiler/runtime.
16
17You might need to edit the "libpaths.pl" file in order to adapt it to
18reflect your Logtalk installation, Prolog compiler, and operating-system
19requirements (for example, some Prolog compilers do not accept or expand
20environment variables occurring on paths).
21
22As defined, the provided "libpaths.pl" file is already compatible with
23some of the most popular Prolog compilers, running on MacOS X, Linux,
24Windows, Unix, and Unix-like operating-systems.
25
26The Prolog integration scripts, found on the "integration" directory,
27automatically load the copy of the "libpaths.pl" file from the Logtalk
28end-user directory created by the "scripts/cplgtdirs.*" scripts. See the
29"INSTALL.txt" and "scripts/NOTES.txt" files for more details. Note that
30some Prolog compilers do not support the <library>(<entity>) notation.
31See the "configs/NOTES.txt" file for details.
32
33The somehow contrived code found on the "libpaths.pl" file is needed to
34ensure compatibility with both the ISO Prolog standard and with most
35Prolog compilers. The code could be greatly simplified by using a multifile
36predicate directive for the library path dynamic predicate. Unfortunately,
37not all Prolog compilers support multifile predicates.
38
39Prolog compilers that are expected to be compatible with the provided
40"libpaths.pl" file as is, across operating-systems:
41
42    * B-Prolog
43    * CIAO
44    * CxProlog
45    * ECLiPSe
46    * GNU-Prolog
47    * K-Prolog
48    * Qu-Prolog
49    * SICStus Prolog
50    * SWI-Prolog
51    * YAP
52    * XSB
53
54Prolog compilers that imply editing the provided "libpaths.pl" file due
55to the lack of support for expanding environment variables on paths:
56
57    * Amzi! Prolog
58    * IF/Prolog
59    * JIProlog
60
61Feedback on other Prolog compilers is most appreciated.
Note: See TracBrowser for help on using the browser.