From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <yallop@gmail.com>
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 3493C7ED7A
	for <caml-list@sympa.inria.fr>; Tue,  2 Oct 2012 00:39:33 +0200 (CEST)
Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  yallop@gmail.com) identity=pra; client-ip=74.125.82.52;
  receiver=mail1-smtp-roc.national.inria.fr;
  envelope-from="yallop@gmail.com";
  x-sender="yallop@gmail.com"; x-conformance=sidf_compatible
Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of
  yallop@gmail.com designates 74.125.82.52 as permitted sender)
  identity=mailfrom; client-ip=74.125.82.52;
  receiver=mail1-smtp-roc.national.inria.fr;
  envelope-from="yallop@gmail.com";
  x-sender="yallop@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-wg0-f52.google.com) identity=helo;
  client-ip=74.125.82.52;
  receiver=mail1-smtp-roc.national.inria.fr;
  envelope-from="yallop@gmail.com";
  x-sender="postmaster@mail-wg0-f52.google.com";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArMBAC8balBKfVI0jWdsb2JhbAArGoYLuDQIIwEBAQEJCQsJEgYjgiABAQEEEgIPHQEbHQEDDAYFCw0CAiYCAiEBAREBBQEcBhMih1ABAw8LLJonCQOLVk+CdYUqChknDVmIdQEFDIEViRxig3KBR4ESA5QUgVWBFYoLgywWKYN6Dg
X-IronPort-AV: E=Sophos;i="4.80,519,1344204000"; 
   d="scan'208";a="175351162"
Received: from mail-wg0-f52.google.com ([74.125.82.52])
  by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 02 Oct 2012 00:39:32 +0200
Received: by wgbfg15 with SMTP id fg15so4050260wgb.9
        for <caml-list@inria.fr>; Mon, 01 Oct 2012 15:39: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:date:message-id:subject:from:to
         :cc:content-type;
        bh=kMmKww5fE3V531b4icK6642HSkN62eYmXY4CoNbdfIk=;
        b=TUDrnIt4CDQ6htHAKGIsr9qWsx5NsEq9ZaNO6LO+lfsRrJ9k7k38BbAUu6Cwxa71AB
         9Vj8/qTNQy05zciYcQ3qnRUIJef385j7zmiNegOT4/Sm4cggH3Yl5YvHsPDCzucgKicf
         vme9haikYzd7k1Ucgevdk8jEgl8lEIr36BN0PtEhu0GBUirBiMNGGavjE0HaWjvu5DFD
         1GqgFf7LP+sma62tBJIxI3WBLEelNyrEdeniPFHnWdZcS0T+mZ/niqn2xPxLVXNcKJ1Q
         qbF35Fw+1Fl5l8Om+4nq96Kl6v5VqKJT/i4DlcPvPgJhS2yGv8njqhZoO3g+fNxM1h6g
         szCA==
MIME-Version: 1.0
Received: by 10.180.93.106 with SMTP id ct10mr17528956wib.8.1349131172639;
 Mon, 01 Oct 2012 15:39:32 -0700 (PDT)
Received: by 10.194.34.229 with HTTP; Mon, 1 Oct 2012 15:39:32 -0700 (PDT)
In-Reply-To: <CAOOOohSsXgVk8YZOk4QkxNw4H9cBvM+enSkPYOdjB==Yrykwrg@mail.gmail.com>
References: <CAOOOohSsXgVk8YZOk4QkxNw4H9cBvM+enSkPYOdjB==Yrykwrg@mail.gmail.com>
Date: Mon, 1 Oct 2012 23:39:32 +0100
Message-ID: <CAAxsn=FaQ5toyuLB4Y2=uc3aZV05KtgOmxS7jdxGfi9SYUNniA@mail.gmail.com>
From: Jeremy Yallop <yallop@gmail.com>
To: Philippe Veber <philippe.veber@gmail.com>
Cc: caml users <caml-list@inria.fr>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Caml-list] Strange camlp4 issue

Dear Philippe,

On 1 October 2012 17:21, Philippe Veber <philippe.veber@gmail.com> wrote:
>                     let _ = (a7818b19c#compound : Rbase.compound 'abdf89974)

This appears to be the line where things are going wrong.
Rbase.compound 'abdf89974 is not a valid type in original (i.e.
standard) OCaml syntax, but is valid in the revised syntax.  It may be
that you're using the wrong camlp4 executable somewhere along the
line: for example, using quotations for revised syntax in your
extension, but building the extension using an original-syntax based
executable such as camlp4o.  There's a handy guide to the various
camlp4 executables on the wiki:

http://brion.inria.fr/gallium/index.php/Using_Camlp4#Camlp4_executables_functionalities

You're seeing different error-reporting behaviour depending on whether
you redirect the file because camlp4 checks whether it's printing to a
terminal when deciding whether to print textual or binary output by
default:

http://caml.inria.fr/svn/ocaml/trunk/camlp4/Camlp4Printers/Camlp4AutoPrinter.ml

Hope that helps a bit,

Jeremy.