From: iguern-a@yahoo.fr
To: caml-list@yquem.inria.fr
Subject: Re : Caml-list Digest, Vol 41, Issue 26
Date: Sat, 15 Nov 2008 12:12:03 +0000 (GMT) [thread overview]
Message-ID: <874841.70928.qm@web28106.mail.ukl.yahoo.com> (raw)
In-Reply-To: <20081115110003.AD426BBB7@yquem.inria.fr>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
> - GLR instead of LR(1) : this gives much more elegant description of the
> grammar (and the possibiliy of ambigous grammar) and there
> is never a conflict. These are replaced by multiple parse trees (you can
> choose a merge function that will report that as an error, if you think
> your grammar should not be ambiguous).
Great ! In Ocamlwizard, we've patched an ocaml parser (3.10.2) which recovers
on errors located at the end of \ffile (using the EOF token). We've also consider using the error token but it's more difficult (because of ambiguities).
Since dypgen generates multiple parse trees, It could be easier to implement this feature. I hope I'll have time to try it.
Regards.
Mohamed Iguernelala
http://ocamlwizard.lri.fr/
[-- Attachment #2: Type: text/html, Size: 976 bytes --]
parent reply other threads:[~2008-11-15 12:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20081115110003.AD426BBB7@yquem.inria.fr>]
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=874841.70928.qm@web28106.mail.ukl.yahoo.com \
--to=iguern-a@yahoo.fr \
--cc=caml-list@yquem.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).