Changeset 5054

Timestamp:

06/30/09 15:10:45 (8 months ago)

Author:

pmoura

Message:

Corrected some spelling and XHTML typos in the User and Reference Manuals.

Location:

trunk/manuals

Files:

• glossary.html (modified) (2 diffs)
• index.html (modified) (1 diff)
• refman/builtins/threaded1.html (modified) (1 diff)
• refman/directives/uses2.html (modified) (2 diffs)
• refman/grammar.html (modified) (2 diffs)
• refman/index.html (modified) (1 diff)
• refman/methods/clause2.html (modified) (2 diffs)
• refman/refman.header (modified) (1 diff)
• userman/categories.html (modified) (3 diffs)
• userman/index.html (modified) (2 diffs)
• userman/messages.html (modified) (5 diffs)
• userman/objects.html (modified) (3 diffs)
• userman/predicates.html (modified) (6 diffs)
• userman/protocols.html (modified) (3 diffs)
• userman/userman.header (modified) (1 diff)

trunk/manuals/glossary.html

@@ -118 +118 @@
 <dd>A request for a service, sent to an object. In more logical terms, a message can be seen as a request for proof construction using an object's predicates.</dd>
 
-<dt id="metainterpreter" class="glossary"><strong>metainterpreter</strong></dt>
+<dt id="meta-interpreter" class="glossary"><strong>meta-interpreter</strong></dt>
 <dd>A program capable of running other programs written in the same language.</dd>
 
@@ -205 +205 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/> 
-        <span>Last updated on: June 12, 2009</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">

trunk/manuals/index.html

@@ -31 +31 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/> 
-        <span>Last updated on: June 21, 2009</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">

trunk/manuals/refman/builtins/threaded1.html

@@ -70 +70 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/> 
-        <span>Last updated on: May 8, 2009</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">
-        <span><a href="../index.html#builtins">previous</a> | <a href="../../glossary.html">glossary</a> | <a href="threaded_once1.html">next</a></span><br/>
+        <span><a href="../index.html#builtins">previous</a> | <a href="../../glossary.html">glossary</a> | <a href="threaded_once1_2.html">next</a></span><br/>
         <span><a href="http://validator.w3.org/check/referer">XHTML</a> + <a href="http://jigsaw.w3.org/css-validator/check/referer">CSS</a></span>
     </div>

trunk/manuals/refman/directives/uses2.html

@@ -30 +30 @@
 </p>
 <p>
-It is possible to specify a predicate alias using the notation <code>Functor/Arity::Alias/Arity</code>. Aliases may be used either for avoiding conflicts between predicates specificed in several <code>uses/2</code> directives or for giving more meanfingul names considering the using context of the predicates.
+It is possible to specify a predicate alias using the notation <code>Functor/Arity::Alias/Arity</code>. Aliases may be used either for avoiding conflicts between predicates specified in several <code>uses/2</code> directives or for giving more meaningful names considering the using context of the predicates.
 </p>
 
@@ -63 +63 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/> 
-        <span>Last updated on: June 4, 2007</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">

trunk/manuals/refman/grammar.html

@@ -763 +763 @@
             <dd>"<code>(</code>" message "<code>,</code>" messages "<code>)</code>" |</dd>
             <dd>"<code>(</code>" message "<code>;</code>" messages "<code>)</code>" |</dd>
-            <dd>"<code>(</code>" message "<code>-></code>" messages "<code>)</code>"</dd>
+            <dd>"<code>(</code>" message "<code>-&gt;</code>" messages "<code>)</code>"</dd>
     </dl>
     <dl>
@@ -846 +846 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/> 
-        <span>Last updated on: June 12, 2009</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">

trunk/manuals/refman/index.html

@@ -346 +346 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/> 
-        <span>Last updated on: June 18, 2009</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">

trunk/manuals/refman/methods/clause2.html

@@ -29 +29 @@
 </p>
 <p>
-This method may be used to enumarete clauses for predicates that are not declared dynamic for dynamic objects provided that the predicates are declared in <em>this</em>.
+This method may be used to enumerate clauses for predicates that are not declared dynamic for dynamic objects provided that the predicates are declared in <em>this</em>.
 </p>
 
@@ -69 +69 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/> 
-        <span>Last updated on: April 29, 2009</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">

trunk/manuals/refman/refman.header

@@ -36 +36 @@
         <span>http://logtalk.org/</span>
     </p>
-    <p class="date">Last updated on June 18, 2009</p>
+    <p class="date">Last updated on June 30, 2009</p>
 </div>
 

trunk/manuals/userman/categories.html

@@ -109 +109 @@
 
 <p>
-We can find, by backtracking, all defined categories by using the <a title="Consult reference manual" href="../refman/builtins/current_category1.html"><code>current_category/1</code></a> Logtalk built-in predicate with an uninstantiated variable:
+We can find, by backtracking, all defined categories by using the <a title="Consult reference manual" href="../refman/builtins/current_category1.html"><code>current_category/1</code></a> Logtalk built-in predicate with a non-instantiated variable:
 </p>
 <pre>| ?- current_category(Category).</pre>
@@ -230 +230 @@
 <pre>| ?- implements_protocol(Category, Protocol, Scope).</pre>
 <p>
-Note that, if we use an uninstantiated variable for the first argument, we will need to use the <a title="Consult reference manual" href="../refman/builtins/current_category1.html"><code>current_category/1</code></a> built-in predicate to ensure that the returned entity is a category and not an object.
+Note that, if we use a non-instantiated variable for the first argument, we will need to use the <a title="Consult reference manual" href="../refman/builtins/current_category1.html"><code>current_category/1</code></a> built-in predicate to ensure that the returned entity is a category and not an object.
 </p>
 <p>
@@ -355 +355 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/> 
-        <span>Last updated on: May 3, 2009</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">

trunk/manuals/userman/index.html

@@ -282 +282 @@
         <dd><a href="programming.html#programming_cc">Conditional compilation</a><span class="leader"></span><span class="page-ref"><span class="programming_cc"></span></span></dd>
         <dd><a href="programming.html#programming_errors">Avoiding common errors</a><span class="leader"></span><span class="page-ref"><span class="programming_errors"></span></span></dd>
-        <dd><a href="programming.html#programming_style">Coding style guidlines</a><span class="leader"></span><span class="page-ref"><span class="programming_style"></span></span></dd>
+        <dd><a href="programming.html#programming_style">Coding style guidelines</a><span class="leader"></span><span class="page-ref"><span class="programming_style"></span></span></dd>
     <dt><a href="programming.html#programming_session">Running a Logtalk session</a><span class="leader"></span><span class="page-ref"><span class="programming_session"></span></span></dt>
         <dd><a href="programming.html#programming_starting">Starting Logtalk</a><span class="leader"></span><span class="page-ref"><span class="programming_starting"></span></span></dd>
         <dd><a href="programming.html#programming_compiling">Compiling and loading your programs</a><span class="leader"></span><span class="page-ref"><span class="programming_compiling"></span></span></dd>
         <dd><a href="programming.html#programming_flags">Compiler flags</a><span class="leader"></span><span class="page-ref"><span class="programming_flags"></span></span></dd>
-        <dd><a href="programming.html#programming_smart">Realoding and smart compilation of source files</a><span class="leader"></span><span class="page-ref"><span class="programming_smart"></span></span></dd>
+        <dd><a href="programming.html#programming_smart">Reloading and smart compilation of source files</a><span class="leader"></span><span class="page-ref"><span class="programming_smart"></span></span></dd>
         <dd><a href="programming.html#programming_batch">Using Logtalk for batch processing</a><span class="leader"></span><span class="page-ref"><span class="programming_batch"></span></span></dd>
     <dt><a href="programming.html#programming_debugging">Debugging Logtalk programs</a><span class="leader"></span><span class="page-ref"><span class="programming_debugging"></span></span></dt>
@@ -318 +318 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/>
-        <span>Last updated on: June 21, 2009</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">

trunk/manuals/userman/messages.html

@@ -23 +23 @@
 
 <p>
-Messages allows us to call object predicates. Logtalk uses the same nomenclature found in other object-oriented programming languages such as Smalltalk. Therefore, the terms <em>predicate</em> and <em>method</em> are often used interchangeably when refering to predicates defined inside objects and categories. A message must always match a predicate within the scope of the sender object.
+Messages allows us to call object predicates. Logtalk uses the same nomenclature found in other object-oriented programming languages such as Smalltalk. Therefore, the terms <em>predicate</em> and <em>method</em> are often used interchangeably when referring to predicates defined inside objects and categories. A message must always match a predicate within the scope of the sender object.
 </p>
 <p>
@@ -65 +65 @@
 
 <p>
-In the Logtalk context, broadcasting is interpreted as the sending of several messages to the same object. This can be achieved by using the message sending method described above. However, for convenience, Logtalk implements an extended syntax for message sending that may improve program readibility in some cases. This extended syntax uses the <code>(,)/2</code>, <code>(;)/2</code>, and <code>(->)/2</code> control constructs. For example, if we wish to send several messages to the same object, we can write:
+In the Logtalk context, broadcasting is interpreted as the sending of several messages to the same object. This can be achieved by using the message sending method described above. However, for convenience, Logtalk implements an extended syntax for message sending that may improve program readability in some cases. This extended syntax uses the <code>(,)/2</code>, <code>(;)/2</code>, and <code>(-&gt;)/2</code> control constructs. For example, if we wish to send several messages to the same object, we can write:
 </p>
 <pre>| ?- Object::(Message1, Message2, ...).</pre>
