From: Dario Teixeira <dario.teixeira@nleyten.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Forcing OCamlbuild to compile a file before another
Date: Fri, 06 Feb 2015 18:58:32 +0000 [thread overview]
Message-ID: <9c4bb489982617ebcfb513a3c6507e52@nleyten.com> (raw)
In-Reply-To: <CAPFanBG7Ny84Czgedo-57iF6jfehvM+EYNo1f6TmS+a6cY-UuA@mail.gmail.com>
Hi,
> I don't expect touching OCamldep to be very difficult. I'd be glad to
> offer the time to provide a patch for the -paths option; ocamldep is a
> small codebase and I don't expect much reluctance from the maintainers
> to add a new feature (the code should be simple, and not affect
> existing behaviors). That may require that you wait for the next
> release in a few months; if you really needed to, you can probably
> hack a simple external tool with the same feature today using the
> compiler-libs.
Thanks Gabriel: your work would be much appreciated, and I would be glad
to test it both in dummy examples and in a real library (namely
Lambdoc).
As for the timing, it won't be a problem for me to wait for 4.03 before
making a 1.0-final release of Lambdoc, particularly if the compiler team
sticks to the recent pattern of gifting the community with a summer
release.
Moreover, it wouldn't surprise me if some more edge cases are found in
the
meantime...
Best regards,
Dario Teixeira
next prev parent reply other threads:[~2015-02-06 18:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 15:08 Dario Teixeira
2015-01-23 16:41 ` Francois Pottier
2015-01-23 19:09 ` Dario Teixeira
2015-01-24 12:56 ` Gabriel Scherer
2015-01-25 18:16 ` Dario Teixeira
2015-01-26 12:30 ` Dario Teixeira
2015-02-03 21:13 ` Gabriel Scherer
2015-02-04 13:18 ` Dario Teixeira
2015-02-04 14:52 ` Gabriel Scherer
2015-02-04 16:15 ` Dario Teixeira
2015-02-04 16:44 ` Gabriel Scherer
2015-02-06 17:01 ` Dario Teixeira
2015-02-06 17:05 ` Gabriel Scherer
2015-02-06 18:58 ` Dario Teixeira [this message]
2015-02-15 10:41 ` Gabriel Scherer
2015-02-15 13:55 ` Dario Teixeira
2015-02-15 14:42 ` Gabriel Scherer
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=9c4bb489982617ebcfb513a3c6507e52@nleyten.com \
--to=dario.teixeira@nleyten.com \
--cc=caml-list@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