Browse thread
Nesting Modules
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Daniel_Bünzli <daniel.buenzli@e...> |
| Subject: | Re: [Caml-list] Nesting Modules |
Le 2 nov. 05 à 11:47, Richard Jones a écrit : > consider a database layer: > > Database > Database_Postgres > Database_MySQL > > Obviously '_' is the way to go here if you want multiple third parties > to provide database modules. 'include' wouldn't work at all here. You are right. I think 'include' doesn't work here because there is a notion of choice. If I understand well your example, functors wouldn't help here because it is not that you want to get a unified interface (frontend) from a specific database implementation (backend), but you really want to access database specific features via the third party modules, right ? Daniel