diff --git a/eo/tutorial/html/eoCheckPoint.html b/eo/tutorial/html/eoCheckPoint.html index 49dd8d99..fe1b4f24 100644 --- a/eo/tutorial/html/eoCheckPoint.html +++ b/eo/tutorial/html/eoCheckPoint.html @@ -58,7 +58,7 @@ and the interface for its operator() is bool operator()(const eoPop<EOT>& ) -

which you could have guessed from the inheritance +

which you could have guessed from the inheritance diagram for class eoContinue, as you see there that eoContinue derives from class eoUF<const eoPop<EOT>&, @@ -88,7 +88,7 @@ when the stopping criterion is met! Existing continuators: Of course you can find out all existing (non-virtual!) subclasses of eoContinue -by looking at its  inheritance +by looking at its  inheritance diagram. But you might find it more convenient to have them listed here:

Exercise diff --git a/eo/tutorial/html/eoLesson3.html b/eo/tutorial/html/eoLesson3.html index 46e2e89f..5213ec9a 100644 --- a/eo/tutorial/html/eoLesson3.html +++ b/eo/tutorial/html/eoLesson3.html @@ -130,7 +130,7 @@ you want to handle (i.e. iinteger, double, yourPrivateClass, ...). In this lesson, we will not go into details: e.g. we will not tell you that the -eoValueParam +eoValueParam is actually a templatized sub-class of abstract class eoParam (oops, I said it!), nor will we deal with parameters outside their use from an eoParser. See the parameter section of the Component-Based tutorial, or wait until @@ -267,7 +267,7 @@ class. eoStateeoObjects that have both an input method (readFrom) and an output method (printOn), -i.e. that derive from the base class eoPersistent. +i.e. that derive from the base class eoPersistent. You must first register object into a state, and can then save them to a (text) file, and later read them from that file using the load @@ -319,7 +319,7 @@ compute whatever is needed over that population. templatized over the type of what they compute (e.g. double, or pair<double>, -or ...). But looking at the inheritance +or ...). But looking at the inheritance diagram of the eoStat class, you find that eoStat objects are also eoValueParam diff --git a/eo/tutorial/html/eoOperators.html b/eo/tutorial/html/eoOperators.html index 0e65fb2b..8884adaa 100644 --- a/eo/tutorial/html/eoOperators.html +++ b/eo/tutorial/html/eoOperators.html @@ -87,29 +87,29 @@ the genotype argument has been modified or not. @@ -122,8 +122,8 @@ former type (2 --> 2) is termed quadratic crossover operator, and is implemanted in the eoQuadOp class; the latter type (2 --> 1) is termed binary operator and is implemanted in class eoBinOp. Both classes are, as usual, templatized by the type of individual they -can handle (see documentation for eoBinOp -and eoQuadOp). +can handle (see documentation for eoBinOp +and eoQuadOp).

Note: Whereas it is straightforward to create a binary crossover operator from a quadratic one (by discarding the changes on the second parent), the reverse might prove impossible (imagine @@ -207,7 +207,7 @@ operators: MutationMutation operators modify one single individual. The corresponding EO class is called eoMonOp. and it si as usual templatized by the type of individual it can handle (see documentation -for eoMonOp). +for eoMonOp).

Interfaces:
The general approach in EO about simple variation operators is to perform in-place @@ -280,7 +280,7 @@ ways to get the parents they will involve, e.g. they can use a different selector for each of the parents they need to select.

The corresponding EO class is called eoGenOp. and it is as usual templatized by the type of individual it can handle -(see documentation for eoGenOp +(see documentation for eoGenOp :-)

Interface:
All the work a general operator is done within the apply() @@ -504,7 +504,7 @@ mainly behaves like an iterator over a population (hence the name, Population-Iterator).

The basic interface of an eoPopulator -(see also the documentation, +(see also the documentation, of course) is the following:

  • diff --git a/eo/tutorial/html/eoProgramming.html b/eo/tutorial/html/eoProgramming.html index b5bca286..cec3d95b 100644 --- a/eo/tutorial/html/eoProgramming.html +++ b/eo/tutorial/html/eoProgramming.html @@ -71,12 +71,12 @@ a hierarchy of functions with defaults behaviors and specialized sub-functions ...
-Functors are so intimately linked to EO that a base class (eoFunctorBase) +Functors are so intimately linked to EO that a base class (eoFunctorBase) has been designed to hold all functors. This base class is itself divided into three derived class. These classes tell you immediately what kind of arguments the operator() method requires and what kind of result it produces. See EO -conventions, and the inheritance +conventions, and the inheritance diagram of class eoFunctorBase.
For a more complete introduction to functors, with detailed discussion, go to the STL @@ -118,7 +118,7 @@ method. is for arity-zero functors, i.e.  their operator() method does not require any argument. It has a single template parameter, the return type of the operator() -method. For instance,  eoMonitor  +method. For instance,  eoMonitor  are eoF's that return an eoMonitor &. @@ -127,7 +127,7 @@ that return an eoMonitor &operator() method requires one argument. It has two template parameters, the type of the argument and the return type of the operator() -method. For instance,  eoMonOp's +method. For instance,  eoMonOp's are eoUF's that take as argument an EOT & and return void @@ -138,14 +138,14 @@ and return voidoperator() method requires two arguments. It has three template parameters, the types of the arguments and the return type of the operator() -method. For instance,  eoBinOp's +method. For instance,  eoBinOp's are eoBF's that take as arguments a const EOT & and an EOT &, and return void . -Now go back to the inheritance +Now go back to the inheritance diagram of class eoFunctorBase, and guess the interface for all functors!

Note: for @@ -153,7 +153,7 @@ obvious simplicity reasons, we very often omit the reference to the