Hi there,

I ran into what I think is a counter-intuitive feature in separate compilation 
of modules that I want to share with you.

It looks like others also had problems with having to dupe type signatures in 
both .mli and .ml files, so is there a working proposal to that end?

Since the .mli and .ml files are properly seen as sig and struct declarations, 
it looks as if a slight change in the semantics of struct would solve the 
problem: Those types declared in the corresponding sig but not redeclared in 
the struct are part of the struct. Is that really a reasonable and 
transparent solution?

The "other" cool functional language solves this by qualifying what to export; 
having the advantage that you declare types only once.

Thanks,

-- 
Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr>
Comp. Sci. Dept., Bilkent University, Ankara  KDE Project: http://www.kde.org
www: http://www.cs.bilkent.edu.tr/~erayo  Malfunction: http://mp3.com/ariza
GPG public key fingerprint: 360C 852F 88B0 A745 F31B  EA0F 7C07 AE16 874D 539C


-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners