From: "Ian Zimmerman" <nobrowser@gmail.com>
To: "Philippe Wang" <lists@philippewang.info>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] annotating nested modules with ocamldoc
Date: Sat, 6 Jan 2007 10:57:15 -0500 [thread overview]
Message-ID: <17af13780701060757h55ce4f3ai2b1bd3524c723272@mail.gmail.com> (raw)
In-Reply-To: <065D28A1-37A8-4AC4-B2D0-EA3D5185A596@philippewang.info>
On 1/6/07, Philippe Wang <lists@philippewang.info> wrote:
> I suggest you to use The Stop special comment (**/**) in the .ml file.
>
> (ocaml reference manual, section 15.2.2 )
I know about that mechanism, it doesn't help in this situation. Note
that the definition of boo uses internal_goo, so internal_goo must
come before module Boo in the source file. Where would I put the stop
comment to achieve what I want?
next prev parent reply other threads:[~2007-01-06 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 15:22 Ian Zimmerman
2007-01-06 15:37 ` [Caml-list] " Philippe Wang
2007-01-06 15:57 ` Ian Zimmerman [this message]
2007-01-06 16:07 ` Philippe Wang
2007-01-06 16:12 ` Daniel Bünzli
2007-01-06 16:38 ` Ian Zimmerman
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=17af13780701060757h55ce4f3ai2b1bd3524c723272@mail.gmail.com \
--to=nobrowser@gmail.com \
--cc=caml-list@inria.fr \
--cc=lists@philippewang.info \
/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