- 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.
-Last updated on: April 21, 2002
+Last updated on: May 14, 2002
diff --git a/Logtalk/manuals/userman/categories.html b/Logtalk/manuals/userman/categories.html
index 57d7222a4..c16f425b9 100644
--- a/Logtalk/manuals/userman/categories.html
+++ b/Logtalk/manuals/userman/categories.html
@@ -21,7 +21,7 @@ Categories provide a way to encapsulate a set of related predicate definitions t
-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 .lgt but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk pre-processor) have, by default, a .pl 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 documenting and save it in a documenting.lgt source file that will be compiled to a documenting.pl 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 .lgt but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk preprocessor) have, by default, a .pl 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 documenting and save it in a documenting.lgt source file that will be compiled to a documenting.pl Prolog file.
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:
Previous | Next | Table of Contents | Bibliography | Glossary
-Last updated on: April 2, 2002
+Last updated on: May 6, 2002
diff --git a/Logtalk/manuals/userman/configuration.html b/Logtalk/manuals/userman/configuration.html
index f4246ab2f..2b2e1120b 100644
--- a/Logtalk/manuals/userman/configuration.html
+++ b/Logtalk/manuals/userman/configuration.html
@@ -53,7 +53,7 @@ Because most Prolog implementers are slowly moving toward more ISO compliant com
-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.
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
Previous | Next | Table of Contents | Bibliography | Glossary
-Last updated on: February 10, 2001
+Last updated on: May 6, 2002
diff --git a/Logtalk/manuals/userman/errors.html b/Logtalk/manuals/userman/errors.html
index 6b59c22aa..2d8a78546 100644
--- a/Logtalk/manuals/userman/errors.html
+++ b/Logtalk/manuals/userman/errors.html
@@ -45,28 +45,28 @@ For example:
-The Logtalk pre-processor/compiler uses the read_term/3 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 read_term/3 predicate).
+The Logtalk preprocessor/compiler uses the read_term/3 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 read_term/3 predicate).
-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 Installing and running Logtalk 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 Installing and running Logtalk section of this manual for details).
-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.
-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 read_term/3 called with the option singletons(S), 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 read_term/3 called with the option singletons(S), then the Logtalk preprocessor/compiler will warn us of any singleton it finds while compiling a Logtalk entity.
-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.
-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.
-Last updated on: December 30, 2001
+Last updated on: May 6, 2002
diff --git a/Logtalk/manuals/userman/features.html b/Logtalk/manuals/userman/features.html
index 483f23382..59f248216 100644
--- a/Logtalk/manuals/userman/features.html
+++ b/Logtalk/manuals/userman/features.html
@@ -91,7 +91,7 @@ Object names can be compound terms (instead of atoms), providing a way to parame
-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.
-Last updated on: April 22, 2002
+Last updated on: May 6, 2002
diff --git a/Logtalk/manuals/userman/installing.html b/Logtalk/manuals/userman/installing.html
index 5495788fb..c92f58ba9 100644
--- a/Logtalk/manuals/userman/installing.html
+++ b/Logtalk/manuals/userman/installing.html
@@ -112,7 +112,7 @@ Since most Prolog compilers are moving closer to the ISO Prolog standard Logtalk compiler and runtime
-The compiler 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 compiler 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.
-Each Logtalk entity (object, category or protocol) is contained in a text file named after the entity. The extension .lgt is normally used. The Logtalk pre-processor compiles these files to plain Prolog, replacing the .lgt extension with .pl (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 .lgt is normally used. The Logtalk preprocessor compiles these files to plain Prolog, replacing the .lgt extension with .pl (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.
@@ -167,10 +167,10 @@ To start a Logtalk session just:
Start Prolog.
Load the appropriate configuration file for your compiler. Configuration files for most common Prolog compilers can be found in the configs subdirectory.
-
Load the Logtalk compiler/pre-processor and runtime files contained in the compiler subdirectory.
+
Load the Logtalk compiler/preprocessor and runtime files contained in the compiler subdirectory.
-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 lgt_load_prolog_code/1 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 lgt_load_prolog_code/1 in the corresponding configuration file.
@@ -183,7 +183,7 @@ Your programs will be made of source files containing your objects, protocols an
| ?- logtalk_compile([source_file1, source_file2, ...]).
-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).
To compile to disk and also load into memory the source files we can use the Logtalk built-in predicate logtalk_load/1:
@@ -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).
-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).
-Last updated on: April 22, 2002
+Last updated on: May 6, 2002
diff --git a/Logtalk/manuals/userman/messages.html b/Logtalk/manuals/userman/messages.html
index 96f7bf256..986126fb8 100644
--- a/Logtalk/manuals/userman/messages.html
+++ b/Logtalk/manuals/userman/messages.html
@@ -29,7 +29,7 @@ Logtalk uses the following three operators for message sending:
:- op(600, fx, ^^).
-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.
-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 .lgt but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk pre-processor) have, by default, a .pl 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 vehicle and save it in a vehicle.lgt source file that will be compiled to a vehicle.pl 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 .lgt but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk preprocessor) have, by default, a .pl 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 vehicle and save it in a vehicle.lgt source file that will be compiled to a vehicle.pl Prolog file.
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 user that contains all user p
Previous | Next | Table of Contents | Bibliography | Glossary
-Last updated on: August 5, 2000
+Last updated on: May 6, 2002
diff --git a/Logtalk/manuals/userman/predicates.html b/Logtalk/manuals/userman/predicates.html
index 96b452d96..33545a224 100644
--- a/Logtalk/manuals/userman/predicates.html
+++ b/Logtalk/manuals/userman/predicates.html
@@ -67,7 +67,7 @@ The first argument describes a valid calling mode. The minimum information will
-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: event, object, category, protocol, callable, term, nonvar, var, atomic, atom, number, integer, float, compound, and list. 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: event, object, category, protocol, callable, term, nonvar, var, atomic, atom, number, integer, float, compound, and list. 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.
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).
-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.
-Last updated on: July 4, 2000
+Last updated on: May 6, 2002
diff --git a/Logtalk/manuals/userman/programming.html b/Logtalk/manuals/userman/programming.html
index 39e1f9953..3ada22f4c 100644
--- a/Logtalk/manuals/userman/programming.html
+++ b/Logtalk/manuals/userman/programming.html
@@ -57,10 +57,10 @@ One of the advantages of a system like Logtalk is that it enable us to use the c
-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 .lgt but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk pre-processor) have, by default, a .pl 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 vehicle and save it in a vehicle.lgt source file that will be compiled to a vehicle.pl Prolog file. If we have a sort(_) parametric object we can save it on a sort1.lgt source file that will be compiled to a sort1.pl 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 .lgt but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk preprocessor) have, by default, a .pl 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 vehicle and save it in a vehicle.lgt source file that will be compiled to a vehicle.pl Prolog file. If we have a sort(_) parametric object we can save it on a sort1.lgt source file that will be compiled to a sort1.pl Prolog file. This name scheme helps avoid file name conflicts (remember that all Logtalk entities share the same name space).
-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.
@@ -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.
-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 read_term/3 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 read_term/3 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.
-Last updated on: December 30, 2001
+Last updated on: May 6, 2002
diff --git a/Logtalk/manuals/userman/protocols.html b/Logtalk/manuals/userman/protocols.html
index d8fc4c317..064d5414a 100644
--- a/Logtalk/manuals/userman/protocols.html
+++ b/Logtalk/manuals/userman/protocols.html
@@ -21,7 +21,7 @@ Protocols enable the separation between interface and implementation: several ob
-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 .lgt but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk pre-processor) have, by default, a .pl 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 listp and save it in a listp.lgt source file that will be compiled to a listp.pl 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 .lgt but this is optional and can be set in the configuration files. Compiled source files (by the Logtalk preprocessor) have, by default, a .pl 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 listp and save it in a listp.lgt source file that will be compiled to a listp.pl Prolog file.
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.
Previous | Next | Table of Contents | Bibliography | Glossary
-Last updated on: April 30, 2001
+Last updated on: May 6, 2002
diff --git a/Logtalk/xml/NOTES b/Logtalk/xml/NOTES
index 5e01a30cd..791b2bdb2 100644
--- a/Logtalk/xml/NOTES
+++ b/Logtalk/xml/NOTES
@@ -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.
=================================================================
diff --git a/Logtalk/xml/ie50.xsl b/Logtalk/xml/ie50.xsl
index b53df1608..598876e00 100644
--- a/Logtalk/xml/ie50.xsl
+++ b/Logtalk/xml/ie50.xsl
@@ -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.
%
diff --git a/Logtalk/xml/lgthtml.xsl b/Logtalk/xml/lgthtml.xsl
index ed17383e4..795510bf5 100644
--- a/Logtalk/xml/lgthtml.xsl
+++ b/Logtalk/xml/lgthtml.xsl
@@ -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.
%
diff --git a/Logtalk/xml/lgtpdfa4.xsl b/Logtalk/xml/lgtpdfa4.xsl
index e7d3e2dc5..bab8b8ac4 100644
--- a/Logtalk/xml/lgtpdfa4.xsl
+++ b/Logtalk/xml/lgtpdfa4.xsl
@@ -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.
%
diff --git a/Logtalk/xml/lgtpdfus.xsl b/Logtalk/xml/lgtpdfus.xsl
index 2703e034e..f645dafba 100644
--- a/Logtalk/xml/lgtpdfus.xsl
+++ b/Logtalk/xml/lgtpdfus.xsl
@@ -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.
%
diff --git a/Logtalk/xml/lgtxml.xsl b/Logtalk/xml/lgtxml.xsl
index 683922fad..3ca48147b 100644
--- a/Logtalk/xml/lgtxml.xsl
+++ b/Logtalk/xml/lgtxml.xsl
@@ -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.
%
diff --git a/Logtalk/xml/logtalk.dtd b/Logtalk/xml/logtalk.dtd
index f3508f8a9..66601a0cd 100644
--- a/Logtalk/xml/logtalk.dtd
+++ b/Logtalk/xml/logtalk.dtd
@@ -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.
%
diff --git a/Logtalk/xml/logtalk.xsd b/Logtalk/xml/logtalk.xsd
index 0b9e7df00..c2f340cba 100644
--- a/Logtalk/xml/logtalk.xsd
+++ b/Logtalk/xml/logtalk.xsd
@@ -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.
%
diff --git a/Logtalk/xml/texml.xsl b/Logtalk/xml/texml.xsl
index 34eec68ef..27c48002f 100644
--- a/Logtalk/xml/texml.xsl
+++ b/Logtalk/xml/texml.xsl
@@ -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.
%
diff --git a/library/logtalk/logtalk.pl b/library/logtalk/logtalk.pl
index 6259f5286..5ddd3f2c4 100644
--- a/library/logtalk/logtalk.pl
+++ b/library/logtalk/logtalk.pl
@@ -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).
diff --git a/library/logtalk/yap430.config b/library/logtalk/yap430.config
index 11397df8c..b389c95de 100644
--- a/library/logtalk/yap430.config
+++ b/library/logtalk/yap430.config
@@ -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
%
diff --git a/Logtalk/manuals/refman/builtins/logtalk_version3.html b/Logtalk/manuals/refman/builtins/logtalk_version3.html
index 2b3fefd96..d08453bc4 100644
--- a/Logtalk/manuals/refman/builtins/logtalk_version3.html
+++ b/Logtalk/manuals/refman/builtins/logtalk_version3.html
@@ -21,7 +21,7 @@
logtalk_version(Major, Minor, Patch)