From: Ville-Pertti Keinonen <will@exomi.com>
To: Stefan Heimann <lists@stefanheimann.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Automatic generation of mli files
Date: Fri, 6 Jun 2003 19:17:14 +0300 [thread overview]
Message-ID: <55FE3CF4-983A-11D7-9B2B-000393863F70@exomi.com> (raw)
In-Reply-To: <20030606155932.GA12058@kunz.ratzer>
> Maybe I should tell how I want to use the tool. I don't want to update
> the .mli file automatically everytime I change something in the .ml
> file. I want to use the compiler as I would do without the tool. The
Having an .mli that may or may not be machine generated would probably
cause unnecessary problems.
You could also generate the .cmi from the .ml; this is already done if
it doesn't already exist. Making minor additions to the top-level
compiler syntax to indicate whether to exclude or make abstract
definitions in the .ml when generating the .cmi shouldn't be too
difficult.
-------------------
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
next prev parent reply other threads:[~2003-06-06 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 9:57 Stefan Heimann
2003-06-06 11:53 ` Maxence Guesdon
2003-06-06 15:33 ` Brian Hurt
2003-06-06 15:59 ` Stefan Heimann
2003-06-06 16:17 ` Ville-Pertti Keinonen [this message]
2003-06-06 18:30 ` Chris Hecker
2003-06-06 19:16 ` Brian Hurt
2003-06-06 19:21 ` Chris Hecker
2003-06-06 21:06 ` Manos Renieris
2003-06-06 22:06 ` Chris Hecker
2003-06-06 20:24 ` Stefan Heimann
2003-06-06 20:38 ` Jeffrey J. Cook
[not found] ` <200306091226.13255.yangsx@fltrp.com>
2003-06-09 4:59 ` Yang Shouxun
2003-06-09 8:10 ` Stefan Heimann
2003-06-07 0:27 ` John Max Skaller
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=55FE3CF4-983A-11D7-9B2B-000393863F70@exomi.com \
--to=will@exomi.com \
--cc=caml-list@inria.fr \
--cc=lists@stefanheimann.net \
/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).