From: brogoff@speakeasy.net
To: Michal Moskal <malekith@pld-linux.org>
Cc: Diego Olivier Fernandez Pons <Diego.FERNANDEZ_PONS@etu.upmc.fr>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Ocamlyacc vs stream parser
Date: Wed, 28 May 2003 08:45:14 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0305280831450.32649-100000@grace.speakeasy.net> (raw)
In-Reply-To: <20030528102456.GA5672@roke.freak>
On Wed, 28 May 2003, Michal Moskal wrote:
> On Wed, May 28, 2003 at 11:37:03AM +0200, Diego Olivier Fernandez Pons wrote:
> > Bonjour,
> >
> > > Sorry, I thought camlp4 recognizes LL(1) languages, and my dragon book
> > > copy states that LR(1) > LL(1) (I'm not sure about LARL(1) though).
> >
> > My Appel states that LL(1) is not included in LALR(1).
>
> Oh, so by proof-by-book you're right :-)
That's pretty funny, but those Romans did have this case covered. I believe
the Latin expression is "argumentum ad verecundiam".
> But in practice LARL(1) seems
> more usefull for parsing, at parsing least programming languages.
This is esoteric flame bait for the parsing crowd. I happen to think that
recursive descent is the best way to write parsers, but note that recursive
descent parsers are capable of parsing non-LL(1) grammars, even without the
fairly obvious hacks. As a real world proof by example, consider that Ada is
often cited as a language not amenable to RDP (Fraser&Hanson : "For example,
C is in the class of languages that can be recognized by recursive descent
parsers, but other languages, like ADA (sic), are not."), yet somehow the
authors of GNAT were ignorant enough to make it work.
In the real world, you'll need to be proficient with YACC and RDP, of course.
-- Brian
-------------------
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:[~2003-05-28 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 9:07 Lukasz Lew
2003-05-23 9:26 ` Michal Moskal
2003-05-26 12:28 ` Damien Doligez
2003-05-27 21:12 ` Pierre Weis
2003-05-28 9:20 ` Michal Moskal
2003-05-28 9:37 ` Diego Olivier Fernandez Pons
2003-05-28 10:24 ` Michal Moskal
2003-05-28 15:45 ` brogoff [this message]
2003-05-28 20:34 ` Alain.Frisch
2003-05-28 10:48 ` Anton Moscal
2003-06-05 14:02 Diego Olivier Fernandez Pons
2003-06-10 9:03 ` Diego Olivier Fernandez Pons
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.LNX.4.44.0305280831450.32649-100000@grace.speakeasy.net \
--to=brogoff@speakeasy.net \
--cc=Diego.FERNANDEZ_PONS@etu.upmc.fr \
--cc=caml-list@inria.fr \
--cc=malekith@pld-linux.org \
/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