Jon Harrop wrote:
> Just occurred to me that one possible solution to our brittle bindings problem 
> might be to parameterize the whole library over the external calls that are 
> made.

Indeed, that's a brilliant idea. Btw, it has been suggested to you a few 
weeks ago.

http://groups.google.com/group/fa.caml/msg/cc6adc628b396b06:
> What you can do is to ship your library as a single module abstracted
> over all its dependencies (that is, a functor which takes as arguments
> modules from the stdlib and other dependent libraries). You can put in
> the interface whatever you expect from these modules, so the same
> functor could be used with future versions if they only add new fields
> (but not new constructors or record fields, for instance). Again, some
> Camlp4 hack could somewhat automate this. 



-- Alain