@@ -102 +102 @@
 
 <p>
-Every message sent using <a title="Consult reference manual" href="../refman/control/to_object2.html"><code>::/2</code></a> operator generates two events, allowe before and one after the message execution. Messages that are sent using the <a title="Consult reference manual" href="../refman/control/to_self1.html"><code>::/1</code></a> (message to <em>self</em>) operator or the <a title="Consult reference manual" href="../refman/control/super1.html"><code>^^/1</code></a> super mechanism described above do not generate any events. The rational behind this distinction is that messages to <em>self</em> and <em>super</em> calls are only used internally in the definition of methods or to execute additional messages with the same target object (represented by <em>self</em>). In other words, events are only generated when using an object's public interface; they cannot be used to break object encapsulation.
+Every message sent using the <a title="Consult reference manual" href="../refman/control/to_object2.html"><code>::/2</code></a> operator generates two events, one before and one after the message execution. Messages that are sent using the <a title="Consult reference manual" href="../refman/control/to_self1.html"><code>::/1</code></a> (message to <em>self</em>) operator or the <a title="Consult reference manual" href="../refman/control/super1.html"><code>^^/1</code></a> super mechanism described above do not generate any events. The rational behind this distinction is that messages to <em>self</em> and <em>super</em> calls are only used internally in the definition of methods or to execute additional messages with the same target object (represented by <em>self</em>). In other words, events are only generated when using an object's public interface; they cannot be used to break object encapsulation.
 </p>
 <p>
@@ -139 +139 @@
 </p>
 <p>
-With event-suport turned on, a message sent from a compiled object to another object translates to three predicate calls:
+With event-support turned on, a message sent from a compiled object to another object translates to three predicate calls:
 </p>
 <dl>
@@ -210 +210 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/> 
-        <span>Last updated on: May 1, 2009</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">

trunk/manuals/userman/objects.html

@@ -204 +204 @@
 
 <p>
-We can find, by backtracking, all defined objects by calling the <a title="Consult reference manual" href="../refman/builtins/current_object1.html"><code>current_object/1</code></a> built-in predicate with an uninstantiated variable:
+We can find, by backtracking, all defined objects by calling the <a title="Consult reference manual" href="../refman/builtins/current_object1.html"><code>current_object/1</code></a> built-in predicate with a non-instantiated variable:
 </p>
 <pre>| ?- current_object(Object).</pre>
@@ -394 +394 @@
 <pre>| ?- implements_protocol(Object, Protocol, Scope).</pre>
 <p>
-Note that, if we use an uninstantiated variable for the first argument, we will need to use the <a title="Consult reference manual" href="../refman/builtins/current_object1.html"><code>current_object/1</code></a> built-in predicate to ensure that the entity returned is an object and not a category.
+Note that, if we use a non-instantiated variable for the first argument, we will need to use the <a title="Consult reference manual" href="../refman/builtins/current_object1.html"><code>current_object/1</code></a> built-in predicate to ensure that the entity returned is an object and not a category.
 </p>
 <p>
@@ -443 +443 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/> 
-        <span>Last updated on: February 24, 2009</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">

trunk/manuals/userman/predicates.html

@@ -300 +300 @@
 <p>
 This allows clauses for a predicate to be defined in several objects or categories. This is a directive that should be used with great care. Support for this directive have been added to Logtalk primarily to support migration of Prolog module code. Spreading clauses for a predicate among several Logtalk entities can be handy in special cases but can also make your code difficult to understand and may pose a safety risk (e.g. by allowing an entity to peek inside other entity, breaking scope rules). Moreover, multifile predicates are only fully supported by some back-end Prolog compilers, raising portability concerns.
+</p>
 <p>
 Consider the following simple example:
@@ -335 +336 @@
 The Logtalk compiler will print a warning if the <code>multifile/1</code> directive is missing. Multifile predicates may also be declared dynamic using the same <code>Entity::Functor/Arity</code> notation (multifile predicates are static by default).
 </p>
+<p>
 When a clause of a multifile predicate is a rule, its body is compiled within the context of the object or category containing the clause. This allows clauses for multifile predicates to call local object or category predicates.
 </p>
@@ -397 +399 @@
 </p>
 <p>
