From: David Allsopp <dra-news@metastack.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: "moosotc@gmail.com" <moosotc@gmail.com>,
Gabriel Scherer <gabriel.scherer@gmail.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Interface(.mli) location
Date: Tue, 9 Aug 2016 16:26:01 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9013504CA77@Remus.metastack.local> (raw)
In-Reply-To: <6718eb74-9b8a-f386-6e7b-e77217f39f95@users.sourceforge.net>
SF Markus Elfring wrote:
>
> > I think the use-case is too niche to justify breaking backwards
> > compatibility.
>
> Do you care for development challenges around parallel software builds?
>
> Would you like to consider other possibilities?
I don't follow you here, I'm afraid. My point was I think it better to add something new which fixes this, rather than risk breaking other things by changing existing behaviour.
> > That's potentially a very subtle way to break someone else's existing
> build system.
>
> How do you think about the application of an extra environment variable
> (or a command line parameter) which specifies the preferred directory for
> the storage of compiled interface descriptions?
What does that solve?
> > The existing behaviour is precisely documented in the manual
>
> I find that there is still room for interpretation.
What kind of room, though? The only ambiguity I can see is precisely how you handle references on the command line including directory names.
> > (even if it's not necessarily the best approach).
>
> Are you looking for corresponding software extensions?
Afraid I don't follow that.
David
next prev parent reply other threads:[~2016-08-09 16:26 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 [this message]
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
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=E51C5B015DBD1348A1D85763337FB6D9013504CA77@Remus.metastack.local \
--to=dra-news@metastack.com \
--cc=caml-list@inria.fr \
--cc=elfring@users.sourceforge.net \
--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).