caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Brown <caml-list@davidb.org>
To: Dustin Sallings <dustin@spy.net>
Cc: Jean-Baptiste Rouquier <jean-baptiste.rouquier@ens-lyon.fr>,
	caml-list@inria.fr
Subject: Re: [Caml-list] non-exported functions
Date: Wed, 29 Oct 2003 02:00:21 -0800	[thread overview]
Message-ID: <20031029100021.GA20874@davidb.org> (raw)
In-Reply-To: <C90D7771-09E4-11D8-B772-000393CFE6B8@spy.net>

On Tue, Oct 28, 2003 at 11:52:03PM -0800, Dustin Sallings wrote:
> 
> On Oct 28, 2003, at 10:50 PM, Jean-Baptiste Rouquier wrote:
> 
> >>I kinda liked automatically generating my .mli,
> >ocamlc -i foo.ml > foo.mli
> 
> 	Right, like that.  If I have to make a custom mli, I have to take 
> 	this out of my build system.  :)

If you wanted to feel more Haskell-like, you could have your build
system search for some specially formatted comment with an exports line
in it.  That way you could declare the things you want to export, and
filter the output of ocamlc -i.  You also want to make sure you write
the output to a temporary file, and only overwrite the foo.mli if it has
changed, otherwise you will rebuild way too much.

Dave

-------------------
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-10-29 17:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-28 20:02 Dustin Sallings
2003-10-28 21:07 ` Richard Jones
2003-10-28 21:10   ` Maxence Guesdon
2003-10-29  0:11     ` Dustin Sallings
2003-10-29  6:50       ` Jean-Baptiste Rouquier
2003-10-29  7:52         ` Dustin Sallings
2003-10-29 10:00           ` David Brown [this message]
2003-10-29 18:31           ` skaller
2003-10-29 18:25       ` skaller
2003-10-29 21:09         ` Richard Jones

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=20031029100021.GA20874@davidb.org \
    --to=caml-list@davidb.org \
    --cc=caml-list@inria.fr \
    --cc=dustin@spy.net \
    --cc=jean-baptiste.rouquier@ens-lyon.fr \
    /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).