From: Ashish Agarwal <agarwal1975@gmail.com>
To: Matej Kosik <5764c029b688c1c0d24a2e97cd764f@gmail.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamldoc ... "Warning: Module or module type BatSet.StringSet not found"
Date: Tue, 8 Oct 2013 13:29:11 -0400 [thread overview]
Message-ID: <CAMu2m2Knj9HuTrvXZc6k2Si_V3dadxZwEYYSwhzd+gYfxNzG-Q@mail.gmail.com> (raw)
In-Reply-To: <52543A03.7080308@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
The User's Manual discusses items that are part of the "official" OCaml
distribution from Inria. OCamldoc has long served the community and
continues to be widely used. On the other hand, the community has recently
initiated quite a few projects to improve many things, a documentation tool
being one of them. Over time, you're probably right that some topics in the
User's Manual should defer to other resources like ocaml.org (which is
itself being enhanced in many ways).
On Tue, Oct 8, 2013 at 12:59 PM, Matej Kosik <
5764c029b688c1c0d24a2e97cd764f@gmail.com> wrote:
> On 08/10/13 16:24, Ashish Agarwal wrote:
> > OCamldoc has trouble finding references to modules in some cases. I
> wouldn't worry about it. See the opam-doc project [1], which aims to
> provide a more robust documentation tool.
> >
> > [1] http://www.cl.cam.ac.uk/projects/ocamllabs/tasks/platform.html#OPAMDoc
>
> I wonder, why is ocamldoc mentioned in the User's Manual [2] if people, as
> you suggest, are not supposed to be worried about it and, on the other
> hand, there is no trace of OPAM therein.
>
> A puzzle.
>
> [2] http://caml.inria.fr/pub/docs/manual-ocaml/
>
[-- Attachment #2: Type: text/html, Size: 1778 bytes --]
next prev parent reply other threads:[~2013-10-08 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 14:36 Matej Kosik
2013-10-08 15:24 ` Ashish Agarwal
2013-10-08 16:59 ` Matej Kosik
2013-10-08 17:29 ` Ashish Agarwal [this message]
2013-10-08 17:44 ` 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=CAMu2m2Knj9HuTrvXZc6k2Si_V3dadxZwEYYSwhzd+gYfxNzG-Q@mail.gmail.com \
--to=agarwal1975@gmail.com \
--cc=5764c029b688c1c0d24a2e97cd764f@gmail.com \
--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).