Logtalk 2.12.0 files.

git-svn-id: https://yap.svn.sf.net/svnroot/yap/trunk@494 b08c6af1-5177-4d33-ba66-4b1c6b8b522a
This commit is contained in:
pmoura 2002-05-28 11:29:37 +00:00
parent 2b684e4636
commit a21cefd6ca
90 changed files with 188 additions and 143 deletions

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================
@ -60,3 +60,16 @@ and load all the example files. Note that the loader file is a Prolog file.
queries in the file to your Prolog top-level.
7. Enjoy!
Ready to start writing your own programs?
1. Take a look at the wenv sub-directory. There you will find syntax
configuration files for popular text editors that enable syntax coloring
when editing Logtalk source files.
2. Create a sub-directory with a suitable name to hold all the files of your
program.
3. Copy to this sub-directory a *.loader file form one of the examples and
modify it to load your own object files.

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
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.logtalk.org/
At this address you can also find useful documentation and information
about Logtalk.
@ -43,7 +43,7 @@ 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
registration@logtalk.org
with the following information:
@ -55,11 +55,11 @@ platforms (mac, pc, unix,...) (optional)
4. SUPPORT
Logtalk support is available for registered users via email to
pmoura@noe.ubi.pt.
support@logtalk.org.
At the URL http://www.ci.uc.pt/logtalk/bugs.html you can find a list of
At the URL http://www.logtalk.org/bugs.html you can find a list of
known problems and download bug fixes. The latest news about Logtalk are
available at the URL http://www.ci.uc.pt/logtalk/news.html
available at the URL http://www.logtalk.org/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.
@ -119,3 +119,4 @@ support address given above.
Happy Logtalking!
Paulo Moura
pmoura@logtalk.org

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================
@ -10,10 +10,28 @@ RELEASE NOTES
=============
2.12.0 - May ??, 2002
2.12.0 - May 25, 2002
New read-only Logtalk flag "version". Corrected exception term generated
when trying to modify a read-only flag using the set_logtalk_flag/2
built-in predicate.
Updated config file for OpenProlog 1.1b5.
New config file for ECLiPSe 5.4.
Renamed config files for CIAO 1.7 (beta of 1.8) to "ciao_aux18.config"
and "ciao18.config".
Updated config file for Amzi! Prolog 6.2.2.
New example of using some of the built-in database handling methods
(dynpred).
Syntax configuration files for jEdit 4.0, VIM 6.1, NEdit 5.2, and
TextPad 4.5 text editors providing syntax highlighting for editing
Logtalk source files.
2.11.0 - April 22, 2002

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================
@ -36,6 +36,9 @@ bricks
classvars
example of implementation of class variables (as found in Smalltalk)
dynpred
example of using some of the built-in database handling methods
errors
example showing the Logtalk compiler warning and error reporting

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,7 +1,7 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -5,8 +5,8 @@
:- info([
version is 1.0,
authors is 'Paulo Moura',
date is 2000/7/24,
comment is 'Operating system protocol.']).
date is 2002/5/10,
comment is 'Operating system file system protocol.']).
:- public(make_directory/1).
@ -63,22 +63,31 @@
argnames is ['File']]).
:- public(file_property/2).
:- mode(file_property(+atom, ?nonvar), zero_or_more).
:- info(file_property/2, [
comment is 'Access to file properties. Fails if the file does not exist or is not user readable.',
argnames is ['File', 'Property']]).
:- public(delete_file/1).
:- mode(delete_file(?atom), zero_or_one).
:- mode(delete_file(+atom), zero_or_one).
:- info(delete_file/1, [
comment is 'Deletes a file.',
argnames is ['File']]).
:- public(rename_file/1).
:- public(rename_file/2).
:- mode(rename_file(?atom), zero_or_one).
:- mode(rename_file(+atom, +atom), zero_or_one).
:- info(rename_file/1, [
comment is 'Renames a file.',
argnames is ['File']]).
:- info(rename_file/2, [
comment is 'Renames a file. Fails if the file does not exist or cannot be renamed.',
argnames is ['Old', 'New']]).
:- end_protocol.

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -4,24 +4,22 @@
<html>
<head>
<title>Logtalk 2.11.0 Documentation</title>
<title>Logtalk 2.12.0 Documentation</title>
<link rel=stylesheet href="styles.css" type="text/css">
</head>
<body>
<hr />
<h1 class="center">Logtalk 2.11.0</h1>
<h1 class="center">Logtalk 2.12.0</h1>
<h3 class="center">Documentation</h3>
<p class="center">
<strong><a href="http://www.ci.uc.pt/logtalk/pmoura.html">Paulo Moura</a></strong><br />
(<a href="mailto:pmoura@noe.ubi.pt">pmoura@noe.ubi.pt</a>)
<strong><a href="http://www.logtalk.org/pmoura.html">Paulo Moura</a></strong><br />
(<a href="mailto:pmoura@logtalk.org">pmoura@logtalk.org</a>)
</p>
<p class="center">
Department of Informatics<br />
<A HREF="http://www.ubi.pt">University of Beira Interior</A><br />
Portugal
<A HREF="http://www.logtalk.org">Logtalk.org</A>
</p>
<hr />
@ -44,7 +42,7 @@ Portugal
<hr />
<p class="center">
Last updated on: April 22, 2002
Last updated on: May 19, 2002
</p>
<p class="center">
<a href="http://validator.w3.org/check/referer"><img src="vh401.gif" alt="Valid HTML 4.01!" width="88" height="31"></a>

