From: Yitzhak Mandelbaum <yitzhak@research.att.com>
To: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Ask for a more efficient way to deallocate memory (full version)
Date: Mon, 10 Dec 2007 21:03:57 -0500 [thread overview]
Message-ID: <337F504E-19AE-4629-A1A2-E48E5CD0EADE@research.att.com> (raw)
In-Reply-To: <200712102259.30602.jon@ffconsultancy.com>
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 3755 bytes --]
next prev parent reply other threads:[~2007-12-11 2:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 21:39 Fabrice.Pardo
2007-12-09 21:55 ` [Caml-list] " Olivier Andrieu
2007-12-10 11:25 ` Fabrice Pardo
2007-12-10 12:03 ` Michaël Le Barbier
2007-12-10 16:33 ` Oliver Bandel
2007-12-10 20:27 ` Richard Jones
2007-12-10 21:05 ` Oliver Bandel
2007-12-10 21:15 ` Gordon Henriksen
2007-12-10 22:13 ` Oliver Bandel
2007-12-10 22:59 ` Jon Harrop
2007-12-10 23:29 ` Jon Harrop
2007-12-11 2:03 ` Yitzhak Mandelbaum [this message]
2007-12-15 21:33 ` Oliver Bandel
2007-12-16 15:14 ` Jon Harrop
2007-12-10 23:24 ` Jon Harrop
2007-12-09 21:57 ` Oliver Bandel
2007-12-09 22:12 ` Jon Harrop
2007-12-09 22:34 ` Oliver Bandel
2007-12-09 22:16 ` Oliver Bandel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=337F504E-19AE-4629-A1A2-E48E5CD0EADE@research.att.com \
--to=yitzhak@research.att.com \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox