From: Sam Steingold <sds@podval.org>
To: EL CHAAR Rabih SGAM/AI/SAM <RABIH.ELCHAAR@sgam.com>
Cc: caml-list@inria.fr
Subject: Re: stand-alone top-level
Date: Tue, 17 Apr 2007 10:23:57 -0400 [thread overview]
Message-ID: <4624D87D.9020906@podval.org> (raw)
In-Reply-To: <7625D6A1880B4C4DA11D2EBB8B43D2B90174741A@FRDEF-EXMB03.europe.am.socgen>
EL CHAAR Rabih SGAM/AI/SAM wrote:
> If you speak about the toplevel as interactive, it needs to see the modules interfaces in order to do the type checking, compilation, ...
> These were always in cmi files, which are not embedded in libraries (cma or cmxa).
it would be nice if they were optionally embeddable in the interactive
top-level.
next prev parent reply other threads:[~2007-04-17 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 14:14 EL CHAAR Rabih SGAM/AI/SAM
2007-04-17 14:23 ` Sam Steingold [this message]
2007-04-17 16:11 ` [Caml-list] " ls-ocaml-developer-2006
-- strict thread matches above, loose matches on Subject: below --
2007-04-17 8:03 [Caml-list] " EL CHAAR Rabih SGAM/AI/SAM
2007-04-17 13:54 ` Sam Steingold
2007-04-16 17:52 Sam Steingold
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=4624D87D.9020906@podval.org \
--to=sds@podval.org \
--cc=RABIH.ELCHAAR@sgam.com \
--cc=caml-list@inria.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).