View File

@ -21,7 +21,7 @@
logtalk_version(Major, Minor, Patch)
</pre>
<p>
Returns the Logtalk pre-processor and runtime version.
Returns the Logtalk preprocessor and runtime version.
</p>
</blockquote>
@ -59,7 +59,7 @@ logtalk_version(?integer, ?integer, ?integer)
<strong><a href="forall2.html">Previous</a> | <a href="retractall1.html">Next</a> | <a href="../index.html">Table of Contents</a> | <a href="../../bibliography.html">Bibliography</a> | <a href="../../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: October 21, 2001
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -48,7 +48,7 @@ set_logtalk_flag(+atom, +atom)
<dt>Value is not a valid value for flag Flag:</dt>
<dd><code>domain_error(valid_flag_value, Value)</code></dd>
<dt>Flag is a read-only flag:</dt>
<dd><code>domain_error(read_only_flag, Flag)</code></dd>
<dd><code>permission_error(modify, read_only_flag, Flag)</code></dd>
</dl>
</blockquote>
@ -65,7 +65,7 @@ set_logtalk_flag(+atom, +atom)
<strong><a href="current_logtalk_flag2.html">Previous</a> | <a href="forall2.html">Next</a> | <a href="../index.html">Table of Contents</a> | <a href="../../bibliography.html">Bibliography</a> | <a href="../../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: February 9, 2002
Last updated on: May 14, 2002
</p>
<hr />

View File

@ -21,7 +21,7 @@
{Goal}
</pre>
<p>
Calls external Prolog code. Can be used to bypass the Logtalk pre-processor/compiler.
Calls external Prolog code. Can be used to bypass the Logtalk preprocessor/compiler.
</p>
</blockquote>
@ -55,7 +55,7 @@ N1/D1 &lt; N2/D2 :-
<strong><a href="to_super1.html">Previous</a> | <a href="../errors.html">Next</a> | <a href="../index.html">Table of Contents</a> | <a href="../../bibliography.html">Bibliography</a> | <a href="../../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: October 21, 2001
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -188,7 +188,7 @@
<strong><a href="../userman/index.html">User manual</a> | <a href="../tutorial/index.html">Tutorial</a> | <a href="../bibliography.html">Bibliography</a> | <a href="../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: April 21, 2002
Last updated on: May 14, 2002
</p>
<hr />

View File

