From: Stefano Zacchiroli <zack@bononia.it>
To: Inria Ocaml Mailing List <caml-list@inria.fr>
Subject: Ulex and dypgen
Date: Thu, 26 Oct 2006 17:29:54 +0200 [thread overview]
Message-ID: <20061026152954.GA12313@aquarium.takhisis.invalid> (raw)
In-Reply-To: <4540D1AA.3030309@laposte.net>
On Thu, Oct 26, 2006 at 05:18:02PM +0200, Matthieu Dubuget wrote:
> is there a way to have menhir (or ocamlyacc) use a lexer produced with ulex?
Actually, I've to pose the very same question for dypgen.
More generally, what about an effort like what has been done for
standardizing OO interfaces for I/O, this time to standardize the
interface of lexers as used by the plethora of parsing engines nowadays
available for OCaml?
Cheers.
--
Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy
zack@{cs.unibo.it,debian.org,bononia.it} -%- http://www.bononia.it/zack/
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. -!-
prev parent reply other threads:[~2006-10-26 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 15:18 Ulex and menhir Matthieu Dubuget
2006-10-26 15:29 ` Stefano Zacchiroli [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=20061026152954.GA12313@aquarium.takhisis.invalid \
--to=zack@bononia.it \
--cc=caml-list@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