From: jeanmarc.eber@lexifi.com
To: Chris Hecker <checker@d6.com>
Cc: Emmanuel Renieris <er@cs.brown.edu>, caml-list@inria.fr
Subject: Re: [Caml-list] interface printing without generating object code?
Date: Sun, 09 Feb 2003 19:45:43 +0100 (MET) [thread overview]
Message-ID: <1044816343.3e46a1d7edc91@imp.pro.proxad.net> (raw)
In-Reply-To: <4.3.2.7.2.20030207180803.03087ef8@localhost>
Quoting Chris Hecker <checker@d6.com>:
>
> >What do you want that's not
> > ocamlc -i -c foo.ml -o /dev/null
> >?
>
> I tried that (well, the windows version with NUL) and it didn't work.
> It
> still generated both a cmi and a cmo. Doesn't yours generate a cmi at
> least, even on unix? I want no output except stdout.
>
>>What do you want that's not
>> ocamlc -i -c foo.ml -o /dev/null
>>?
>I tried that (well, the windows version with NUL) and it didn't work. It
>still generated both a cmi and a cmo. Doesn't yours generate a cmi at
>least, even on unix? I want no output except stdout.
Indeed, something not too far away from what you want exists today in the
compiler; look into /utils/clflags.ml:
let dont_write_files = ref false (* set to true under ocamldoc *)
This flag is used for avoiding the production of a cmi file (look
at file typing/typemod.ml:
if not !Clflags.dont_write_files then
Env.save_signature sg modulename (prefixname ^ ".cmi");
when the module is used in conjunction with ocamldoc.
My guess:
It should be enough to
-make this flag "accessible" by a compiler switch, and
-to add a similar test in 2 or 3 places, for avoiding any file production
by the compiler.
I argue also in favor of such an enhancement.
Jean-Marc Eber
LexiFi
-------------------
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-02-09 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 3:07 Chris Hecker
2003-02-07 21:48 ` Emmanuel Renieris
2003-02-08 2:09 ` Chris Hecker
2003-02-08 22:06 ` Emmanuel Renieris
2003-02-09 12:08 ` Michal Moskal
2003-02-09 18:45 ` jeanmarc.eber [this message]
2003-02-10 8:59 ` Xavier Leroy
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=1044816343.3e46a1d7edc91@imp.pro.proxad.net \
--to=jeanmarc.eber@lexifi.com \
--cc=caml-list@inria.fr \
--cc=checker@d6.com \
--cc=er@cs.brown.edu \
/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