From: David Teller <David.Teller@univ-orleans.fr>
To: Caml <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Two questions on OCamlDoc
Date: Fri, 05 Sep 2008 12:25:03 +0200 [thread overview]
Message-ID: <1220610303.8100.16.camel@Blefuscu> (raw)
In-Reply-To: <1220356028.6406.33.camel@Blefuscu>
Okay, I've found the solution to most of my problems, thanks to Maxence.
The code will be committed soon to the Batteries repository if anyone is
interested.
I have one more question, though: assuming that I have a reference to a
[t_module] for a module with both a [.mli] and a [.ml], is there a
simple way to access the underlying implementation without having to
reparse [m_code]?
Thanks,
David
On Tue, 2008-09-02 at 13:47 +0200, David Teller wrote:
> Hi everyone,
>
> I'm currently toying with OCamlDoc, with very little success. I'm
> attempting to do two things:
> * getting OCamlDoc to understand that some modules (which I can modify)
> contain the documentation for some other modules (which I can't) replace
> some modules with others
> * inlining the documentation for modules in modules which import those.
--
David Teller-Rajchenbach
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-09-05 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 11:47 David Teller
2008-09-02 12:05 ` [Caml-list] " David Teller
2008-09-02 12:48 ` Another question on OcamlDoc Jan Kybic
2008-09-02 17:19 ` [Caml-list] " David Teller
2008-09-03 6:48 ` Maxence Guesdon
2008-09-15 13:09 ` Jan Kybic
2008-09-02 13:37 ` [Caml-list] Two questions on OCamlDoc Maxence Guesdon
2008-09-02 13:12 ` Maxence Guesdon
2008-09-05 10:25 ` David Teller [this message]
2008-09-05 12:03 ` Maxence Guesdon
2008-09-05 12:33 ` David Teller
2008-09-05 12:37 ` Maxence Guesdon
2008-09-05 12:42 ` David Teller
2008-09-05 12:58 ` 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=1220610303.8100.16.camel@Blefuscu \
--to=david.teller@univ-orleans.fr \
--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