From: David Teller <David.Teller@univ-orleans.fr>
To: Yitzhak Mandelbaum <yitzhak@research.att.com>
Cc: Nicolas Pouillard <nicolas.pouillard@gmail.com>,
caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Building a parser with Camlp4
Date: Sat, 08 Dec 2007 15:02:53 +0100 [thread overview]
Message-ID: <1197122573.6111.5.camel@Blefuscu> (raw)
In-Reply-To: <473A3930-912E-4050-8389-B92229B8ABC3@research.att.com>
Well, with my current parser, parsing the standard library of JavaScript
2 (a few thousand lines) several minutes (with debugging code on). Which
is a bit too much. So, no, I can't answer your question but yes,
performance does matter.
Cheers,
David
On Wed, 2007-11-28 at 07:38 -0500, Yitzhak Mandelbaum wrote:
> A more important question (IMHO) : does it matter? I.e. how fast do
> you need the parser to be?
prev parent reply other threads:[~2007-12-08 14:02 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
2007-12-08 14:02 ` David Teller [this message]
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=1197122573.6111.5.camel@Blefuscu \
--to=david.teller@univ-orleans.fr \
--cc=caml-list@yquem.inria.fr \
--cc=nicolas.pouillard@gmail.com \
--cc=yitzhak@research.att.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