diogo/yap-6.3
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Logtalk 2.9.2 description files.

Browse Source 
git-svn-id: https://yap.svn.sf.net/svnroot/yap/trunk@277 b08c6af1-5177-4d33-ba66-4b1c6b8b522a
This commit is contained in:
pmoura
2002-01-07 22:59:00 +00:00
parent f95ddd47c5
commit 908cc7ae84
5 changed files with 138 additions and 97 deletions
Download Patch File Download Diff File Expand all files Collapse all files

125
Logtalk/LICENSE
View File

@@ -1,5 +1,4 @@
The "Artistic License"
The Artistic License
Preamble
@@ -10,32 +9,32 @@ giving the users of the package the right to use and distribute the
Package in a more-or-less customary fashion, plus the right to make
reasonable modifications.
Definitions
Definitions:
"Package" refers to the collection of files distributed by the
Copyright Holder, and derivatives of that collection of files
created through textual modification.
- "Package" refers to the collection of files distributed by the
Copyright Holder, and derivatives of that collection of files created
through textual modification.
"Standard Version" refers to such a Package if it has not been
modified, or has been modified in accordance with the wishes of
the Copyright Holder as specified below.
- "Standard Version" refers to such a Package if it has not been
modified, or has been modified in accordance with the wishes of the
Copyright Holder.
"Copyright Holder" is whoever is named in the copyright or
copyrights for the package.
- "Copyright Holder" is whoever is named in the copyright or copyrights
for the package.
"You" is you, if you're thinking about copying or distributing
this Package.
- "You" is you, if you're thinking about copying or distributing this
Package.
"Reasonable copying fee" is whatever you can justify on the basis
of media cost, duplication charges, time of people involved, and
so on. (You will not be required to justify it to the Copyright
Holder, but only to the computing community at large as a market
that must bear the fee.)
- "Reasonable copying fee" is whatever you can justify on the basis of
media cost, duplication charges, time of people involved, and so on.
(You will not be required to justify it to the Copyright Holder, but
only to the computing community at large as a market that must bear the
fee.)
"Freely Available" means that no fee is charged for the item
itself, though there may be fees involved in handling the item.
It also means that recipients of the item may redistribute it
under the same conditions they received it.
- "Freely Available" means that no fee is charged for the item itself,
though there may be fees involved in handling the item. It also means
that recipients of the item may redistribute it under the same
conditions they received it.
1. You may make and give away verbatim copies of the source form of the
Standard Version of this Package without restriction, provided that you
@@ -51,38 +50,39 @@ provided that you insert a prominent notice in each changed file stating
how and when you changed that file, and provided that you do at least
ONE of the following:
a.place your modifications in the Public Domain or otherwise make
them Freely Available, such as by posting said modifications to
Usenet or an equivalent medium, or placing the modifications on a
major archive site such as uunet.uu.net, or by allowing the
Copyright Holder to include your modifications in the Standard
Version of the Package.
a) place your modifications in the Public Domain or otherwise make them
Freely Available, such as by posting said modifications to Usenet or an
equivalent medium, or placing the modifications on a major archive site
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b.use the modified Package only within your corporation or
organization.
b) use the modified Package only within your corporation or
organization.
c.rename any non-standard executables so the names do not conflict
with standard executables, which must also be provided, and provide
a separate manual page for each non-standard executable that clearly
documents how it differs from the Standard Version.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a
separate manual page for each non-standard executable that clearly
documents how it differs from the Standard Version.
d.make other distribution arrangements with the Copyright Holder.
d) make other distribution arrangements with the Copyright Holder.
4. You may distribute the programs of this Package in object code or
executable form, provided that you do at least ONE of the following:
a.distribute a Standard Version of the executables and library
files, together with instructions (in the manual page or equivalent)
on where to get the Standard Version.
a) distribute a Standard Version of the executables and library files,
together with instructions (in the manual page or equivalent) on where
to get the Standard Version.
b.accompany the distribution with the machine-readable source of
the Package with your modifications.
b) accompany the distribution with the machine-readable source of the
Package with your modifications.
c.give non-standard executables non-standard names, and clearly
document the differences in manual pages (or equivalent), together
with instructions on where to get the Standard Version.
c) accompany any non-standard executables with their corresponding
Standard Version executables, giving the non-standard executables
non-standard names, and clearly documenting the differences in manual
pages (or equivalent), together with instructions on where to get the
Standard Version.
d.make other distribution arrangements with the Copyright Holder.
d) make other distribution arrangements with the Copyright Holder.
5. You may charge a reasonable copying fee for any distribution of this
Package. You may charge any fee you choose for support of this Package.
@@ -90,44 +90,21 @@ You may not charge a fee for this Package itself. However, you may
distribute this Package in aggregate with other (possibly commercial)
programs as part of a larger (possibly commercial) software distribution
provided that you do not advertise this Package as a product of your
own. You may embed this Package's interpreter within an executable of
yours (by linking); this shall be construed as a mere form of
aggregation, provided that the complete Standard Version of the
interpreter is so embedded.
own.
6. The scripts and library files supplied as input to or produced as
output from the programs of this Package do not automatically fall under
the copyright of this Package, but belong to whomever generated them,
and may be sold commercially, and may be aggregated with this Package.
If such scripts or library files are aggregated with this Package via
the so-called "undump" or "unexec" methods of producing a binary
executable image, then distribution of such an image shall neither be
construed as a distribution of this Package nor shall it fall under the
restrictions of Paragraphs 3 and 4, provided that you do not represent
such an executable image as a Standard Version of this Package.
7. C subroutines (or comparably compiled subroutines in other languages)
supplied by you and linked into this Package in order to emulate
subroutines and variables of the language defined by this Package shall
not be considered part of this Package, but are the equivalent of input
as in Paragraph 6, provided these subroutines do not change the language
in any way that would cause it to fail the regression tests for the
language.
7. C or perl subroutines supplied by you and linked into this Package
shall not be considered part of this Package.
8. Aggregation of this Package with a commercial distribution is always
permitted provided that the use of this Package is embedded; that is,
when no overt attempt is made to make this Package's interfaces visible
to the end user of the commercial distribution. Such use shall not be
construed as a distribution of this Package.
8. The name of the Copyright Holder may not be used to endorse or
promote products derived from this software without specific prior
written permission.
9.The name of the Copyright Holder may not be used to endorse or promote
products derived from this software without specific prior written
permission.
10.THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED
9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.

13
Logtalk/QUICK_START
View File

@@ -1,8 +1,8 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.8.4
Release 2.9.2
Copyright (c) 1998-2001 Paulo Moura. All Rights Reserved.
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================
@@ -42,11 +42,12 @@ lgt_load_prolog_code/1 in the configuration file.
Now you can try some of the included examples:
1. Open the examples sub-directory. There you find several sub-directories
with ready to run examples. Select and open one of them.
with ready to run examples and a NOTES file containing a brief description
of each example. Select and open one of the examples sub-directory.
3. Read the example NOTES file. Some examples are dependent on other
examples or on library objects. You may need to load additional files before
running the chosen example.
3. Read the example NOTES file. Some examples are dependent on other examples
or on library objects. You may need to load additional files before running
the chosen example.
4. Change the working directory of your Prolog compiler to the example
directory. If you don't know what predicate to use, check the configs/NOTES

23
Logtalk/README
View File

@@ -1,8 +1,8 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.8.4
Release 2.9.2
Copyright (c) 1998-2001 Paulo Moura. All Rights Reserved.
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================
@@ -32,7 +32,7 @@ stated.
The latest release of the Logtalk package is always available at the
URL:
http://www.ci.uc.pt/logtalk/logtalk.html
http://www.ci.uc.pt/logtalk/logtalk.html
At this address you can also find useful documentation and information
about Logtalk.
@@ -43,12 +43,12 @@ about Logtalk.
To register as a Logtalk user either use the registration form found at
the Logtalk web site or send an email message to:
pmoura@noe.ubi.pt
pmoura@noe.ubi.pt
with the following information:
email address, full name, organization, organization type
(education, commercial, government,...) prolog compilers used (optional),
(education, commercial, government,...), prolog compilers used (optional),
platforms (mac, pc, unix,...) (optional)
@@ -63,16 +63,15 @@ available at the URL http://www.ci.uc.pt/logtalk/news.html
There is also a mailing list, logtalk, used to announce new releases and
bug fixes and for discussion between Logtalk users, that you can subscribe.
For instructions on how to subscribe send an email message to:
For instructions on how to subscribe open the web page:
majordomo@ci.uc.pt
http://sagitta.ci.uc.pt/mailman/listinfo.cgi/logtalk
or send an email message to:
with the words:
logtalk-request@list-serv.ci.uc.pt
help
end
in the body of the message (not in the subject).
with just the word "help" as subject or in the body.
5. INSTALLATION

64
Logtalk/RELEASE_NOTES
View File

@@ -1,8 +1,8 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.8.4
Release 2.9.2
Copyright (c) 1998-2001 Paulo Moura. All Rights Reserved.
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================
@@ -10,6 +10,66 @@ RELEASE NOTES
=============
2.9.2 - January 4, 2002
The Logtalk compiler can now print a warning when compiling source files
that use non-ISO defined built-in predicates using a new portability/1
compiler option. Updated the relevant sections of the user manual and the
errors example.
Corrected a compiler bug where the entity relation tables only recorded
the last entry per entity relation type.
Updated config file for CIAO 1.7#162.
2.9.1 - December 5, 2001
Logtalk compiler now prints a warning when redefining or replacing an
existing entity.
Corrected a compiler bug in the error checking code for the info/1
and info/2 directives.
Changed the order of object loading in the "mi" example to avoid
suporious warning messages.
Added a new problem ("bridge") to the "searching" example. Improved
"performance" monitor to give correct reports on alternative solutions.
Corrected a bug in the "water jug" state space example.
2.9.0 - October 22, 2001
Added config files for CIAO Prolog 1.7p115 and B-Prolog 6.0.
Compiling and loading an entity that contains references to unknown
entities (by default) prints a warning. Updated user and reference
manuals.
Rewrited all the compiler warning/error code and output messages.
Changed compiled code functors postfixes from "_sdcl" and "_sdef" to
"_idcl" and "_idef" (implies recompilation of all objects, protocols,
and categories).
Changed all occurrences and references to the term "entity_scope" to
"scope".
Removed some redundant productions from the Logtalk grammar.
Updated documentation on the xml directory. Renamed some of the .xsl
files. Added sample scripts to batch convert .xml files to .html files.
Added a new loader utility file, all.loader, to load all library files
loaded by the other loader files.
Started work on documenting the Logtalk pre-processor/compiler source
file.
New "errors" example. Updated the "inheritance" example.
2.8.4 - March 9, 2001
Updated config files for BinProlog 8.0, K-Prolog 5.01, XSB 2.3, and

10
Logtalk/UPGRADING
View File

@@ -1,8 +1,8 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.8.4
Release 2.9.2
Copyright (c) 1998-2001 Paulo Moura. All Rights Reserved.
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================
@@ -33,4 +33,8 @@ Most examples have been rewritten to take advantage of the library.
Logtalk version 2.8.0 introduces a small change on the logtalk_compile/1-2
and logtalk_load/1-2 predicates that may imply updating your loader utility
files: the first argument is now always a list of entities even if we want
to compile or laod a single entity.
to compile or load a single entity.
Logtalk version 2.9.0 changes compiled code functors postfixes from "_sdcl"
and "_sdef" to "_idcl" and "_idef", impliying recompilation of all objects,
protocols, and categories.