Update rationale page

Author: pmoura

_pages/download.md

@@ -21,7 +21,7 @@ Prolog compiler is accomplished using a small
 includes adapter files for all supported Prolog compilers:
 
 -   [B-Prolog 8.1 or later versions](http://www.picat-lang.org/bprolog/)
--   [Ciao Prolog (version 1.21.0 or later)](http://ciao-lang.org) *(experimental)*
+-   [Ciao Prolog (version 1.22.0 or later)](http://ciao-lang.org) *(experimental)*
 -   [CxProlog 0.98.1 or later versions](http://ctp.di.fct.unl.pt/~amd/cxprolog/)
 -   [ECLiPSe 6.1\#143 or later versions](http://eclipseclp.org/)
 -   [GNU Prolog 1.4.5 or later versions](http://www.gprolog.org/)

_pages/rationale.md

@@ -16,9 +16,9 @@ Logtalk is designed to _extend_ and _leverage_ Prolog. It provides an alternativ
 * Default importing of module exported predicates when loading a module file
 * Strongly biased towards implicit predicate qualification
 
-These fundamental characteristics make module systems relatively simple to implement but also effectively prevent extending them to provide several key features present in Logtalk, some of them described here, that support a wide range of code encapsulation and reuse scenarios typically found in applications. Notably, Logtalk enables simple implementations of common design patterns that are cumbersome at best using Prolog modules.
+These fundamental characteristics make module systems relatively simple to implement but also effectively prevent extending them to provide several key features present in Logtalk, some of them described here, that support a wide range of code encapsulation and reuse scenarios typically found in applications. Notably, Logtalk enables simple implementations of [common design patterns](https://github.com/LogtalkDotOrg/logtalk3/tree/master/examples/design_patterns) that are cumbersome at best using Prolog modules.
 
-Logtalk also fixes some murky predicate semantics found in Prolog, improves some of its key mechanisms, and provides unique libraries. Note that all advantages described next _coexist_ with Prolog. I.e. Logtalk acts strictly as an _add-on_. It does not patch or modify Prolog's own built-in features.
+Logtalk also fixes some murky predicate semantics found in Prolog, improves some of its key mechanisms, and provides unique [libraries](https://logtalk.org/manuals/libraries/index.html). Note that all advantages described next _coexist_ with Prolog. I.e. Logtalk acts strictly as an _add-on_. It does not patch or modify Prolog's own built-in features.
 
 ### Protocols (interfaces)
 
@@ -107,7 +107,7 @@ The Logtalk code is as readable as the module code, provides the same performanc
 
 ### Portability
 
-Logtalk is written in highly portable code and currently supports [15 backend Prolog systems](download.html#requirements). It can support any Prolog system that complies with official and de facto core standards. Logtalk libraries and [developer tools](tools.html) are also portable. Portability implies robustness (by allowing testing with a larger number of Prolog systems) and risk mitigation (by facilitating switching between Prolog systems).
+Logtalk is written in highly portable code and currently supports [15 backend Prolog systems](download.html#requirements). It can support any Prolog system that complies with official and de facto core standards. Logtalk [libraries](https://logtalk.org/manuals/libraries/index.html) and [developer tools](tools.html) are also portable. Portability contributes to robustness (by allowing testing with a larger number of Prolog systems) and risk mitigation (by facilitating switching between Prolog systems).
 
 In contrast, the ISO Prolog standard for modules is ignored (for sound reasons) by Prolog implementers. Worse, Prolog systems implementing a module system have significant differences that hinder portability. A few examples:
 
@@ -128,11 +128,11 @@ In addition, not all Prolog systems implement modules. Examples include B-Prolog
 
 Logtalk provides **fully portable** implementations of key mechanisms to all supported backend Prolog compilers. These include:
 
-* Conditional compilation
-* Term-expansion
-* Message printing
-* Question asking
-* Reflection
+* [Conditional compilation](https://logtalk.org/manuals/refman/directives/conditional_compilation_directives.html)
+* [Term-expansion](https://logtalk.org/manuals/userman/expansion.html)
+* [Message printing](https://logtalk.org/manuals/userman/printing.html)
+* [Question asking](https://logtalk.org/manuals/userman/printing.html#asking-questions)
+* [Reflection](https://logtalk.org/manuals/userman/reflection.html)
 
 Conditional compilation directives are found nowadays in most Prolog systems although some implementations are buggy, including in some high profile systems, if you need more than the very basic usage.
 

_pages/tools.md

@@ -94,6 +94,7 @@ working code that also comply with coding guidelines. Lint checks include:
 -   File, entity, predicate, and variable names not following official coding guidelines
 -   Variable names that differ only on case
 -   Clauses whose body is a disjunction
+-   Naked meta-variables in cut-transparent control constructs
 
 Lint checks are controlled by a set of [compiler flags](https://logtalk.org/manuals/userman/programming.html#lint-flags).
 Additional checks are provided by the [`make`](#make) and [`dead_code_scanner`](#dead-code-scanner) tools, by libraries, and by other developer tools. For large projects, the data generated by the [`code_metrics`](#code-metrics) tool may also be relevant in accessing the quality of your code.

_site/download.html

@@ -291,7 +291,7 @@ <h2 id="requirements">Requirements</h2>
 
 <ul>
   <li><a href="http://www.picat-lang.org/bprolog/">B-Prolog 8.1 or later versions</a></li>
-  <li><a href="http://ciao-lang.org">Ciao Prolog (version 1.21.0 or later)</a> <em>(experimental)</em></li>
+  <li><a href="http://ciao-lang.org">Ciao Prolog (version 1.22.0 or later)</a> <em>(experimental)</em></li>
   <li><a href="http://ctp.di.fct.unl.pt/~amd/cxprolog/">CxProlog 0.98.1 or later versions</a></li>
   <li><a href="http://eclipseclp.org/">ECLiPSe 6.1#143 or later versions</a></li>
   <li><a href="http://www.gprolog.org/">GNU Prolog 1.4.5 or later versions</a></li>

_site/rationale.html

@@ -287,9 +287,9 @@
   <li>Strongly biased towards implicit predicate qualification</li>
 </ul>
 
-<p>These fundamental characteristics make module systems relatively simple to implement but also effectively prevent extending them to provide several key features present in Logtalk, some of them described here, that support a wide range of code encapsulation and reuse scenarios typically found in applications. Notably, Logtalk enables simple implementations of common design patterns that are cumbersome at best using Prolog modules.</p>
+<p>These fundamental characteristics make module systems relatively simple to implement but also effectively prevent extending them to provide several key features present in Logtalk, some of them described here, that support a wide range of code encapsulation and reuse scenarios typically found in applications. Notably, Logtalk enables simple implementations of <a href="https://github.com/LogtalkDotOrg/logtalk3/tree/master/examples/design_patterns">common design patterns</a> that are cumbersome at best using Prolog modules.</p>
 
-<p>Logtalk also fixes some murky predicate semantics found in Prolog, improves some of its key mechanisms, and provides unique libraries. Note that all advantages described next <em>coexist</em> with Prolog. I.e. Logtalk acts strictly as an <em>add-on</em>. It does not patch or modify Prolog’s own built-in features.</p>
+<p>Logtalk also fixes some murky predicate semantics found in Prolog, improves some of its key mechanisms, and provides unique <a href="https://logtalk.org/manuals/libraries/index.html">libraries</a>. Note that all advantages described next <em>coexist</em> with Prolog. I.e. Logtalk acts strictly as an <em>add-on</em>. It does not patch or modify Prolog’s own built-in features.</p>
 
 <h3 id="protocols-interfaces">Protocols (interfaces)</h3>
 
@@ -374,7 +374,7 @@ <h3 id="objects-subsume-modules">Objects subsume modules</h3>
 
 <h3 id="portability">Portability</h3>
 
-<p>Logtalk is written in highly portable code and currently supports <a href="download.html#requirements">15 backend Prolog systems</a>. It can support any Prolog system that complies with official and de facto core standards. Logtalk libraries and <a href="tools.html">developer tools</a> are also portable. Portability implies robustness (by allowing testing with a larger number of Prolog systems) and risk mitigation (by facilitating switching between Prolog systems).</p>
+<p>Logtalk is written in highly portable code and currently supports <a href="download.html#requirements">15 backend Prolog systems</a>. It can support any Prolog system that complies with official and de facto core standards. Logtalk <a href="https://logtalk.org/manuals/libraries/index.html">libraries</a> and <a href="tools.html">developer tools</a> are also portable. Portability contributes to robustness (by allowing testing with a larger number of Prolog systems) and risk mitigation (by facilitating switching between Prolog systems).</p>
 
 <p>In contrast, the ISO Prolog standard for modules is ignored (for sound reasons) by Prolog implementers. Worse, Prolog systems implementing a module system have significant differences that hinder portability. A few examples:</p>
 
@@ -398,11 +398,11 @@ <h3 id="key-mechanisms">Key mechanisms</h3>
 <p>Logtalk provides <strong>fully portable</strong> implementations of key mechanisms to all supported backend Prolog compilers. These include:</p>
 
 <ul>
-  <li>Conditional compilation</li>
-  <li>Term-expansion</li>
-  <li>Message printing</li>
-  <li>Question asking</li>
-  <li>Reflection</li>
+  <li><a href="https://logtalk.org/manuals/refman/directives/conditional_compilation_directives.html">Conditional compilation</a></li>
+  <li><a href="https://logtalk.org/manuals/userman/expansion.html">Term-expansion</a></li>
+  <li><a href="https://logtalk.org/manuals/userman/printing.html">Message printing</a></li>
+  <li><a href="https://logtalk.org/manuals/userman/printing.html#asking-questions">Question asking</a></li>
+  <li><a href="https://logtalk.org/manuals/userman/reflection.html">Reflection</a></li>
 </ul>
 
 <p>Conditional compilation directives are found nowadays in most Prolog systems although some implementations are buggy, including in some high profile systems, if you need more than the very basic usage.</p>

_site/tools.html

@@ -361,6 +361,7 @@ <h2 id="lint-checker">Lint checker</h2>
   <li>File, entity, predicate, and variable names not following official coding guidelines</li>
   <li>Variable names that differ only on case</li>
   <li>Clauses whose body is a disjunction</li>
+  <li>Naked meta-variables in cut-transparent control constructs</li>
 </ul>
 
 <p>Lint checks are controlled by a set of <a href="https://logtalk.org/manuals/userman/programming.html#lint-flags">compiler flags</a>.