From: Josh Triplett <josh@freedesktop.org>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH 0/5] keyword driven parsing
Date: Fri, 09 Mar 2007 15:29:32 -0800 [thread overview]
Message-ID: <45F1EDDC.800@freedesktop.org> (raw)
In-Reply-To: <20070308085925.GA19829@chrisli.org>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
Christopher Li wrote:
> On Wed, Mar 07, 2007 at 10:55:07PM -0800, Josh Triplett wrote:
>> Christopher Li wrote:
>>
>> Beautiful! Looks far more elegant and maintainable; thanks.
>>
>> I've applied the first four patches in this series. The fifth causes a
>> regression in validation/context.c; see the attached diff of the output from
>> the fourth to the fifth patches.
>
> Hah. I misunderstand the syntax of context with only two arguments.
> This syntax sucks. The meaning of the each argument depends on the total
> number of arguments.
Guilty. :) I had to keep the two-argument version for backward compatibility,
but I still wanted what I considered a more intuitive argument order for the
new three-argument version. Think of the two-argument version as deprecated.
> The patch is updated.
>
> Chris
>
> Introduce keyword driven attribute parsing
>
> Now we are really parsing the attribute rather than building the
> expression tree first.
>
> Signed-Off-By: Christopher Li <sparse@chrisli.org>
Thanks, applied.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2007-03-09 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 10:01 [PATCH 0/5] keyword driven parsing Christopher Li
2007-03-07 15:45 ` Linus Torvalds
2007-03-08 6:55 ` Josh Triplett
2007-03-08 8:59 ` Christopher Li
2007-03-09 23:29 ` Josh Triplett [this message]
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=45F1EDDC.800@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=torvalds@osdl.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).