From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Parser
Date: Sat, 07 Mar 2009 12:15:39 +0100 [thread overview]
Message-ID: <87zlfxd1no.fsf@xs4all.nl> (raw)
In-Reply-To: <49ADF2ED.3060102@lacqui.com> (Kevin Lacquement's message of "Tue, 03 Mar 2009 19:18:05 -0800")
Kevin Lacquement <kevin@lacqui.com> writes:
> Again looking at the script parser, I notices that it uses a
> Yacc-generated parser, but a hand-written tokenizer. Is there a reason
> that it doesn't use Lex? Is it due to external dependencies, and if so,
> is there a way to recreate these deps (library or whatever) within the
> constraints of the bootloader?
Right, and I really hate the handwritten parser. It is easy to
cleanly use bison. Lex, OTOH, isn't easy and clean to use. IIRC it
depended on file IO, etc. If you know a *clean* way to deal with
this, I would favor it. Making all kinds of dirty stubs is something
I don't really like.
--
Marco
next prev parent reply other threads:[~2009-03-07 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 3:18 Parser Kevin Lacquement
2009-03-07 11:15 ` Marco Gerards [this message]
2009-03-09 16:43 ` Parser Kevin Lacquement
2009-03-09 18:09 ` Parser Felix Zielcke
2009-03-09 19:03 ` Parser Kevin Lacquement
2009-03-09 20:55 ` Parser David Miller
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=87zlfxd1no.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.