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 mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by sympa.inria.fr (Postfix) with ESMTPS id BEE567ED5C for ; Tue, 31 Jul 2012 00:08:38 +0200 (CEST) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of gabriel.scherer@gmail.com) identity=pra; client-ip=209.85.213.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="gabriel.scherer@gmail.com"; x-sender="gabriel.scherer@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of gabriel.scherer@gmail.com designates 209.85.213.182 as permitted sender) identity=mailfrom; client-ip=209.85.213.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="gabriel.scherer@gmail.com"; x-sender="gabriel.scherer@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-yx0-f182.google.com) identity=helo; client-ip=209.85.213.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="gabriel.scherer@gmail.com"; x-sender="postmaster@mail-yx0-f182.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuUCAG0EF1DRVdW2k2dsb2JhbABFFqgykQkIIgEBAQEJCQsJFAQjgiABAQEWAiwBGxILAQMSEAMKDUIBAREBBQEKGBMSEIdbAQMMC5wuCQOMI4JxhSYKGScDCleIcQEFDIpcaIcJA4hNiyiBVIEUiXaDJj6EHg X-IronPort-AV: E=Sophos;i="4.77,681,1336341600"; d="scan'208";a="168601752" Received: from mail-yx0-f182.google.com ([209.85.213.182]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 31 Jul 2012 00:08:38 +0200 Received: by yenl8 with SMTP id l8so7937257yen.27 for ; Mon, 30 Jul 2012 15:08:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=ICnmSiTssvTrsF5rMOIqEU2SZhVaFetR5TqCvpO2DiY=; b=Fti42zmG1tmJohz7h1W9hvFqMhRNIAfv1fsUGB75R8Dwf1cIiRzxJh+0p6l44wNtpI WH1sUfl2S5916sLdC4JU8QVrqDjdcRyvoTeVlH3lLhIN7EotS0WElxrMIjQiq0uCjsky RT4L1Fyt2/eqMq8bAlJ5vdm1OdZ5qExVC9lBjZsd+Gi8Ed6Zd4HIasKs/byZRZlx0+QA bsFO8eGKZ4P3WSz3aZEMJFt1623YEKQsvPJQ+nE2D/mx5L/CYgy2//lBTe8EahkFGqs0 WquW1gS3q90pVvSQxFkAp+TRZfbgGrm/ns6iZHD+Suz7D2Rk/vyJJb25aud6utmRf322 GJhQ== Received: by 10.50.217.137 with SMTP id oy9mr111766igc.56.1343686116733; Mon, 30 Jul 2012 15:08:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.94.39 with HTTP; Mon, 30 Jul 2012 15:07:56 -0700 (PDT) From: Gabriel Scherer Date: Mon, 30 Jul 2012 15:07:56 -0700 Message-ID: To: Hongbo Zhang Cc: caml-list@inria.fr Content-Type: text/plain; charset=ISO-8859-1 Subject: [Caml-list] Beware of compiler internals (Was: ocamldoc for ocaml's compiler?) Dear list, The new 4.00 release has added fairly interesting feature relying on the compiler internals: the new -bin-annot option allowing to export and manipulate the typedtree of an OCaml program has already stirred interest among tools writers (see Jun Furuse's OCamlspotter changes, or the questions of Hongbo Zhang). I just wanted to remark that the interface those tools expose are *not* stabilized and will *certainly* change before the next OCaml release: this code is very young, not reliable (don't expect all features to work as advertized), and flaws will certainly be discovered and fixed. To my knowledge, there is no compatibility guarantee coming from the compiler writers. Please keep that in mind when experimenting with those features: they are experimental, and if you decide to rely on them everyone will be interested in your feedback, but you're on your own and you should expect maintenance work (or even feature loss) during the next few releases. Regards -- from San Francisco. On Thu, Jul 26, 2012 at 4:15 AM, Hongbo Zhang wrote: > On 7/25/12 11:13 PM, Hongbo Zhang wrote: >> >> On 7/25/12 7:12 PM, Hongbo Zhang wrote: >>> >>> Hi List, >>> Did anyone have a try to build ocamldoc's documentation for ocaml's >>> compiler? >>> Many Thanks >>> >> Hi, I managed to build documentation for ocaml compiler. Another problem >> comes that ocamldoc prefers .mli to .ml which renders -keep-code not >> useful. >> Any ideas? >> Once I finished, if people interested, I would be happy to share. >> Thanks >> >> > Hi, > I put it here > http://www.seas.upenn.edu/~hongboz/hongbo_zhang_files/typing.docdir/index.html > > > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa-roc.inria.fr/wws/info/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs >