From: Yitzhak Mandelbaum <yitzhak@research.att.com>
To: Nicolas Pouillard <nicolas.pouillard@gmail.com>
Cc: David Teller <david.teller@univ-orleans.fr>,
caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Building a parser with Camlp4
Date: Wed, 28 Nov 2007 07:38:31 -0500 [thread overview]
Message-ID: <473A3930-912E-4050-8389-B92229B8ABC3@research.att.com> (raw)
In-Reply-To: <1196243387-sup-4653@port-ext2.ensta.fr>
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
A more important question (IMHO) : does it matter? I.e. how fast do
you need the parser to be?
On Nov 28, 2007, at 4:57 AM, Nicolas Pouillard wrote:
>> * Camlp4 looks relatively slow -- is it much slower than Yacc ?
>
> Yes, that's the cost of dynamic extensibility.
--------------------------------------------------
Yitzhak Mandelbaum
AT&T Labs - Research
http://www.research.att.com/~yitzhak
[-- Attachment #2: Type: text/html, Size: 3066 bytes --]
next prev parent reply other threads:[~2007-11-28 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 7:14 David Teller
2007-11-28 9:57 ` [Caml-list] " Nicolas Pouillard
2007-11-28 12:38 ` Yitzhak Mandelbaum [this message]
2007-12-08 14:02 ` David Teller
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=473A3930-912E-4050-8389-B92229B8ABC3@research.att.com \
--to=yitzhak@research.att.com \
--cc=caml-list@yquem.inria.fr \
--cc=david.teller@univ-orleans.fr \
--cc=nicolas.pouillard@gmail.com \
/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