caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Guillaume Yziquel <guillaume.yziquel@citycable.ch>
To: Pietro Abate <Pietro.Abate@pps.jussieu.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ocamlbuild, ocamldoc and module packs
Date: Sat, 12 Nov 2011 09:35:14 +0100	[thread overview]
Message-ID: <20111112083513.GS10557@localhost> (raw)
In-Reply-To: <20111111130847.GA10832@pps.jussieu.fr>

Le Friday 11 Nov 2011 à 14:08:47 (+0100), Pietro Abate a écrit :
> Hello.
> 
> As far as I know ocamldoc doesn't play very well with -pack. There is 
> a very old bug on mantis about this.
> 
> I'm in a situation that is worst then yours where I use pack to hide
> modules with the same name as in ModuleOne/A and ModuleTwo/A and
> ocamldoc refuses altogether to generate doc for both modules.  I've not
> found a solution neither for my problem, or more in general for the one
> you describe below.

Well, I'm having the same issue, as ModuleOne and ModuleTwo satisfy a
signature implying a common module.

> I think the good ppl that put Batteries together had similar issues.
> 
> If you look at the Batteries source there is a lot of code aimed at
> solving this problem by effectively creating new source files that can
> be properly digested by ocamldoc. For what I gathered is pretty specific
> to their case, but probably you can use it as an example to write an
> appropriate ocamldoc plugin.

I guess workarounds or ugly hacks are way too overkill for my current
purpose.

> Maybe the recent release of Argot by XC solves some of these problem
> (just a wild guess, I didn't look at it very carefully).

I'll have a try at Argot as soon as the current situation gets too
frustrating.

> Hope this helps.

Thanks.

> p

-- 
     Guillaume Yziquel


      reply	other threads:[~2011-11-12  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-10 20:52 Guillaume Yziquel
2011-11-11 13:08 ` Pietro Abate
2011-11-12  8:35   ` Guillaume Yziquel [this message]

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=20111112083513.GS10557@localhost \
    --to=guillaume.yziquel@citycable.ch \
    --cc=Pietro.Abate@pps.jussieu.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).