Fixing a small glitch that was giving wrong clues to newcomers ...

Thanks to Christophe-Marie Duquesne for the post
This commit is contained in:
evomarc 2008-12-25 16:01:57 +00:00
commit 893204f8f1

View file

@ -36,13 +36,13 @@ the fitness: an EO object is some object which has a fitness of some type
F that can be anything. The definition for that is (see <font face="Arial,Helvetica"><a href="../../doc/html/_e_o_8h-source.html">EO.h</a></font>) F that can be anything. The definition for that is (see <font face="Arial,Helvetica"><a href="../../doc/html/_e_o_8h-source.html">EO.h</a></font>)
<p><b><tt><font color="#999900">template&lt;class F> class EO</font></tt></b> <p><b><tt><font color="#999900">template&lt;class F> class EO</font></tt></b>
<p>The idea is that, later in your code, you can define a class as follows <p>The idea is that, later in your code, you can define a class as follows
(see for instance&nbsp; <a href="../../doc/html/eo_bit_8h-source.html">eoBit.h</a>). (see for instance&nbsp; <a href="../../doc/html/eoOneMax.html">eoOneMax.h</a> - or check <a href="eoLesson5.html">Lesson 5</a> for more details).
<p><b><tt><font color="#999900">template&lt;class F> class eoBit : public <p><b><tt><font color="#999900">template&lt;class F> class eoOneMax : public
EO&lt;F></font></tt></b> EO&lt;F></font></tt></b>
<br><b><tt><font color="#999900">{ ... code for eoBit&nbsp; };</font></tt></b> <br><b><tt><font color="#999900">{ ... code for eoOneMax&nbsp; };</font></tt></b>
<p>and then use it in your application as <p>and then use it in your application as
<p><b><tt><font color="#999900">eoBit&lt;double> myeoBit;</font></tt></b> <p><b><tt><font color="#999900">eoOneMax&lt;double> myeoBit;</font></tt></b>
<p>declares an object of type eoBin which has as fitness a double. <p>declares an object of type eoOneMax which has as fitness a double.
<p>Whereas the <b><font color="#FF6600">advantages</font></b> <p>Whereas the <b><font color="#FF6600">advantages</font></b>
are obvious (writing generic reusable code instead are obvious (writing generic reusable code instead
of having to rewrite the same pieces of code for different types), there of having to rewrite the same pieces of code for different types), there