caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Eray Ozkural <exa@kablonet.com.tr>
To: caml-list@inria.fr
Subject: [Caml-list] Module intf/impl annoyances
Date: Sat, 12 Apr 2003 19:18:33 +0300	[thread overview]
Message-ID: <200304121918.33443.exa@kablonet.com.tr> (raw)

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


             reply	other threads:[~2003-04-15 20:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12 16:18 Eray Ozkural [this message]
2003-04-22 13:23 ` Hendrik Tews
2003-04-25  9:29   ` Jean-Christophe Filliatre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200304121918.33443.exa@kablonet.com.tr \
    --to=exa@kablonet.com.tr \
    --cc=caml-list@inria.fr \
    --cc=erayo@cs.bilkent.edu.tr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).