template<F> class EO +F that can be anything. The definition for that is (see EO.h) +
template<class F> class EO
The idea is that, later in your code, you can define a class as follows -(see for instance eoBin.h -
template<F> class eoBin : public EO<F>
-
{ ... code for eoBin };
+(see for instance eoBit.h).
+
template<class F> class eoBit : public
+EO<F>
+
{ ... code for eoBit };
and then use it in your application as -
eoBin<double> myeoBin; +
eoBit<double> myeoBit;
declares an object of type eoBin which has as fitness a double.
Whereas the advantages are obvious (writing generic reusable code instead
of having to rewrite the same pieces of code for different types), there
@@ -376,10 +377,6 @@ names of the variables they are used to initialize, e.g.
-
-
-
-
class eoMyClass
{
public:
@@ -448,7 +445,7 @@ object to store such nowhere-belonging pointers: whenever you allocate
such a thing, store it into an eoState : deleting that state will delete
all the stored pointers - one eoState is thus the only object you have
to care of.
-
The above pointera llocation sequence thus become +
The above pointer allocation sequence thus become
eoTournamentSelection<EOT> *ptSelect
= new eoTournamentSelection<EOT>(tSize);
state.storeFunctor(ptSelect);
@@ -492,10 +489,6 @@ main page - Algorithm-Based - Marc Schoenauer
-
-
Last
-modified: Mon Nov 6 07:01:57 CET 2000
+
Marc Schoenauer