From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id pA4Ib8Y7015062 for ; Fri, 4 Nov 2011 19:37:08 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhACAEMwtE7RVde2kGdsb2JhbABDmlOPKAgiAQEBAQkJDQcUBCGBcgEBAQMBEgIsARsYBgMBCwYFCzALIgERAQUBHBkih2CYYwqLVIJhhSo9iHACBQqJIQSICIwUjTo9g34 X-IronPort-AV: E=Sophos;i="4.69,456,1315173600"; d="scan'208";a="116978310" Received: from mail-ey0-f182.google.com ([209.85.215.182]) by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 04 Nov 2011 19:37:03 +0100 Received: by eyd10 with SMTP id 10so3917939eyd.27 for ; Fri, 04 Nov 2011 11:37:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=wF5lj9hhN9cE4ZXXntcxAoYFuDYYuyKBE53TZakP36g=; b=ZAwwn68IYnP3zuf3hPtxpi7Gu9k+bodI0JLzqVBo1cxFw4EKOiu5yzGBaUsTyisFOC Tq7QlRJW1S1mSg7yn0JB08n40psDD4WE475aAuCE5F2pgzIeLhDdTeeqopcpRwIABO1+ dB0lAxe+KGPovsuv0uTbZPdovvpOStU6rwqTY= MIME-Version: 1.0 Received: by 10.14.15.195 with SMTP id f43mr1434426eef.233.1320431823182; Fri, 04 Nov 2011 11:37:03 -0700 (PDT) Received: by 10.14.95.197 with HTTP; Fri, 4 Nov 2011 11:37:03 -0700 (PDT) In-Reply-To: References: Date: Sat, 5 Nov 2011 03:37:03 +0900 Message-ID: From: Jun Furuse To: caml-list@inria.fr Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by walapai.inria.fr id pA4Ib8Y7015062 Subject: Re: [Caml-list] Re: Jump-to-definition and type-aware completion for Caml (was : Argot 1.0 release) On Fri, Nov 4, 2011 at 10:21 PM, Daniel Bünzli wrote: > That's the problem. I tend not to rely too much beyond what is > provided by the standard distribution. Spotter patch does not affect the object files at all, so I am sure that it is compatible with the original compiler. I test this compatibility by compiling the original ocamlc by the patched one. If you do not trust me (and you should not :-) ), you can always use the patched compiler at the development stage, then recompile your program/library by the original compiler just before the installation. Jun