From: Dario Teixeira <darioteixeira@yahoo.com>
To: caml-list@inria.fr, Jacques Carette <carette@mcmaster.ca>
Subject: Re: [Caml-list] Unicode solutions
Date: Mon, 12 Apr 2010 08:44:42 -0700 (PDT) [thread overview]
Message-ID: <49370.20872.qm@web111509.mail.gq1.yahoo.com> (raw)
In-Reply-To: <4BC32FAC.8060703@mcmaster.ca>
Hi,
> It seems like ulex + dypgen works for the front-end
> part. Back-end?
> [It's not clear to me that ulex + menhir works]
I can confirm that at least with a recent Menhir, you can use whichever lexer
you want, even Ulex. In fact, I have used the Ulex+Menhir combination in a
couple of my own projects, and their source-code is available if you want
to check out how it's done:
https://forge.ocamlcore.org/scm/viewvc.php/trunk/ccss/src/ccss.ml?root=ccss
https://forge.ocamlcore.org/scm/viewvc.php/trunk/lambdoc/src/lib/lambdoc_read_lambtex/main.ml?root=lambdoc
Hope that helps,
Dario Teixeira
next prev parent reply other threads:[~2010-04-12 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 14:35 Jacques Carette
2010-04-12 15:44 ` Dario Teixeira [this message]
2010-04-12 17:30 ` [Caml-list] " Francois Pottier
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=49370.20872.qm@web111509.mail.gq1.yahoo.com \
--to=darioteixeira@yahoo.com \
--cc=caml-list@inria.fr \
--cc=carette@mcmaster.ca \
/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).