Portability issues


Abstract Data Types
EO Generic Classes
EO Specific Classes
Utility classes

EO is a library created in Granada, Spain, Europe, with the main target of being an open platform for evolutionary computation, in general.

EO provides interfaces (in the ADT, abstract data types, directory), templates which follow those interfaces (in the generic directory), specific implementation of those templates (in the specific directory), and utilities, graphics representation, and so on a so forth.

EO has been designed so that all EC paradigms, except maybe genetic programming, can fit into it. All those paradigms are not that different, having for instance different genetic representations (in EO any object or chromosome with randomly accesible components or genes can be evolved), or selection and reproduction strategies (in EO, selection and reproduction strategies are just mappings from one population to another, so any of them can fit in).

The idea behind EO is component- and object-based computing. EO provides interfaces and some examples, but the community that uses it should provide the rest of components, needed to program any EC application, in any environment. EO has been developed and tested in WinNT and Unix machines, so it should have no problem in any one of them.

If you have any new component to include in EO, please write to us in eodev@kal-el.ugr,es; also if there is any compilation/runtime problem.

Conventions
This library will use an initial capital for all classes, initial lowercase for all objects. Abstract data types like EO belonging to the library will have the EO preffix, as in evolutionary || evolvable object, or both. Some other conventions

EO should be kept as portable as possible, including at least UNIX and Win platforms, with as many compilers as possible. In order to do so, try to follow these guidelines

alphabetic index hierarchy of classes


BinOp