From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: Martin DeMello <martindemello@gmail.com>,
OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] Bos 0.1.0
Date: Mon, 23 May 2016 19:08:34 -0400 [thread overview]
Message-ID: <CAPFanBFRP=ndD_o-uUz7Tg3UaUyGA3URWJ9vtzhE1UGKJw7eNg@mail.gmail.com> (raw)
In-Reply-To: <EBC04A884CF3423EAE5B8D541E987587@erratique.ch>
There are some parts of the ocamlbuild internals that have their own
implementations of file path handling and quoting/escaping, and that
are a bit too arcane to my taste. (I tend to not change them because
they mostly work well, but they come back to bite us once in a while.)
When I got the announcement for Bos, I indeed thought that it could be
a nice idea to have a look. (I probably won't do it myself in the
short term, my development time is very constrained right now; plus
the fact that I cannot test on Windows myself makes me wary of
changing those parts of the codebase.)
On Mon, May 23, 2016 at 6:43 PM, Daniel Bünzli
<daniel.buenzli@erratique.ch> wrote:
> Le mardi, 24 mai 2016 à 00:17, Martin DeMello a écrit :
>> Do you think this would be a good route towards getting ocamlbuild working seamlessly on windows?
>
> Well bos does not do any kind of magic to work well on windows except avoiding what needs to be avoided, namely fork(2). Contrary to what it's name suggests the Unix library is not a bad OS abstraction layer and works quite well on windows; even more so with the work David Allsopp put into 4.03.
>
> At the moment, but it may change in the future, bos is only a more lighter and simpler way to work with the Unix library correctly. Unix programming can be tricky and quite verbose, e.g. to setup program pipelines. Also note that bos' simpler interface may be not be suitable for all programs, i.e. bos doesn't replace Unix.
>
> IIRC (Gabriel may want to comment) to get ocamlbuild working seamlessly on windows one needs to get rid of fork, a few pointless shellouts and make people stop use Sh command specs in their plugins. So I don't think bos necessarily helps here, using Unix conservatively in ocamlbuild should do.
>
> Best,
>
> Daniel
>
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2016-05-23 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 21:01 Daniel Bünzli
2016-05-23 22:17 ` Martin DeMello
2016-05-23 22:43 ` Daniel Bünzli
2016-05-23 23:08 ` Gabriel Scherer [this message]
2016-05-24 6:49 ` Adrien Nader
2016-05-24 12:57 ` SP
2016-05-24 13:14 ` Daniel Bünzli
2016-05-24 14:02 ` SP
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='CAPFanBFRP=ndD_o-uUz7Tg3UaUyGA3URWJ9vtzhE1UGKJw7eNg@mail.gmail.com' \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
--cc=martindemello@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).