From: David Teller <David.Teller@univ-orleans.fr>
To: Maxence Guesdon <maxence.guesdon@inria.fr>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Documenting submodules ?
Date: Mon, 05 May 2008 11:12:05 +0200 [thread overview]
Message-ID: <1209978725.6431.18.camel@Blefuscu> (raw)
In-Reply-To: <20080505103513.6f48d8fc@alcazar.inria.fr>
On Mon, 2008-05-05 at 10:35 +0200, Maxence Guesdon wrote:
> Indeed, ocamldoc does not use the comment of sub.ml in the page generated
> for main.ml. This is normal behaviour.
I'm aware that it's the normal behaviour of ocamldoc. I'm just looking
for a work-around or a plug-in.
> You could comment the creation of the
> Sub module (i.e. Main.Sub) by putting a comment around
> module Sub = Sub
I wrote that in my first post :)
More seriously, it's ok if I have only one or two modules. But if I want
to comment both the creation of Sub and the actual contents of Sub, it's
not really a good method. Even more so since I have 70+ modules
developed separately, which I attempt to present with a consistent
Java-style package hierarchy. That would mean copying and pasting about
9000+ lines of code for the moment, with more coming, and nasty bugs
lurking whenever the source packages are updated.
> This is normal behaviour too. You're redefining a module here, and the
> way it is defined is reflected by the html code generated by ocamldoc, with
> a link on the Sub.SubSub page.
I have a link to an empty Sub.SubSub page. Is that normal behaviour ?
Cheers,
David
--
David Teller
Security of Distributed Systems
http://www.univ-orleans.fr/lifo/Members/David.Teller
Angry researcher: French Universities need reforms, but the LRU act brings liquidations.
next prev parent reply other threads:[~2008-05-05 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 22:17 David Teller
2008-05-01 19:51 ` [Caml-list] " Arnaud Spiwack
2008-05-05 8:11 ` Julien Signoles
2008-05-05 8:22 ` David Teller
2008-05-05 8:35 ` Maxence Guesdon
2008-05-05 9:12 ` David Teller [this message]
2008-05-05 9:48 ` Maxence Guesdon
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=1209978725.6431.18.camel@Blefuscu \
--to=david.teller@univ-orleans.fr \
--cc=caml-list@yquem.inria.fr \
--cc=maxence.guesdon@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