From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: Dario Teixeira <darioteixeira@yahoo.com>
Cc: Caml_mailing list <caml-list@yquem.inria.fr>,
romain.bardou <romain.bardou@lri.fr>
Subject: Re: [Caml-list] File inclusion with Ocamldoc
Date: Wed, 15 Oct 2008 17:05:50 +0200 [thread overview]
Message-ID: <1224083082-sup-3321@ausone.inria.fr> (raw)
In-Reply-To: <372513.57372.qm@web54601.mail.re2.yahoo.com>
Excerpts from Dario Teixeira's message of Wed Oct 15 16:43:32 +0200 2008:
> Hi,
>
> > It works for me with the 3.10.1. I just tried to write a
> > file test.ml, and a file truc.odocl with "Test" in it, and then
> > ran ocamlbuild :
> > ocamlbuild truc.docdic/index.html
> > And it worked. Or maybe I didn't understand what you want?
>
> You're right. I took the Ocamlbuild manual at face value, since
> it states it cannot handle implementation files. Nevertheless,
> I'm still running into some problems with Ocamlbuild+Ocamldoc.
> First, while Ocamldoc will by default merge the comments from .ml
> and .mli files (with precedence given to the .mli file, unless
> -inv-merge-ml-mli is given), when I use Ocamlbuild to generate
> the documentation I notice the following pattern: if only the .ml
> file is present then it's used for generating the documentation;
> If, however, both .ml and .mli are present, then only the .mli
> is taken into account (no merging is done). Second, how does one
> tell Ocamlbuild to include .txt files in the documentation?
The manual states that implementation files are not handled because if you
have a .ml and .mli then ocamlbuild will choose the .mli.
--
Nicolas Pouillard aka Ertai
next prev parent reply other threads:[~2008-10-15 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 13:51 Dario Teixeira
2008-10-14 17:22 ` [Caml-list] " Maxence Guesdon
2008-10-14 19:17 ` Dario Teixeira
2008-10-15 8:55 ` Romain Bardou
2008-10-15 14:43 ` Dario Teixeira
2008-10-15 15:05 ` Nicolas Pouillard [this message]
2008-10-16 15:27 ` 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=1224083082-sup-3321@ausone.inria.fr \
--to=nicolas.pouillard@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=darioteixeira@yahoo.com \
--cc=romain.bardou@lri.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