From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Dario Teixeira <darioteixeira@yahoo.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Forced linking and Ocamlbuild
Date: Mon, 5 Apr 2010 17:41:49 +0200 [thread overview]
Message-ID: <w2r91a3da521004050841q61f57327vc1c6b0030e5f3201@mail.gmail.com> (raw)
In-Reply-To: <892901.19224.qm@web111502.mail.gq1.yahoo.com>
> (I realise there's always the option of adding a
> dummy reference, but I'm looking for a cleaner solution).
Is it really "unclean" ?
Suppose you'd like to use ocamldoc to output a dot file to understand
the dependencies of your program, if you manage to achieve what you
want to do you'll miss that dependency.
The more info there is in the source (vs. the build procedure) the
easier it is to understand the program.
Best,
Daniel
next prev parent reply other threads:[~2010-04-05 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 15:08 Dario Teixeira
2010-04-05 15:41 ` Daniel Bünzli [this message]
2010-04-05 16:02 ` [Caml-list] " Dario Teixeira
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=w2r91a3da521004050841q61f57327vc1c6b0030e5f3201@mail.gmail.com \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@yquem.inria.fr \
--cc=darioteixeira@yahoo.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).