From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id EFD0D7EE4B for ; Tue, 8 Oct 2013 19:29:33 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of agarwal1975@gmail.com) identity=pra; client-ip=209.85.223.180; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="agarwal1975@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of agarwal1975@gmail.com designates 209.85.223.180 as permitted sender) identity=mailfrom; client-ip=209.85.223.180; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="agarwal1975@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-ie0-f180.google.com) identity=helo; client-ip=209.85.223.180; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="postmaster@mail-ie0-f180.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmQCAEhAVFLRVd+0lGdsb2JhbABZgz9SuGCIQ4EaCBYOAQEBAQcLCwkSKoIlAQEEAUABGx0BAwELBgUEBw0uIQEBEQEFARwGExSHXwEDCQYMnCyMU4MKhBoKGScNZIkBAQUMgk+JfIJrB4QjA5YYgWmBL4sbAoNJGCmDEIFaIA X-IPAS-Result: AmQCAEhAVFLRVd+0lGdsb2JhbABZgz9SuGCIQ4EaCBYOAQEBAQcLCwkSKoIlAQEEAUABGx0BAwELBgUEBw0uIQEBEQEFARwGExSHXwEDCQYMnCyMU4MKhBoKGScNZIkBAQUMgk+JfIJrB4QjA5YYgWmBL4sbAoNJGCmDEIFaIA X-IronPort-AV: E=Sophos;i="4.90,1057,1371074400"; d="scan'208";a="29560322" Received: from mail-ie0-f180.google.com ([209.85.223.180]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 08 Oct 2013 19:29:33 +0200 Received: by mail-ie0-f180.google.com with SMTP id u16so20354222iet.11 for ; Tue, 08 Oct 2013 10:29:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=9MVwTjkjy64aLwED60lWxKFTf2YwyzvYp3Lz0PPkkkA=; b=rOGxk3oPPtxDHQmILyFqxiTsCZ2STTExr6PX+VIO2Usp3DitJkoox/yQvIa2/pSpSh X8nM9GOsXTT2GZ/vIZsbvpOa3T5/hhsrt89FSKS8JNqDXQB/buTSust+EFZ70cwVefpO CAXHWqYwK6GGNg3G0li5+Sb3IHQY2l4xcDCYPnPjgQh/Ia+gAptZWtLgFsyvNgTjQ2j/ AUpoTNba4g1hZVf2dO7RKWBSsmEYUjRPUWPiWN/kXctCRMbfs6iReReGhGpcLaf05IZp FjJPUjomarrhiqmhFfNaCatK5kMZxnMkRmRkNvIN1JiI1bpv57g7f3NHNxOPRF18tOAG UKlA== X-Received: by 10.50.61.205 with SMTP id s13mr2195421igr.29.1381253371902; Tue, 08 Oct 2013 10:29:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.72.230 with HTTP; Tue, 8 Oct 2013 10:29:11 -0700 (PDT) In-Reply-To: <52543A03.7080308@gmail.com> References: <52541870.7040000@gmail.com> <52543A03.7080308@gmail.com> From: Ashish Agarwal Date: Tue, 8 Oct 2013 13:29:11 -0400 Message-ID: To: Matej Kosik <5764c029b688c1c0d24a2e97cd764f@gmail.com> Cc: "caml-list@inria.fr" Content-Type: multipart/alternative; boundary=047d7bd7679a940e5004e83e1c66 Subject: Re: [Caml-list] ocamldoc ... "Warning: Module or module type BatSet.StringSet not found" --047d7bd7679a940e5004e83e1c66 Content-Type: text/plain; charset=ISO-8859-1 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/ > --047d7bd7679a940e5004e83e1c66 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
The User's Manual discusses items that are part of the= "official" OCaml distribution from Inria. OCamldoc has long serv= ed the community and continues to be widely used. On the other hand, the co= mmunity has recently initiated quite a few projects to improve many things,= a documentation tool being one of them. Over time, you're probably rig= ht that some topics in the User's Manual should defer to other resource= s like ocaml.org (which is itself being en= hanced in many ways).



On Tue, Oct 8, 2013 at 12:59 PM, Matej Kosik <57= 64c029b688c1c0d24a2e97cd764f@gmail.com> wrote:
On 08/10/13 16:24, Ashish = Agarwal wrote:
> OCamldoc has trouble finding references to modules in some cases. I wo= uldn't worry about it. See the opam-doc project [1], which aims to prov= ide a more robust documentation tool.
>
> [1] http://www.cl.cam.ac.uk/projects/ocamllabs/= tasks/platform.html#OPAM Doc

I wonder, why is ocamldoc mentioned in the User's Manual [2] if p= eople, 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/

--047d7bd7679a940e5004e83e1c66--