From: Kristopher Micinski <krismicinski@gmail.com>
To: "Raphaël Proust" <raphlalou@gmail.com>
Cc: David Allsopp <dra-news@metastack.com>, OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Anonymous sum types in functors
Date: Mon, 24 Jun 2013 15:13:55 -0400 [thread overview]
Message-ID: <CAF1Sy-Hnf+hpu+f9t8fJ05xgOgTU8V3dfVBNTo-XHKkP83trjg@mail.gmail.com> (raw)
In-Reply-To: <CAAmHUAn5AbkrMfYH0nvzc-FtF5X=Dfr58+K=HEz6AYFV-0OC4A@mail.gmail.com>
Great, I googled for this, but didn't turn up anything: it seems
sensible this would exist.
Kris
On Mon, Jun 24, 2013 at 10:41 AM, Raphaël Proust <raphlalou@gmail.com> wrote:
> On Mon, Jun 24, 2013 at 3:37 PM, Kristopher Micinski
> <krismicinski@gmail.com> wrote:
>>>
>>> The "reason" for wanting to avoid that in this instance is the specific application - the sets are actually bit masks and there are about 50 of them (using a code generator, unsurprisingly). Given that the ocamldoc output is already going to be interesting, I was trying to avoid having 100 modules if possible :o)
>>
>> This honestly sounds like something that you should be able to avoid
>> in OCamlDoc. It seems sensible you should be able to mark things as
>> "don't generate documentation for these", but I havent' seen such.
>
> From: http://caml.inria.fr/pub/docs/manual-ocaml/manual029.html#toc120
>
> The special comment (**/**) tells OCamldoc to discard elements placed
> after this comment, up to the end of the current class, class type,
> module or module type, or up to the next stop comment.
>
>
> Cheers,
> --
> ______________
> Raphaël Proust
next prev parent reply other threads:[~2013-06-24 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-23 7:16 David Allsopp
2013-06-23 15:14 ` Xavier Leroy
2013-06-23 23:15 ` Jacques Garrigue
2013-06-24 9:39 ` David Allsopp
2013-06-24 14:37 ` Kristopher Micinski
2013-06-24 14:41 ` Raphaël Proust
2013-06-24 19:13 ` Kristopher Micinski [this message]
2013-06-25 8:39 ` David Allsopp
[not found] <563607038852382852@orange.fr>
2013-06-23 9:48 ` David Allsopp
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=CAF1Sy-Hnf+hpu+f9t8fJ05xgOgTU8V3dfVBNTo-XHKkP83trjg@mail.gmail.com \
--to=krismicinski@gmail.com \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.com \
--cc=raphlalou@gmail.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