From: moosotc@gmail.com
To: David Allsopp <dra-news@metastack.com>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Interface(.mli) location
Date: Tue, 09 Aug 2016 14:43:03 +0300 [thread overview]
Message-ID: <87d1licgmw.fsf@gmail.com> (raw)
In-Reply-To: <87k2fqcirv.fsf@gmail.com> (moosotc@gmail.com's message of "Tue, 09 Aug 2016 13:56:52 +0300")
moosotc@gmail.com writes:
> David Allsopp <dra-news@metastack.com> writes:
>
[..snip..]
>>>
>>> d) Make the compiler skip generation of .cmi if it sees one in the -I
>>> directories?
>>
>> No - I think the use-case is too niche to justify breaking backwards
>> compatibility. That's potentially a very subtle way to break someone
>> else's existing build system. The existing behaviour is precisely
>> documented in the manual (even if it's not necessarily the best
>> approach).
>>
>
> Original post asked for either change of behavior or documentation, I
> failed to find the precise documentation, care pointing out where
> exactly things are described in the manual?
Also, consider this:
[malc@linmac2 mli]$ cat repro2.sh; sh repro2.sh
#!/bin/sh
set -x
rm -fr a* d o
mkdir -p o d
echo 'type a = int and b = int' >a.ml
echo 'type a = int' >d/a.mli
ocamlc -c -o o/a.cmi d/a.mli
md5sum o/a.cmi
ocamlc -c -o o/a.cmo a.ml
md5sum o/a.cmi
+ rm -fr a.ml d o
+ mkdir -p o d
+ echo 'type a = int and b = int'
+ echo 'type a = int'
+ ocamlc -c -o o/a.cmi d/a.mli
+ md5sum o/a.cmi
dddf074fdfa94cad226485870c617116 o/a.cmi
+ ocamlc -c -o o/a.cmo a.ml
+ md5sum o/a.cmi
bc44d889df40c61e43dbd94535ffd614 o/a.cmi
IOW compilation of a.ml will override .cmi produced by compilation of
a.mli, the point, I guess, is that there's a lot to specify here.
--
mailto:moosotc@gmail.com
next prev parent reply other threads:[~2016-08-09 11:50 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 [this message]
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
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=87d1licgmw.fsf@gmail.com \
--to=moosotc@gmail.com \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.com \
--cc=gabriel.scherer@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