From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 6A9857ED7A for ; Mon, 10 Sep 2012 14:55:39 +0200 (CEST) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of wojciech.meyer@googlemail.com) identity=pra; client-ip=209.85.217.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="wojciech.meyer@googlemail.com"; x-sender="wojciech.meyer@googlemail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of wojciech.meyer@googlemail.com designates 209.85.217.182 as permitted sender) identity=mailfrom; client-ip=209.85.217.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="wojciech.meyer@googlemail.com"; x-sender="wojciech.meyer@googlemail.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-lb0-f182.google.com) identity=helo; client-ip=209.85.217.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="wojciech.meyer@googlemail.com"; x-sender="postmaster@mail-lb0-f182.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AssBAOniTVDRVdm2m2dsb2JhbABFuzoIIgEBAQEBCAkLCRQngiABAQEDARICLAEBNwEECwsLAzgiEgEFARwGGxqHWwEDCQacSQkDimaEMAEFhF8KQA2JTQaRSZVgjj8+hAc X-IronPort-AV: E=Sophos;i="4.80,398,1344204000"; d="scan'208";a="172524264" Received: from mail-lb0-f182.google.com ([209.85.217.182]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 10 Sep 2012 14:55:39 +0200 Received: by lbbgg13 with SMTP id gg13so1950071lbb.27 for ; Mon, 10 Sep 2012 05:55:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BmEh6J2GhH8rZGjASoR3oUFPMs3LLk9BSnAAPDnExFM=; b=UN8P3A+jqcyV5RGof1TlD1mnBfJckJUg2MIiGsx9ufZhyTmKGRKzULUVdPnMrihFu/ fuwIZYSh/frqHgOIwEStrC4gsRv57Rp11EQyMp3NW9Qy/6PCJud+ZwqHj1XkNFBfzhWW wLV++Ywqyhyrk81QuZqGUnSfhmaVtBxnSAekIh67tV7JtYBpxs86g9xJduC6CsTfeeQR fY60M4IAxaP5eLgshFjWrcuukvyNqDLyYCimS5dODLPYuHGgEs/U9/EXBoqhY16xemZF openpQOrABpZqOCh3FtEHTbm8dVFTWBR4S5SF/Fwkq1TL336+ykaHZYUTw0r85+furYc HiuQ== MIME-Version: 1.0 Received: by 10.112.82.33 with SMTP id f1mr4978449lby.35.1347281738401; Mon, 10 Sep 2012 05:55:38 -0700 (PDT) Received: by 10.114.28.68 with HTTP; Mon, 10 Sep 2012 05:55:38 -0700 (PDT) In-Reply-To: <504DD828.3000208@gmail.com> References: <504DD828.3000208@gmail.com> Date: Mon, 10 Sep 2012 13:55:38 +0100 Message-ID: From: Wojciech Meyer To: Hongbo Zhang Cc: Gabriel Scherer , Anil Madhavapeddy , caml users Content-Type: text/plain; charset=ISO-8859-1 Subject: [Caml-list] Re: working %.pp.ml target with ocamfind/ocamlbuild > Yes, it's damn useful not only for bootstrapping, but also for > developing to locate type errors. But there's something wrong with > Camlp4's printer, it has *4* printers in total, writing a printer for an > Ast which has no backend is totally useless. In my branch of camlp4, *I > removed all those 4 printers and using tools/pprintast.ml* in ocaml's > compiler source tree(with some my own bug fixes), and it works very > well. Yes, typing errors are also hard to track in the default Camlp4 "stealth mode". I generally think it works well, apart from the corner cases which will always occur during development where you really need full excerpt of the generated code. > Btw, are you in ICFP? we could have a talk about Camlp4 :-) Not on ICFP but on OUD only.. but yeah, we could talk about Camlp4, I think OCaml meta programming tools deserve much more attention in general. - Wojciech