From: SF Markus Elfring <elfring@users.sourceforge.net>
To: David Allsopp <dra-news@metastack.com>
Cc: moosotc@gmail.com, Gabriel Scherer <gabriel.scherer@gmail.com>,
caml-list@inria.fr
Subject: Re: [Caml-list] Interface(.mli) location
Date: Tue, 9 Aug 2016 11:22:35 +0200 [thread overview]
Message-ID: <378f6aa4-7e9d-19ee-2e45-93f386349703@users.sourceforge.net> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D901350423CC@Remus.metastack.local>
> a) Delete ./a.cmi as part of your build procedure.
Can this design option trigger difficulties in your file system configuration?
> This isn't ideal, though, because you lose the type-checking against d/a.cmi
Would you like to explain this conclusion a bit more?
> c) Implement a new option in the compiler driver which suppresses
> the automatic generation of .cmi files (e.g. ocamlc -c -I d -no-cmi a.ml)
I would find such a command parameter also useful.
Will any more fine-tuning be considered for the safer handling
of interface descriptions and corresponding implementations?
Regards,
Markus
next prev parent reply other threads:[~2016-08-09 9:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 16:09 moosotc
2016-08-08 17:03 ` Gabriel Scherer
2016-08-08 17:12 ` Gerd Stolpmann
2016-08-08 17:16 ` moosotc
2016-08-08 18:30 ` David Allsopp
2016-08-08 18:57 ` moosotc
2016-08-08 19:39 ` David Allsopp
2016-08-08 19:59 ` moosotc
2016-08-08 22:54 ` David Allsopp
2016-08-09 8:45 ` SF Markus Elfring
2016-08-09 16:26 ` David Allsopp
2016-08-09 17:55 ` SF Markus Elfring
2016-08-09 10:56 ` moosotc
2016-08-09 11:43 ` moosotc
2016-08-09 11:46 ` moosotc
2016-08-09 18:08 ` David Allsopp
2016-08-09 18:35 ` moosotc
2016-08-09 18:59 ` David Allsopp
2016-08-09 19:55 ` moosotc
2016-08-10 8:20 ` David Allsopp
2016-08-10 10:38 ` moosotc
2016-08-09 18:33 ` David Allsopp
2016-08-09 18:38 ` moosotc
2016-08-09 19:02 ` David Allsopp
2016-08-09 9:22 ` SF Markus Elfring [this message]
2016-08-09 16:32 ` David Allsopp
2016-08-09 18:10 ` SF Markus Elfring
2016-08-09 18:26 ` David Allsopp
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=378f6aa4-7e9d-19ee-2e45-93f386349703@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.com \
--cc=gabriel.scherer@gmail.com \
--cc=moosotc@gmail.com \
/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).