From: Dario Teixeira <darioteixeira@yahoo.com>
To: caml-list@yquem.inria.fr, Micha <micha-1@fantasymail.de>
Subject: Re: [Caml-list] The lexer hack
Date: Sat, 14 Nov 2009 10:08:52 -0800 (PST) [thread overview]
Message-ID: <411864.11130.qm@web111503.mail.gq1.yahoo.com> (raw)
In-Reply-To: <200911141720.13847.micha-1@fantasymail.de>
Hi,
> if the lexer cannot decide it on the tokens seen, a packrat
> parser (like Aurochs) may be a better choice, since in a PEG
> there is no seperate lexer, it's all one grammar, so you don't
> have this problem.
But does Aurochs also handle UTF8 streams?
In the meantime I've implemented the parser using Ulex/Menhir
with the "dummy action" trick I mentioned before. It allowed
me to simplify the tokenizer tremendously, though it's still
present:
https://forge.ocamlcore.org/plugins/scmsvn/viewcvs.php/trunk/lambdoc/src/lib/lambdoc_read_lambtex/?root=lambdoc
Cheers,
Dario Teixeira
next prev parent reply other threads:[~2009-11-14 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 14:42 Dario Teixeira
2009-11-10 17:35 ` [Caml-list] " David Allsopp
2009-11-10 20:02 ` Dario Teixeira
2009-11-14 16:20 ` Micha
2009-11-14 18:08 ` Dario Teixeira [this message]
2009-11-14 19:09 ` Goswin von Brederlow
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=411864.11130.qm@web111503.mail.gq1.yahoo.com \
--to=darioteixeira@yahoo.com \
--cc=caml-list@yquem.inria.fr \
--cc=micha-1@fantasymail.de \
/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).