From: Jon Loeliger <jdl@jdl.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] DTC: Remove the need for the GLR Parser.
Date: Tue, 23 Oct 2007 09:49:09 -0500 [thread overview]
Message-ID: <E1IkL49-0006W4-8X@jdl.com> (raw)
In-Reply-To: Your message of "Tue, 23 Oct 2007 16:41:51 +0200." <cace68e0fe3e4e257b7c63d18c805f18@kernel.crashing.org>
So, like, the other day Segher Boessenkool mumbled:
>
> >> And even without glr-parser, I'm still uncomfortable with the
> >> lexer<->parser execution ordering issues with the current
> >> /dts-version/ proposal. It may now be true that the order is
> >> guaranteed to be correct, but it's still not exactly obvious.
>
> If you require /dts-version/ (and similar global dtc-control stmts)
> to be at the start of the file, can't you avoid this ordering problem
> by starting to parse the file with a simple (hand-written) parser
> (which would handle these statements) and only when you cannot parse
> any more switch to the "normal" parser (which won't handle them)?
> Or is this a stupid suggestion :-)
My concern here is that I think we are attempting to make
this significantly more complex than it needs to be.
We have a pretty good KISS opportunity here, and I've shown
it to be working so far. Longer term, all this cruft will
go away and it will become a moot point anyway.
jdl
next prev parent reply other threads:[~2007-10-23 14:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 21:13 [PATCH] DTC: Remove the need for the GLR Parser Jon Loeliger
2007-10-23 2:54 ` David Gibson
2007-10-23 14:24 ` Jon Loeliger
2007-10-23 14:41 ` Segher Boessenkool
2007-10-23 14:49 ` Jon Loeliger [this message]
2007-10-23 23:41 ` David Gibson
2007-10-23 23:37 ` David Gibson
2007-10-23 16:07 ` Jon Loeliger
2007-10-23 23:44 ` David Gibson
2007-10-24 1:11 ` David Gibson
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=E1IkL49-0006W4-8X@jdl.com \
--to=jdl@jdl.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).