From: John Skaller <skaller@ozemail.com.au>
To: caml-list@inria.fr
Subject: [Caml-list] ocaml doc
Date: Tue, 17 Jun 2003 21:28:46 +1000 [thread overview]
Message-ID: <3EEEFB6E.1050002@ozemail.com.au> (raw)
Ocamldoc didn't understand the following annotations:
type srcref =
string (** filename *) *
int (** line number, 1 origin *) *
int (** starting column, 1 origin *) *
int (** ending column, 1 origin *)
Anyone else think this might be useful?
It also won't label polymorphic variant components ..
type X = [
| `A (** an A *)
| `B (** a B *)
]
but from the guide examples the following is
supposed to work and does:
type weather =
| Rain of int (** The comment for construtor Rain *)
| Sun (** The comment for constructor Sun *)
-------------------------------------
Minor qibble: the html formatting of
function signatures isn't very sweet.
When one overflows, the new line starts
hard on the left margin (it should be indented).
Also, if there is going to be an overflow,
all the components at the top level should be
on a separate line like:
val f:
A ->
B ->
C ->
D
or perhaps
val f:
A
-> B (* comment .. *)
-> C (* comment .. *)
Another minor quibble: I tried to latex
the -latex output, and it couldn't find
the style file ocamldoc.sty. I had to copy
it manually to where I needed it. But the -html
generator copies the style.css file where its needed.
--
John Max Skaller, mailto:skaller@ozemail.com.au
snail:10/1 Toxteth Rd, Glebe, NSW 2037, Australia.
voice:61-2-9660-0850
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2003-06-17 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 11:28 John Skaller [this message]
2003-06-17 14:18 ` Maxence Guesdon
2003-06-25 15:13 ` 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=3EEEFB6E.1050002@ozemail.com.au \
--to=skaller@ozemail.com.au \
--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