Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
RE: [Caml-list] choosing modules at runtime
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2002-09-24 (11:10)
From: Sebastien.deMentendeHorne@e...
Subject: RE: [Caml-list] choosing modules at runtime

> On Tue, 24 Sep 2002, wrote:
> > Hmmm, by the way, if a plugin architecture is needed, are 
> we facing the same
> > problem ?
> It depends. In most cases higher-order modules (i.e. 
> functors) are perfect
> tools for creating plugin architectures. Problems only sometimes arise
> when "plugins" are dynamically selected or even generated, 
> e.g. depending
> on some command-line switches. Then they can become somewhat 
> cumbersome
> to use. In such cases first-class modules would be fine.
I looked at functors and they suffered of staticity.
The plugin we use are dynamically (runtime) selected and they should/could
be even generated at runtime, compiled, loaded and selected... I think that
plugins are most often used in a dynamic way so definitely, first-class
modules would be great.
To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: