RE: [Caml-list] choosing modules at runtime

[Sebastien.deMentendeHorne@electrabel.com]

Hmmm, by the way, if a plugin architecture is needed, are we facing the same
problem ?

I did look at OCaml some weeks ago for an application which is at the moment
written in C++ and that needs a plugin architecture.
There are virtual classes on one side for specifying the interface of the
plugin (in ocaml, I think it would be module signatures) and concrete
classes that inherits from the virtual ones and that implements in different
ways the same signature (module implementations in ocaml). The algorithms
are generic as they are written for the virtual classes.
The loading of the different implementation is done dynamically and
dispatching of methods is done via polymorphism.

Is first class modules the elegant solution for this plugin framework (OCaml
not useful here)?
Does Ocaml offer another solution for this problem ?

Best regards,

Sébastien de Menten               |    ELECTRABEL 
Tel:  ++32 10 48 51 76            |    Risk Asset and Liability Management, 
Fax:  ++32 10 48 51 09            |    Place de l'université, 16, 4ème étage

Gsm:  ++32 478 789 444            |    B-1348 Louvain-la-Neuve, BELGIUM 



-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners