caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Teller <David.Teller@univ-orleans.fr>
To: Julien Signoles <Julien.Signoles@lri.fr>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Documenting submodules ?
Date: Mon, 05 May 2008 10:22:50 +0200	[thread overview]
Message-ID: <1209975770.6431.5.camel@Blefuscu> (raw)
In-Reply-To: <Pine.LNX.4.63.0805051008080.16412@serveur9-10.lri.fr>

Let me rephrase:

Case 1)

==== sub.ml
(** This is [Sub] *)

type t
 (** This is [Sub.t]*)

==== main.ml
module Sub = Sub

Running ocamldoc drops the comments of sub.ml .

Case 2)

==== sub.ml
module SubSub = struct
  type t
  (** This is [SubSub.t] *)
end

==== main.ml
module SubSubSub = Sub.SubSub


Running ocamlc drops the comments of sub.ml -- and the very existence of
SubSub.t.

Cheers,
 David

On Mon, 2008-05-05 at 10:11 +0200, Julien Signoles wrote:
> > When invoking ocamldoc, either directly or through ocamlbuild + .odocl,
> > the generated documentation only contains the name of modules, without
> > any of the comments or even the values.
> 
> Usually ocamldoc works fine with submodule:
> 
> ===== sub.ml
> (** This is {!A}. It contains a properly-documented submodule {!A.B} and a
>      single value {!A.a}. *)
> module A = struct
> 
>    (** This is {!B}. It contains a single value {!B.b}. *)
>    module B = struct let b = 1 end
> 
>    let a = 0
> 
> end
> =====
> 
> $ ocamldoc -version
> Ocamldoc 3.10.1
> $ ocamldoc -html sub.ml
> 
> Hope this helps,
> Julien Signoles
> 
-- 
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. 


  reply	other threads:[~2008-05-05  8:21 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 [this message]
2008-05-05  8:35     ` Maxence Guesdon
2008-05-05  9:12       ` David Teller
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=1209975770.6431.5.camel@Blefuscu \
    --to=david.teller@univ-orleans.fr \
    --cc=Julien.Signoles@lri.fr \
    --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;
as well as URLs for NNTP newsgroup(s).