From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] ocamlbuild & deps
Date: Sat, 21 Feb 2009 21:19:52 +0100 [thread overview]
Message-ID: <231BADDB-F88E-4A3D-994B-863579C20810@erratique.ch> (raw)
In-Reply-To: <49A04DAE.6010109@lri.fr>
Le 21 févr. 09 à 19:53, Romain Bardou a écrit :
> Ok I think I did not explain correctly. Let's say that :
[...]
I think you are not getting my point. What I meant in the first place
is that I see strictly no difference between :
> rule ~deps ~prod r
and
> rule ~prod begin fun env build ->
> let static_deps = build (List.map (fun d -> env d) deps) in
> List.iter Outcome.ignore_good static_deps;
> r env build
> end
Strictly speaking this means that all dependencies can be resolved by
the 'build' argument. However it is sometimes useful to introduce a
partial order among them. Now your distinction dynamic/static is just
a limited way of specifiying a partial order among dependencies. The
generalized way of introducing that order is just to have calls to the
'build' argument in the order you want inside your rule.
If the above is true then I think it would be usefull to mention this
in the documentation about the 'build' argument.
Best,
Daniel
next prev parent reply other threads:[~2009-02-21 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 14:01 Daniel Bünzli
2009-02-20 15:39 ` [Caml-list] " Romain Bardou
2009-02-20 16:31 ` Daniel Bünzli
2009-02-21 18:53 ` Romain Bardou
2009-02-21 20:19 ` Daniel Bünzli [this message]
2009-02-21 20:23 ` Daniel Bünzli
2009-02-26 13:04 ` Daniel Bünzli
2009-03-02 13:43 ` Daniel Bünzli
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=231BADDB-F88E-4A3D-994B-863579C20810@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@yquem.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).