From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=AWL,HTML_MESSAGE,SPF_SOFTFAIL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by yquem.inria.fr (Postfix) with ESMTP id E4502BC6B for ; Tue, 11 Dec 2007 03:04:10 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAN9+XUfAFOFueGdsb2JhbACCcoxzAQoEBg8a X-IronPort-AV: E=Sophos;i="4.24,149,1196636400"; d="scan'208,217";a="6682303" Received: from mail-red.research.att.com ([192.20.225.110]) by mail3-smtp-sop.national.inria.fr with ESMTP; 11 Dec 2007 03:04:10 +0100 Received: from [192.168.0.101] (vpn-30.research.att.com [135.207.240.30]) by bigmail.research.att.com (8.13.7+Sun/8.11.6) with ESMTP id lBB2483v008529 for ; Mon, 10 Dec 2007 21:04:08 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <200712102259.30602.jon@ffconsultancy.com> References: <39980.81.57.198.61.1197236388.squirrel@webmail.lpn.cnrs.fr> <1197324811.475dba0b8c26d@webmail.in-berlin.de> <200712102259.30602.jon@ffconsultancy.com> Content-Type: multipart/alternative; boundary=Apple-Mail-172--11894492 Message-Id: <337F504E-19AE-4629-A1A2-E48E5CD0EADE@research.att.com> From: Yitzhak Mandelbaum Subject: Re: [Caml-list] Ask for a more efficient way to deallocate memory (full version) Date: Mon, 10 Dec 2007 21:03:57 -0500 To: caml-list X-Mailer: Apple Mail (2.752.3) X-Spam: no; 0.00; yitzhak:01 mandelbaum:01 yitzhak:01 camlp:01 camlp:01 compiler:01 top-down:01 recursive:01 bottom-up:01 lalr:01 compiler:01 parser:01 parser:01 type-checker:01 mandelbaum:01 --Apple-Mail-172--11894492 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Dec 10, 2007, at 5:59 PM, Jon Harrop wrote: > > However, using any camlp4 macros requires using the camlp4 > replacement for the > front-end of the compiler. That uses a different parsing technology > (top-down > recursive descent LL rather than bottom-up LALR) so the error > messages from > the compiler are completely different. Just to clarify : the error messages from the *parser* are completely different. Everything after the parser is the same with or without camlp4. Most importantly, you don't have to learn new type-checker messages. Yitzhak -------------------------------------------------- Yitzhak Mandelbaum AT&T Labs - Research http://www.research.att.com/~yitzhak --Apple-Mail-172--11894492 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1
On Dec 10, 2007, at 5:59 PM, Jon Harrop wrote:


However, using any camlp4 macros requires using the camlp4 = replacement for the=A0

front-end of the compiler. That uses a = different parsing technology (top-down=A0

recursive descent LL rather than = bottom-up LALR) so the error messages from=A0

the compiler are completely = different.


Just to clarify : the = error messages from the *parser* are completely different. Everything = after the parser is the same with or without camlp4. Most importantly, = you don't have to learn new type-checker messages.

Yitzhak

=

=
= --Apple-Mail-172--11894492--