@ -21,7 +21,7 @@ Categories provide a way to encapsulate a set of related predicate definitions t
<h2><a class="back" title="Return to index" name="defining" href="index.html#categories_defining">Defining a new category</a></h2>
<p>
We can define a new category in the same way we write Prolog code: by using a text editor. Each category (object or protocol) we define should be contained in its own text file. It is recommended that this text file be named after the category. By default, all Logtalk source files use the extension <code>.lgt</code> but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk pre-processor) have, by default, a <code>.pl</code> extension. Again, this can be set to match the needs of a particular Prolog compiler in the corresponding configuration file. For instance, we may define a category named <code>documenting</code> and save it in a <code>documenting.lgt</code> source file that will be compiled to a <code>documenting.pl</code> Prolog file.
We can define a new category in the same way we write Prolog code: by using a text editor. Each category (object or protocol) we define should be contained in its own text file. It is recommended that this text file be named after the category. By default, all Logtalk source files use the extension <code>.lgt</code> but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk preprocessor) have, by default, a <code>.pl</code> extension. Again, this can be set to match the needs of a particular Prolog compiler in the corresponding configuration file. For instance, we may define a category named <code>documenting</code> and save it in a <code>documenting.lgt</code> source file that will be compiled to a <code>documenting.pl</code> Prolog file.
</p>
<p>
Category names must be atoms. Objects, categories, and protocols share the same name space: we can not have a category with the same name as an object or a protocol.
@ -277,7 +277,7 @@ Omitting the scope keyword is equivalent to writing:
<strong><a href="protocols.html">Previous</a> | <a href="predicates.html">Next</a> | <a href="index.html">Table of Contents</a> | <a href="../bibliography.html">Bibliography</a> | <a href="../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: April 2, 2002
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -53,7 +53,7 @@ Because most Prolog implementers are slowly moving toward more ISO compliant com
<h2><a class="back" title="Return to index" name="files" href="index.html#configuration_files">Configuration files</a></h2>
<p>
Configuration files provide the glue code between the Logtalk pre-processor/runtime and a Prolog compiler. Each configuration file contains two sets of predicates: ISO Prolog standard predicates and directives not built-in in the target Prolog compiler and Logtalk-specific predicates.
Configuration files provide the glue code between the Logtalk preprocessor/runtime and a Prolog compiler. Each configuration file contains two sets of predicates: ISO Prolog standard predicates and directives not built-in in the target Prolog compiler and Logtalk-specific predicates.
</p>
<p>
Logtalk already includes ready to use configuration files for most Prolog compilers. However, you may need to write your own configuration file if one is not available for your Prolog compiler. In most cases, you can borrow code from some of the predefined configuration files. If you send me your configuration file, with a reference to the target Prolog compiler, maybe I can include it in the next release of Logtalk.
@ -70,7 +70,7 @@ If you are unsure that your Prolog compiler provides all the ISO predicates need
<strong><a href="documenting.html">Previous</a> | <a href="installing.html">Next</a> | <a href="index.html">Table of Contents</a> | <a href="../bibliography.html">Bibliography</a> | <a href="../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: February 10, 2001
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -45,28 +45,28 @@ For example:
<h2><a class="back" title="Return to index" name="compiler" href="index.html#errors_compiler">Compiler warnings and errors</a></h2>
<p>
The Logtalk pre-processor/compiler uses the <code>read_term/3</code> ISO Prolog defined built-in predicate to read and process a Logtalk source file. One consequence of this is that invalid Prolog terms or syntax errors may abort the compilation process with limited information given to the user (due to the inherent limitations of the <code>read_term/3</code> predicate).
The Logtalk preprocessor/compiler uses the <code>read_term/3</code> ISO Prolog defined built-in predicate to read and process a Logtalk source file. One consequence of this is that invalid Prolog terms or syntax errors may abort the compilation process with limited information given to the user (due to the inherent limitations of the <code>read_term/3</code> predicate).
</p>
<p>
If all the (Prolog) terms in a source file are valid, then there is a set of errors or potential errors, described below, that the pre-processor will try to detect and report, depending on the used compiler options (see the <A HREF="installing.html#options">Installing and running Logtalk</A> section of this manual for details).
If all the (Prolog) terms in a source file are valid, then there is a set of errors or potential errors, described below, that the preprocessor will try to detect and report, depending on the used compiler options (see the <A HREF="installing.html#options">Installing and running Logtalk</A> section of this manual for details).
</p>
<h3><a class="back" title="Return to index" name="wunknown" href="index.html#errors_wunknown">Unknown entities</a></h3>
<p>
The Logtalk pre-processor/compiler will warn us of any referenced entity that is not currently loaded. The warning may reveal a misspell entity name or just an entity that it will be loaded next.
The Logtalk preprocessor/compiler will warn us of any referenced entity that is not currently loaded. The warning may reveal a misspell entity name or just an entity that it will be loaded next.
</p>
<h3><a class="back" title="Return to index" name="wsingletons" href="index.html#errors_wsingletons">Singleton variables</a></h3>
<p>
Singleton variables in a clause are often misspell variables and, as such, one of the most common errors when programming in Prolog. If your Prolog compiler complies with the Prolog ISO standard or at least supports the ISO predicate <code>read_term/3</code> called with the option <code>singletons(S)</code>, then the Logtalk pre-processor/compiler will warn us of any singleton it finds while compiling a Logtalk entity.
Singleton variables in a clause are often misspell variables and, as such, one of the most common errors when programming in Prolog. If your Prolog compiler complies with the Prolog ISO standard or at least supports the ISO predicate <code>read_term/3</code> called with the option <code>singletons(S)</code>, then the Logtalk preprocessor/compiler will warn us of any singleton it finds while compiling a Logtalk entity.
</p>
<h3><a class="back" title="Return to index" name="wprolog" href="index.html#errors_wprolog">Redefinition of Prolog built-in predicates</a></h3>
<p>
The Logtalk pre-processor/compiler will warn us of any redefinition of a Prolog built-in predicate inside an object or category. Sometimes the redefinition is intended. In other cases, the user may not be aware that the subjacent Prolog compiler may already provide the predicate as a built-in or we may want to ensure code portability among several Prolog compilers with different sets of built-in predicates.
The Logtalk preprocessor/compiler will warn us of any redefinition of a Prolog built-in predicate inside an object or category. Sometimes the redefinition is intended. In other cases, the user may not be aware that the subjacent Prolog compiler may already provide the predicate as a built-in or we may want to ensure code portability among several Prolog compilers with different sets of built-in predicates.
</p>
<h3><a class="back" title="Return to index" name="wpredicates" href="index.html#errors_wpredicates">Redefinition of Logtalk built-in predicates</a></h3>
@ -96,7 +96,7 @@ A warning will be reported if a predicate clause contains a call to a non-ISO de
<h3><a class="back" title="Return to index" name="wothers" href="index.html#errors_wothers">Other warnings and errors</a></h3>
<p>
The Logtalk pre-processor/compiler will throw an error if it finds a predicate clause or a directive that cannot be parsed. The default behaviour is to report the error and abort the compilation of the offending entity.
The Logtalk preprocessor/compiler will throw an error if it finds a predicate clause or a directive that cannot be parsed. The default behaviour is to report the error and abort the compilation of the offending entity.
</p>
<hr />
@ -129,7 +129,7 @@ The message sending mechanisms always check if the receiver of a message is a de
<strong><a href="events.html">Previous</a> | <a href="documenting.html">Next</a> | <a href="index.html">Table of Contents</a> | <a href="../bibliography.html">Bibliography</a> | <a href="../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: December 30, 2001
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -91,7 +91,7 @@ Object names can be compound terms (instead of atoms), providing a way to parame
<blockquote>
<p>
Logtalk has a smooth learning curve, by adopting standard Prolog syntax (using a pre-processor) and by enabling an incremental learning and use of most of its features.
Logtalk has a smooth learning curve, by adopting standard Prolog syntax (using a preprocessor) and by enabling an incremental learning and use of most of its features.
</p>
</blockquote>
@ -108,7 +108,7 @@ The Logtalk system has been designed to be compatible with most Prolog compilers
<strong><a href="index.html">Previous</a> | <a href="messages.html">Next</a> | <a href="index.html">Table of Contents</a> | <a href="../bibliography.html">Bibliography</a> | <a href="../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: July 4, 2000
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -218,7 +218,7 @@
<strong><a title="Consult reference manual" href="../refman/index.html">Reference manual</a> | <a href="../tutorial/index.html">Tutorial</a> | <a href="../bibliography.html">Bibliography</a> | <a href="../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: April 22, 2002
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -112,7 +112,7 @@ Since most Prolog compilers are moving closer to the ISO Prolog standard <a href
<h3><a class="back" title="Return to index" name="compiler" href="index.html#installing_compiler">Logtalk compiler and runtime</a></h3>
<p>
The <code>compiler</code> sub-directory contains the Prolog source file(s) that implement the Logtalk pre-processor/compiler and the Logtalk runtime. The compiler and the runtime may be split in two (or more) separate files or combined in a single file, depending on the Logtalk release that you are installing.
The <code>compiler</code> sub-directory contains the Prolog source file(s) that implement the Logtalk preprocessor/compiler and the Logtalk runtime. The compiler and the runtime may be split in two (or more) separate files or combined in a single file, depending on the Logtalk release that you are installing.
</p>
<h3><a class="back" title="Return to index" name="library" href="index.html#installing_library">Library</a></h3>
@ -130,7 +130,7 @@ Logtalk 2.x contains new implementations of some of the examples provided with p
<h3><a class="back" title="Return to index" name="entities" href="index.html#installing_entities">Logtalk source files</a></h3>
<p>
Each Logtalk entity (object, category or protocol) is contained in a text file named after the entity. The extension <code>.lgt</code> is normally used. The Logtalk pre-processor compiles these files to plain Prolog, replacing the <code>.lgt</code> extension with <code>.pl</code> (the default Prolog extension). If your Prolog compiler expects the Prolog source filenames to end with a specific, different extension, you can set it in the corresponding configuration file.
Each Logtalk entity (object, category or protocol) is contained in a text file named after the entity. The extension <code>.lgt</code> is normally used. The Logtalk preprocessor compiles these files to plain Prolog, replacing the <code>.lgt</code> extension with <code>.pl</code> (the default Prolog extension). If your Prolog compiler expects the Prolog source filenames to end with a specific, different extension, you can set it in the corresponding configuration file.
</p>
<h3><a class="back" title="Return to index" name="loaders" href="index.html#installing_loaders">Loader utility files</a></h3>
@ -167,10 +167,10 @@ To start a Logtalk session just:
<ol>
<li>Start Prolog.</li>
<li>Load the appropriate configuration file for your compiler. Configuration files for most common Prolog compilers can be found in the <code>configs</code> subdirectory.</li>
<li>Load the Logtalk compiler/pre-processor and runtime files contained in the <code>compiler</code> subdirectory.</li>
<li>Load the Logtalk compiler/preprocessor and runtime files contained in the <code>compiler</code> subdirectory.</li>
</ol>
<p>
Note that the both configuration files and compiler/pre-processor files are Prolog source files. The predicate called to load (and compile) them depends on your Prolog compiler. In case of doubt, consult your Prolog compiler reference manual or take a look at the definition of the predicate <code>lgt_load_prolog_code/1</code> in the corresponding configuration file.
Note that the both configuration files and compiler/preprocessor files are Prolog source files. The predicate called to load (and compile) them depends on your Prolog compiler. In case of doubt, consult your Prolog compiler reference manual or take a look at the definition of the predicate <code>lgt_load_prolog_code/1</code> in the corresponding configuration file.
</p>
<h3><a class="back" title="Return to index" name="compiling" href="index.html#installing_compiling">Compiling and loading your programs</a></h3>
@ -183,7 +183,7 @@ Your programs will be made of source files containing your objects, protocols an
| ?- logtalk_compile([source_file1, source_file2, ...]).
</pre>
<p>
This predicate runs the pre-processor on each argument file and, if no fatal errors are found, outputs Prolog source files that can then be consulted or compiled in the usual way by your Prolog compiler. Note that the predicate argument must be a list of entity names, not file names (or paths).
This predicate runs the preprocessor on each argument file and, if no fatal errors are found, outputs Prolog source files that can then be consulted or compiled in the usual way by your Prolog compiler. Note that the predicate argument must be a list of entity names, not file names (or paths).
</p>
<p>
To compile to disk and also load into memory the source files we can use the Logtalk built-in predicate <a title="Consult reference manual" href="../refman/builtins/logtalk_load1.html"><code>logtalk_load/1</code></a>:
@ -294,7 +294,7 @@ Smart compilation of source files is usually off by default. You can turn it on
| ?- set_logtalk_flag(smart_compilation, on).
</pre>
<p>
Some caveats that you should be aware. First, some warnings that might be produced when compiling a source file will not show up if the corresponding object file is up-to-date because the source file is not being (re)compiled. Second, if you are using several Prolog compilers with Logtalk, be sure to perform the first compilation of your source files with smart compilation turned off: the intermediate Prolog files generated by the Logtalk pre-processor may be not compatible across Prolog compilers or even for the same Prolog compiler across operating systems (due to different end-of-line characters).
Some caveats that you should be aware. First, some warnings that might be produced when compiling a source file will not show up if the corresponding object file is up-to-date because the source file is not being (re)compiled. Second, if you are using several Prolog compilers with Logtalk, be sure to perform the first compilation of your source files with smart compilation turned off: the intermediate Prolog files generated by the Logtalk preprocessor may be not compatible across Prolog compilers or even for the same Prolog compiler across operating systems (due to different end-of-line characters).
</p>
<hr />
@ -315,7 +315,7 @@ To supress printing of compiling and loading messages (including compiling warni
<strong><a href="configuration.html">Previous</a> | <a href="programming.html">Next</a> | <a href="index.html">Table of Contents</a> | <a href="../bibliography.html">Bibliography</a> | <a href="../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: April 22, 2002
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -29,7 +29,7 @@ Logtalk uses the following three operators for message sending:
:- op(600, fx, ^^).
</pre>
<p>
It is assumed that these operators remain active (once the Logtalk pre-processor and runtime files are loaded) until the end of the Prolog session (this is the usual behaviour of most Prolog compilers). Note that these operator definitions are compatible with the pre-defined operators in the Prolog ISO standard.
It is assumed that these operators remain active (once the Logtalk preprocessor and runtime files are loaded) until the end of the Prolog session (this is the usual behaviour of most Prolog compilers). Note that these operator definitions are compatible with the pre-defined operators in the Prolog ISO standard.
</p>
<hr />
@ -179,7 +179,7 @@ See the session on Event-driven programming for more details.
<strong><a href="features.html">Previous</a> | <a href="objects.html">Next</a> | <a href="index.html">Table of Contents</a> | <a href="../bibliography.html">Bibliography</a> | <a href="../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: July 4, 2000
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -31,7 +31,7 @@ Objects, prototypes, parents, classes, subclasses, superclasses, metaclasses, in
<h2><a class="back" title="Return to index" name="defining" href="index.html#objects_defining">Defining a new object</a></h2>
<p>
We can define a new object in the same way we write Prolog code: by using a text editor. Each object (category or protocol) we define should be contained in its own text file. It is recommended that this text file be named after the object. By default, all Logtalk source files use the extension <code>.lgt</code> but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk pre-processor) have, by default, a <code>.pl</code> extension. Again, this can be set to match the needs of a particular Prolog compiler in the corresponding configuration file. For instance, we may define an object named <code>vehicle</code> and save it in a <code>vehicle.lgt</code> source file that will be compiled to a <code>vehicle.pl</code> Prolog file.
We can define a new object in the same way we write Prolog code: by using a text editor. Each object (category or protocol) we define should be contained in its own text file. It is recommended that this text file be named after the object. By default, all Logtalk source files use the extension <code>.lgt</code> but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk preprocessor) have, by default, a <code>.pl</code> extension. Again, this can be set to match the needs of a particular Prolog compiler in the corresponding configuration file. For instance, we may define an object named <code>vehicle</code> and save it in a <code>vehicle.lgt</code> source file that will be compiled to a <code>vehicle.pl</code> Prolog file.
</p>
<p>
Object names can be atoms or compound terms (if we are defining parametric objects, see below). Objects, categories and protocols share the same name space: we can not have an object with the same name as a protocol or a category.
@ -446,7 +446,7 @@ Logtalk defines a pseudo-object named <code>user</code> that contains all user p
<strong><a href="messages.html">Previous</a> | <a href="protocols.html">Next</a> | <a href="index.html">Table of Contents</a> | <a href="../bibliography.html">Bibliography</a> | <a href="../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: August 5, 2000
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -67,7 +67,7 @@ The first argument describes a valid calling mode. The minimum information will
</dl>
</blockquote>
<p>
These four mode atoms are also declared as prefix operators by the Logtalk pre-processor. This makes it possible to include type information for each argument like in the example above. Some of the possible type values are: <code>event</code>, <code>object</code>, <code>category</code>, <code>protocol</code>, <code>callable</code>, <code>term</code>, <code>nonvar</code>, <code>var</code>, <code>atomic</code>, <code>atom</code>, <code>number</code>, <code>integer</code>, <code>float</code>, <code>compound</code>, and <code>list</code>. The first four are Logtalk specific. The remaining are common Prolog types. We can also use our own types that can be either atoms or compound terms.
These four mode atoms are also declared as prefix operators by the Logtalk preprocessor. This makes it possible to include type information for each argument like in the example above. Some of the possible type values are: <code>event</code>, <code>object</code>, <code>category</code>, <code>protocol</code>, <code>callable</code>, <code>term</code>, <code>nonvar</code>, <code>var</code>, <code>atomic</code>, <code>atom</code>, <code>number</code>, <code>integer</code>, <code>float</code>, <code>compound</code>, and <code>list</code>. The first four are Logtalk specific. The remaining are common Prolog types. We can also use our own types that can be either atoms or compound terms.
</p>
<p>
The second argument documents the number of proofs (or solutions) for the specified mode. The possible values are:
@ -102,7 +102,7 @@ Note that most predicates have more than one valid mode implying several mode di
:- mode(atom_concat(+atom, +atom, -atom), zero_or_one).
</pre>
<p>
Some old Prolog compilers supported some sort of mode directives to improve performance. To the best of my knowledge, there is no modern Prolog compiler supporting these kind of directive. The current version of the Logtalk pre-processor just parses and than discards this directive. Nevertheless, the use of mode directives is a good starting point to the documentation of your predicates.
Some old Prolog compilers supported some sort of mode directives to improve performance. To the best of my knowledge, there is no modern Prolog compiler supporting these kind of directive. The current version of the Logtalk preprocessor just parses and than discards this directive. Nevertheless, the use of mode directives is a good starting point to the documentation of your predicates.
</p>
<h3><a class="back" title="Return to index" name="meta" href="index.html#predicates_meta">Metapredicate directive</a></h3>
@ -374,7 +374,7 @@ will only return user predicates that are declared public.
<strong><a href="categories.html">Previous</a> | <a href="inheritance.html">Next</a> | <a href="index.html">Table of Contents</a> | <a href="../bibliography.html">Bibliography</a> | <a href="../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: July 4, 2000
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -57,10 +57,10 @@ One of the advantages of a system like Logtalk is that it enable us to use the c
<h3><a class="back" title="Return to index" name="source_files" href="index.html#programming_source_files">Source files</a></h3>
<p>
A Logtalk source file must contain only one entity, either an object, a category, or a protocol. It is recommended that each source file be named after the entity identifier. For parametric objects, the identifier arity can be appended to the identifier functor. By default, all Logtalk source files use the extension <code>.lgt</code> but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk pre-processor) have, by default, a <code>.pl</code> extension. Again, this can be set to match the needs of a particular Prolog compiler in the corresponding configuration file. For example, we may define an object named <code>vehicle</code> and save it in a <code>vehicle.lgt</code> source file that will be compiled to a <code>vehicle.pl</code> Prolog file. If we have a <code>sort(_)</code> parametric object we can save it on a <code>sort1.lgt</code> source file that will be compiled to a <code>sort1.pl</code> Prolog file. This name scheme helps avoid file name conflicts (remember that all Logtalk entities share the same name space).
A Logtalk source file must contain only one entity, either an object, a category, or a protocol. It is recommended that each source file be named after the entity identifier. For parametric objects, the identifier arity can be appended to the identifier functor. By default, all Logtalk source files use the extension <code>.lgt</code> but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk preprocessor) have, by default, a <code>.pl</code> extension. Again, this can be set to match the needs of a particular Prolog compiler in the corresponding configuration file. For example, we may define an object named <code>vehicle</code> and save it in a <code>vehicle.lgt</code> source file that will be compiled to a <code>vehicle.pl</code> Prolog file. If we have a <code>sort(_)</code> parametric object we can save it on a <code>sort1.lgt</code> source file that will be compiled to a <code>sort1.pl</code> Prolog file. This name scheme helps avoid file name conflicts (remember that all Logtalk entities share the same name space).
</p>
<p>
Any Logtalk source file can contain arbitrary directives and clauses before the opening entity directive. These directives and clauses will not be compiled by the Logtalk pre-processor and will be copied unchanged to the beginning of the corresponding Prolog output file. This feature is included to help the integration of Logtalk with other Prolog extensions like, for example, constraint programming extensions.
Any Logtalk source file can contain arbitrary directives and clauses before the opening entity directive. These directives and clauses will not be compiled by the Logtalk preprocessor and will be copied unchanged to the beginning of the corresponding Prolog output file. This feature is included to help the integration of Logtalk with other Prolog extensions like, for example, constraint programming extensions.
</p>
<h3><a class="back" title="Return to index" name="portability" href="index.html#programming_portability">Portable programs</a></h3>
@ -87,7 +87,7 @@ Since each Logtalk entity is independently compiled, if an object inherits a dyn
In general, Logtalk does not verify if a user predicate call/return arguments comply with the declared modes. On the other hand, Logtalk built-in predicates, built-in methods and message sending control structures are carefully checked for calling mode errors.
</p>
<p>
Logtalk error handling strongly depends on the ISO compliance of the chosen Prolog compiler. For instance, the error terms that are generated by some Logtalk built-in predicates assume that the Prolog built-ins behave as defined in the ISO standard regarding error conditions. In particular, if your Prolog compiler does not support a <code>read_term/3</code> built-in predicate compliant with the ISO Prolog Standard definition, then the current version of the Logtalk pre-processor will not be able to detect misspell variables in your source code.
Logtalk error handling strongly depends on the ISO compliance of the chosen Prolog compiler. For instance, the error terms that are generated by some Logtalk built-in predicates assume that the Prolog built-ins behave as defined in the ISO standard regarding error conditions. In particular, if your Prolog compiler does not support a <code>read_term/3</code> built-in predicate compliant with the ISO Prolog Standard definition, then the current version of the Logtalk preprocessor will not be able to detect misspell variables in your source code.
</p>
<hr />
@ -95,7 +95,7 @@ Logtalk error handling strongly depends on the ISO compliance of the chosen Prol
<strong><a href="installing.html">Previous</a> | <a href="index.html">Next</a> | <a href="index.html">Table of Contents</a> | <a href="../bibliography.html">Bibliography</a> | <a href="../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: December 30, 2001
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -21,7 +21,7 @@ Protocols enable the separation between interface and implementation: several ob
<h2><a class="back" title="Return to index" name="defining" href="index.html#protocols_defining">Defining a new protocol</a></h2>
<p>
We can define a new protocol in the same way we write Prolog code: by using a text editor. Each protocol (object or category) we define should be contained in its own text file. It is recommended that this text file be named after the protocol. By default, all Logtalk source files use the extension <code>.lgt</code> but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk pre-processor) have, by default, a <code>.pl</code> extension. Again, this can be set to match the needs of a particular Prolog compiler in the corresponding configuration file. For example, we may define a protocol named <code>listp</code> and save it in a <code>listp.lgt</code> source file that will be compiled to a <code>listp.pl</code> Prolog file.
We can define a new protocol in the same way we write Prolog code: by using a text editor. Each protocol (object or category) we define should be contained in its own text file. It is recommended that this text file be named after the protocol. By default, all Logtalk source files use the extension <code>.lgt</code> but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk preprocessor) have, by default, a <code>.pl</code> extension. Again, this can be set to match the needs of a particular Prolog compiler in the corresponding configuration file. For example, we may define a protocol named <code>listp</code> and save it in a <code>listp.lgt</code> source file that will be compiled to a <code>listp.pl</code> Prolog file.
</p>
<p>
Protocol names must be atoms. Objects, categories and protocols share the same name space: we can not have a protocol with the same name as an object or a category.
@ -252,7 +252,7 @@ The same rules applies to protocols implemented by categories.
<strong><a href="objects.html">Previous</a> | <a href="categories.html">Next</a> | <a href="index.html">Table of Contents</a> | <a href="../bibliography.html">Bibliography</a> | <a href="../glossary.html">Glossary</a></strong>
</p>
<p class="center">
Last updated on: April 30, 2001
Last updated on: May 6, 2002
</p>
<hr />

View File

@ -1,6 +1,6 @@
=================================================================
Logtalk - Object oriented extension to Prolog
Release 2.11.0
Release 2.12.0
Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
=================================================================

View File

@ -8,7 +8,7 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Logtalk - Object oriented extension to Prolog
% Release 2.11.0
% Release 2.12.0
%
% Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
%

View File

@ -14,7 +14,7 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Logtalk - Object oriented extension to Prolog
% Release 2.11.0
% Release 2.12.0
%
% Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
%

View File

@ -9,7 +9,7 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Logtalk - Object oriented extension to Prolog
% Release 2.11.0
% Release 2.12.0
%
% Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
%

View File

@ -9,7 +9,7 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Logtalk - Object oriented extension to Prolog
% Release 2.11.0
% Release 2.12.0
%
% Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
%

View File

@ -14,7 +14,7 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Logtalk - Object oriented extension to Prolog
% Release 2.11.0
% Release 2.12.0
%
% Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
%

View File

@ -3,7 +3,7 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Logtalk - Object oriented extension to Prolog
% Release 2.11.0
% Release 2.12.0
%
% Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
%

View File

@ -15,7 +15,7 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Logtalk - Object oriented extension to Prolog
% Release 2.11.0
% Release 2.12.0
%
% Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
%

View File

@ -12,7 +12,7 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Logtalk - Object oriented extension to Prolog
% Release 2.11.0
% Release 2.12.0
%
% Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
%

