From: Manos Renieris <er@cs.brown.edu>
To: Chris Hecker <checker@d6.com>
Cc: Brian Hurt <brian.hurt@qlogic.com>,
Stefan Heimann <lists@stefanheimann.net>,
Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Automatic generation of mli files
Date: Fri, 6 Jun 2003 17:06:23 -0400 [thread overview]
Message-ID: <20030606210622.GA29247@cs.brown.edu> (raw)
In-Reply-To: <4.3.2.7.2.20030606121624.016d8770@localhost>
On Fri, Jun 06, 2003 at 12:21:17PM -0700, Chris Hecker wrote:
>
> And, for having mlis around for decoupling for build dependencies (as
> opposed to having them for interface design, where you care about what's
> exported), ocaml -i > foo.mli works just fine.
At least under unix, it does not.
The shell creates foo.mli before the compilation starts; ocamlc sees
that and believes a .cmi should exist; but it doesn't; so compilation
aborts.
Xavier Leroy has promised
(http://caml.inria.fr/archives/200302/msg00078.html)
a separate command line option to generate .mli's without compiling,
but I don't see it yet.
-- Manos
-------------------
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 21:06 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
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 [this message]
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=20030606210622.GA29247@cs.brown.edu \
--to=er@cs.brown.edu \
--cc=brian.hurt@qlogic.com \
--cc=caml-list@inria.fr \
--cc=checker@d6.com \
--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).