Changeset 1191
- Timestamp:
- 07/25/04 11:15:53 (4 years ago)
- Location:
- trunk
- Files:
-
- 11 modified
-
examples/NOTES (modified) (1 diff)
-
INSTALL (modified) (1 diff)
-
library/dates.notes (modified) (1 diff)
-
library/events.notes (modified) (1 diff)
-
library/hierarchies.notes (modified) (1 diff)
-
library/NOTES (modified) (3 diffs)
-
library/types.notes (modified) (1 diff)
-
misc/NOTES (modified) (1 diff)
-
README (modified) (1 diff)
-
RELEASE_NOTES (modified) (1 diff)
-
scripts/NOTES (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/examples/NOTES
r1151 r1191 10 10 description of each example is included below. 11 11 12 Each example contains a NOTES file and a loader utility file that may13 be used to load all the example entities. In addition, most examples12 Each example folder contains a NOTES file and a loader helper file which 13 may be used to load all the example entities. In addition, most examples 14 14 contain a SCRIPT file with sample queries for your to try. 15 15 16 Most of these examples need objects, protocols, and categories that17 are defined in the Logtalk standard library or in other examples, so18 you should load them first (see the NOTES files inside the library19 folder andthe NOTES file inside each example folder).16 Most of these examples need objects, protocols, and categories which are 17 defined in the Logtalk standard library or in other examples, so you 18 should load them first (see the NOTES files inside the library folder and 19 the NOTES file inside each example folder). 20 20 21 21 Some examples may redefine objects already loaded from other examples. 22 22 You may want to restart Logtalk after trying each example. 23 23 24 Some of the examples code have been adopted from public available 25 Prolog code and from known Prolog text books and are copyrighted by26 the respectiveauthors.24 Some of the examples code have been adopted from public available Prolog 25 code and from known Prolog text books and are copyrighted by the respective 26 authors. 27 27 28 These are programming examples, meaning that you should study the 29 sourcefiles to fully understand them.28 These are programming examples, meaning that you should study the source 29 files to fully understand them. 30 30 31 31 All examples are formatted using four spaces tabs. 32 32 33 33 By default, compiling an example generates a .xml documenting file for each 34 compiled entity (object, category, or protocol). See the xml sub-directory35 for instructions on how to browse the .xml files for on-line reading or how36 toconvert the files to a print-ready format such as PDF.34 compiled entity (object, category, or protocol). See the xml folder for 35 instructions on how to browse the .xml files for on-line reading or how to 36 convert the files to a print-ready format such as PDF. 37 37 38 38 -
trunk/INSTALL
r1182 r1191 17 17 INSTALLING FOR A SINGLE USER 18 18 19 In the case of a single user, the Logtalk directory can simply be20 copied tothe user home directory.19 In the case of a single user, the Logtalk directory may simply be copied to 20 the user home directory. 21 21 22 22 23 23 INSTALLING FOR MULTIPLE USERS 24 24 25 In the case of multiple users, the Logtalk directory can be copied to 26 anylocation that its accessible by all the users.25 In the case of multiple users, the Logtalk directory can be copied to any 26 location that its accessible by all the users. 27 27 28 28 Regarding directory and file permissions, it is advisable to make all files -
trunk/library/dates.notes
r1151 r1191 17 17 18 18 Please note that some of the functionality of these objects depends 19 on the usedProlog support for accessing operating system time and19 on the chosen Prolog support for accessing operating system time and 20 20 date values. -
trunk/library/events.notes
r1151 r1191 17 17 The protocol event_handlersp declares the two basic event handler predicates 18 18 (before/3 and after/3). You will need to refer this protocol in your objects 19 if you needto use the super control structure (^^/1) with these predicates.19 if you want to use the super control structure (^^/1) with these predicates. 20 20 21 21 The monitor object implements more sophisticated event handling predicates. 22 22 23 Some of the objects assume that the usedProlog compiler defines the23 Some of the objects assume that the chosen Prolog compiler defines the 24 24 usual sort/2 built-in predicate. -
trunk/library/hierarchies.notes
r1151 r1191 12 12 | ?- logtalk_load(hierarchies_loader). 13 13 14 These objects implement reflection predicates over class /instance15 and prototypehierarchies.14 These objects implement reflection predicates over class and prototype 15 hierarchies. -
trunk/library/NOTES
r1151 r1191 7 7 8 8 9 This folder contains objects, categories, and protocols that implement 10 predicates for dealing with common Prolog types and structures. 9 This folder contains some useful objects, categories, and protocols. 11 10 12 11 To load a group of objects, protocols, and categories in this library … … 56 55 | ?- logtalk_load(all_loader). 57 56 58 Specific notes about each group of objects, categories, and protocols 59 can befound in the corresponding *.notes files.57 Specific notes about each group of objects, categories, and protocols can be 58 found in the corresponding *.notes files. 60 59 61 Some of the files contained in this directory represent work in progress 62 a nd are not loaded by default by any loader utility file.60 Some of the files contained in this directory represent work in progress and 61 are not loaded by default by any loader utility file. 63 62 64 Some of the code in this library is based on public domain Prolog code, 65 inparticular, code adopted from the Edinburgh Prolog library. The definition63 Some of the code in this library is based on public domain Prolog code, in 64 particular, code adopted from the Edinburgh Prolog library. The definition 66 65 of predicate reverse/2 in object list is from Richard O'Keefe and can be found 67 66 in its book "The Craft of Prolog". … … 70 69 documenting file for each compiled entity (object, category, or protocol). 71 70 See the xml sub-directory for instructions on how to browse the .xml files 72 for on-line reading or how to convert the files to print-ready format. 71 for on-line reading or how to convert the files to a print-ready format such 72 as PDF. 73 73 74 74 All source files are formatted using four-spaces tabs. -
trunk/library/types.notes
r1151 r1191 13 13 14 14 These objects implement predicates over common Prolog terms and 15 structures like lists, diffrence lists, binary trees, dictionaries,16 and queues.15 structures such as lists, difference lists, binary trees, queues, 16 dictionaries, and sets. -
trunk/misc/NOTES
r1151 r1191 61 61 62 62 make_xsblgt.sh 63 makes a script named ciaolgt for running Logtalk with XSB63 makes a script named xsblgt for running Logtalk with XSB 64 64 65 65 These scripts require the environment variable LOGTALKHOME (pointing to the -
trunk/README
r1151 r1191 36 36 http://www.logtalk.org/ 37 37 38 At this address you can also find useful documentation and information38 At this address you can also find additional documentation and information 39 39 about Logtalk. 40 40 -
trunk/RELEASE_NOTES
r1188 r1191 17 17 on single entity source files plus loading and compiling helper files. 18 18 19 Updated URL used on the automatically generated XML documenting files19 Updated the URL used on the automatically generated XML documenting files 20 20 when compiling entities with the option doctype(web). 21 21 -
trunk/scripts/NOTES
r1151 r1191 61 61 62 62 make_xsblgt.sh 63 makes a script named ciaolgt for running Logtalk with XSB63 makes a script named xsblgt for running Logtalk with XSB 64 64 65 65 These scripts require the environment variable LOGTALKHOME (pointing to the