View File

@ -2,7 +2,7 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Logtalk - Object oriented extension to Prolog
% Release 2.11.0
% Release 2.12.0
%
% Copyright (c) 1998-2002 Paulo Moura. All Rights Reserved.
%
@ -1019,7 +1019,7 @@ logtalk_version(Major, Minor, Patch) :-
\+ integer(Patch),
throw(error(type_error(integer, Patch), logtalk_version(Major, Minor, Patch))).
logtalk_version(2, 11, 0).
logtalk_version(2, 12, 0).
@ -1046,12 +1046,12 @@ set_logtalk_flag(Flag, Value) :-
throw(error(domain_error(valid_flag, Flag), set_logtalk_flag(Flag, Value))).
set_logtalk_flag(Flag, Value) :-
\+ lgt_valid_flag(Flag, Value),
throw(error(domain_error(valid_flag_value, Value), set_logtalk_flag(Flag, Value))).
lgt_read_only_flag(Flag),
throw(error(permission_error(modify, read_only_flag, Flag), set_logtalk_flag(Flag, Value))).
set_logtalk_flag(Flag, Value) :-
lgt_read_only_flag(Flag),
throw(error(domain_error(read_only_flag, Flag), set_logtalk_flag(Flag, Value))).
\+ lgt_valid_flag(Flag, Value),
throw(error(domain_error(valid_flag_value, Value), set_logtalk_flag(Flag, Value))).
set_logtalk_flag(Flag, Value) :-
retractall(lgt_flag_(Flag, _)),
@ -1080,6 +1080,7 @@ current_logtalk_flag(Flag, Value) :-
\+ lgt_flag_(Flag, _),
lgt_default_flag(Flag, Value).
current_logtalk_flag(version, version(2, 12, 0)).
@ -5292,6 +5293,8 @@ lgt_valid_flag(plredef).
lgt_valid_flag(portability).
lgt_valid_flag(report).
lgt_valid_flag(smart_compilation).
lgt_valid_flag(startup_message).
lgt_valid_flag(version).
@ -5310,8 +5313,8 @@ lgt_valid_flag(Flag, Value) :-
%
% true if the argument is a read only Logtalk flag
lgt_read_only_flag(_) :-
fail.
lgt_read_only_flag(startup_message).
lgt_read_only_flag(version).

View File

@ -1,7 +1,7 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Logtalk - Object oriented extension to Prolog
% Release 2.11.0
% Release 2.12.0
%
% configuration file for YAP Prolog 4.3.x
%