From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: "Soegtrop, Michael" <michael.soegtrop@intel.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Ocamldoc ignores section header special comments
Date: Wed, 6 Jul 2016 10:29:14 +0100 [thread overview]
Message-ID: <87B62CFDFABA4A48AC1B29B4835DBD1E@erratique.ch> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A172CF1F269@IRSMSX102.ger.corp.intel.com>
Le mercredi, 6 juillet 2016 à 10:21, Soegtrop, Michael a écrit :
> Dear OCaml Users,
>
> I started to use ocamldoc (via ocamlbuild doc.docdir/index.html). It works as expected, just it ignores all section headers (they don’t appear in the generated HTML at all).
Which compiler version are you using ? There are various bugs in the 4.02.* line that make it unsuitable to generate documentation (directives are lost and/or stuttering documentation is generated). Use 4.01 or 4.03.
Best,
Daniel
next prev parent reply other threads:[~2016-07-06 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 9:21 Soegtrop, Michael
2016-07-06 9:29 ` Daniel Bünzli [this message]
2016-07-06 9:44 ` Soegtrop, Michael
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=87B62CFDFABA4A48AC1B29B4835DBD1E@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=michael.soegtrop@intel.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).