From: Alain Frisch <Alain.Frisch@ens.fr>
To: Pierre Weis <pierre.weis@inria.fr>
Cc: Luc Maranget <Luc.Maranget@inria.fr>, <jgoerzen@complete.org>,
Caml list <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamllex/yacc and camlp4
Date: Thu, 17 Jun 2004 08:46:55 +0200 (MET DST) [thread overview]
Message-ID: <Pine.SOL.4.44.0406170842470.23010-100000@clipper.ens.fr> (raw)
In-Reply-To: <200406162248.AAA11976@pauillac.inria.fr>
On Thu, 17 Jun 2004, Pierre Weis wrote:
> 1) ocamllex and ocamlyacc implementation technologies are damned fast
> and it is difficult to compete with them using streams.
As I understand it, the question was about implementing ocamllex/ocamlyacc
frontend (parsing the specifications) and backend (producing OCaml code)
using Camlp4, not about implementing lexers/parsers using Camlp4 grammars.
I wrote a pa_ocamllex some time ago (and it is included in the OCaml
distribution), but it is no longer in sync with new ocamllex features
(capture variables).
Using Camlp4 to parse the specifications has several advantages: simpler
build procedure (no intermediate file to be generated), support for
alternative syntaxes (e.g. the revised syntax).
-- Alain
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-06-17 6:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 3:26 John Goerzen
2004-06-16 6:56 ` Luc Maranget
2004-06-16 22:48 ` Pierre Weis
2004-06-17 2:04 ` William Lovas
2004-06-17 9:42 ` skaller
2004-06-17 6:46 ` Alain Frisch [this message]
2004-06-17 9:36 ` skaller
2004-06-17 1:44 ` Shawn Wagner
2004-06-29 7:34 ` [Caml-list] Startconditions in ocamllex oliver
2004-06-29 8:00 ` Luc Maranget
2004-06-30 7:45 ` Hendrik Tews
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=Pine.SOL.4.44.0406170842470.23010-100000@clipper.ens.fr \
--to=alain.frisch@ens.fr \
--cc=Luc.Maranget@inria.fr \
--cc=caml-list@inria.fr \
--cc=jgoerzen@complete.org \
--cc=pierre.weis@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;
as well as URLs for NNTP newsgroup(s).