[Caml-list] parametric modules file layout

[Caml-list] parametric modules file layout

[Ivan]

Hello!

I'm creating a functor named Forest that is parametrized by two modules: A - defines operations on assoc pair, and H - defines operations on hierarchical types. So I have three signatures : ASSOC, HIER, FOREST and one module Make. Each signature is rather large and needs to be defined both in mli and ml. 

I know, that with types the problem of code repetition can be solved by refactoring them in a separate module (a ml file with implicit mli). Is it a valid solution for signatures? Can I put a signature in the sig.ml file and then refer to it with  ``Sig.ASSOC?'' Or maybe there're other solutions or common practices to solve such problems?


Thanks, in advance.

Re: [Caml-list] parametric modules file layout

[Romain Bardou]

On 18/07/2012 09:16, Ivan wrote:
>
> Hello!
>
> I'm creating a functor named Forest that is parametrized by two modules: A - defines operations on assoc pair, and H - defines operations on hierarchical types. So I have three signatures : ASSOC, HIER, FOREST and one module Make. Each signature is rather large and needs to be defined both in mli and ml.
>
> I know, that with types the problem of code repetition can be solved by refactoring them in a separate module (a ml file with implicit mli). Is it a valid solution for signatures? Can I put a signature in the sig.ml file and then refer to it with  ``Sig.ASSOC?'' Or maybe there're other solutions or common practices to solve such problems?
>
>
> Thanks, in advance.
>

I don't think there is any problem with that solution. It's what I would do.

Cheers,

-- 
Romain

Re: [Caml-list] parametric modules file layout

[Dan Bensen]

[-- Attachment #1: Type: text/plain, Size: 259 bytes --]

> three signatures : ASSOC, HIER, FOREST
> put a signature in the sig.ml file
> maybe there're other solutions or common practices

I don't know if this is common, but you could 
put them in separate .ml files and call the types 
ASSOC.T, HIER.T, and FOREST.T

[-- Attachment #2: Type: text/html, Size: 581 bytes --]