-Some meta-predicates have meta-arguments which are not goals but closures. Logtalk supports the definition of meta-predicates that are called with closures instead of goals as long as the definition uses the Logtalk built-in predicate <a title="Consult reference manual" href="../refman/methods/call1.html"><code>call/N</code></a> to call the closure with the addtional arguments. For example:
+Some meta-predicates have meta-arguments which are not goals but closures. Logtalk supports the definition of meta-predicates that are called with closures instead of goals as long as the definition uses the Logtalk built-in predicate <a title="Consult reference manual" href="../refman/methods/call1.html"><code>call/N</code></a> to call the closure with the additional arguments. For example:
 </p>
 <pre>:- public(all_true/2).
@@ -639 +641 @@
 </p>
 <p>
-Term and goal expansion may be used either by calling the <code>expand_term/2</code> and <code>expand_goal/2</code> methods explicitly or by using <em><a class="glossary" title="Go to glossary definition" href="../../glossary.html#hook">hook objects</a></em>. Clauses for the <code>term_expansion/2</code> and <code>goal_expansion/2</code> predicates defined within an object or a category are never in the compilation of the object or the category itself.
+Term and goal expansion may be used either by calling the <code>expand_term/2</code> and <code>expand_goal/2</code> methods explicitly or by using <em><a class="glossary" title="Go to glossary definition" href="../glossary.html#hook">hook objects</a></em>. Clauses for the <code>term_expansion/2</code> and <code>goal_expansion/2</code> predicates defined within an object or a category are never in the compilation of the object or the category itself.
 </p>
 
@@ -723 +725 @@
 Prolog built-in meta-predicates may only be called locally within objects or categories, i.e. they cannot be used as messages. Compiling calls to non-standard, Prolog built-in meta-predicates can be tricky for two reasons: first, there is no standard way of checking if a built-in predicate is also a meta-predicate and finding out which are its meta-arguments; second, in some cases, the meta-arguments of a meta-predicate are not goals but closures, used for constructing goals. The way the goals are constructed is specific to the meta-predicate and cannot be reliable inferred by the Logtalk compiler. For meta-predicates whose meta-arguments are directly called as goals, the solution is to explicitly declare them in the corresponding Prolog configuration file using the predicate <code>'$lgt_pl_meta-predicate'/2</code>. For example:
 </p>
-<pre>'$lgt_pl_meta_predicate'(*->(::, ::), control_construct).
+<pre>'$lgt_pl_meta_predicate'(*-&gt;(::, ::), control_construct).
 '$lgt_pl_meta_predicate'(call_with_depth_limit(::, *, *), predicate).</pre>
 <p>
@@ -732 +734 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/> 
-        <span>Last updated on: June 12, 2009</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">

trunk/manuals/userman/protocols.html

@@ -57 +57 @@
 
 <p>
-We can find, by backtracking, all defined protocols by using the <a title="Consult reference manual" href="../refman/builtins/current_protocol1.html"><code>current_protocol/1</code></a> built-in predicate with an uninstantiated variable:
+We can find, by backtracking, all defined protocols by using the <a title="Consult reference manual" href="../refman/builtins/current_protocol1.html"><code>current_protocol/1</code></a> built-in predicate with a non-instantiated variable:
 </p>
 <pre>| ?- current_protocol(Protocol).</pre>
@@ -160 +160 @@
 <pre>| ?- implements_protocol(ObjectOrCategory, Protocol, Scope).</pre>
 <p>
-Note that, if we use an uninstantiated variable for the first argument, we will need to use the <a title="Consult reference manual" href="../refman/builtins/current_object1.html"><code>current_object/1</code></a> or <a title="Consult reference manual" href="../refman/builtins/current_category1.html"><code>current_category/1</code></a> built-in predicates to identify the kind of entity returned.
+Note that, if we use a non-instantiated variable for the first argument, we will need to use the <a title="Consult reference manual" href="../refman/builtins/current_object1.html"><code>current_object/1</code></a> or <a title="Consult reference manual" href="../refman/builtins/current_category1.html"><code>current_category/1</code></a> built-in predicates to identify the kind of entity returned.
 </p>
 
@@ -235 +235 @@
     <div class="copyright">
         <span>Copyright &copy; <a href="mailto:pmoura@logtalk.org">Paulo Moura</a> &mdash; <a href="http://logtalk.org">Logtalk.org</a></span><br/> 
-        <span>Last updated on: December 1, 2008</span>
+        <span>Last updated on: June 30, 2009</span>
     </div>
     <div class="navbottom">

trunk/manuals/userman/userman.header

@@ -36 +36 @@
         <span>http://logtalk.org/</span>
     </p>
-    <p class="date">Last updated on June 21, 2009</p>
+    <p class="date">Last updated on June 30, 2009</p>
 </div>