11:32 <liyang> 'ullo all...

11:34 <liyang> how do I have a module export a non-opaque type without having the (identical) type definition twice? (Once in the implementation, other in the interface.)

11:41 <karryall> liyang: you can't

11:43 <liyang> ick... it's a good thing this is only a single line, but surely you wouldn't want to do that for anything larger?

11:44 <karryall> you can use the -i option of the compiler : it ouputs the type of the module it compiles

11:47 <liyang> Hm... Is that what people normally do? I've a single-implementation module here (and have no intention to make another one; it's just what I gleaned from The Book)... should I just stick to a single source file in that case?

11:49 <karryall> Hum. I'm not sure I understand you.

11:49 <liyang> (but what if I do want to hide certain bits of the module...)

11:49 <karryall> If you have a "small" .ml file, you can use it without a .mli

11:50 <karryall> but if you want to hide some things you have to use a .mli

11:50 <liyang> I've a module.ml and module.mli -- I'd rather not duplicate information in both files if I can possible avoid it...

11:51 <karryall> anyway the compiler checks that the 2 files are consistent

11:51 <liyang> ah okay...

11:51 <karryall> ... and that's what people normally do

11:51 <liyang> thanks for pointing out -i to me. I'll keep that one in mind. :)

11:52 <mellum> you don't really need a .mli...

11:52 <mellum> if you don't provide one, the compiler will just assume you export everything.

11:52 <liyang> I'd like to keep a few things hidden though, that's the thing.