From: "Jan Beulich" <JBeulich@suse.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: yann.morin.1998@free.fr, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/2] kconfig: don't silently ignore unhandled characters
Date: Tue, 04 Nov 2014 14:14:15 +0000 [thread overview]
Message-ID: <5458ED470200007800044DA7@mail.emea.novell.com> (raw)
In-Reply-To: <1415110006.20372.165.camel@x220>
>>> On 04.11.14 at 15:06, <pebolle@tiscali.nl> wrote:
> On Tue, 2014-11-04 at 09:05 +0000, Jan Beulich wrote:
>> At the very least we should tell people that waht they wrote is not
>> what the utility understands.
>
> Yes, we should change this. I'm inclined to think the should die with an
> error on invalid syntax. Would that be too strict?
I would think so. This could be made more strict once the warning
was in place for a couple of releases.
>> --- 3.18-rc3-kconfig.orig/scripts/kconfig/zconf.lex.c_shipped
>> +++ 3.18-rc3-kconfig/scripts/kconfig/zconf.lex.c_shipped
>> @@ -414,14 +414,14 @@ static yyconst flex_int16_t yy_nxt[][17]
>> },
>>
>> {
>> - 11, 26, 26, 27, 28, 29, 30, 31, 29, 32,
>> - 33, 34, 35, 35, 36, 37, 38
>> + 11, 26, 27, 28, 29, 30, 31, 32, 30, 33,
>> + 34, 35, 36, 36, 37, 38, 39
>>
>> },
>>
>> {
>> - 11, 26, 26, 27, 28, 29, 30, 31, 29, 32,
>> - 33, 34, 35, 35, 36, 37, 38
>> + 11, 26, 27, 28, 29, 30, 31, 32, 30, 33,
>> + 34, 35, 36, 36, 37, 38, 39
>> },
>>
>> {
>
> I guess we must trust that you manually edited this _shipped file
> correctly.
There was no manual editing involved - this is the re-generated
version.
>> @@ -920,7 +931,7 @@ static int input (void );
>> /* This used to be an fputs(), but since the string might contain NUL's,
>> * we now use fwrite().
>> */
>> -#define ECHO do { if (fwrite( zconftext, zconfleng, 1, zconfout )) {} } while (0)
>> +#define ECHO fwrite( zconftext, zconfleng, 1, zconfout )
>> #endif
>>
>> /* Gets input and stuffs it into "buf". number of characters read, or YY_NULL,
>
> But this hunk looks unrelated. Is this needed?
I think it should stay, even if my flex version may be slightly different
from the one that was used originally. As above - it's simply a result
of re-generating.
Jan
next prev parent reply other threads:[~2014-11-04 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 9:05 [PATCH 1/2] kconfig: don't silently ignore unhandled characters Jan Beulich
2014-11-04 14:06 ` Paul Bolle
2014-11-04 14:14 ` Jan Beulich [this message]
2014-11-05 10:36 ` Paul Bolle
2014-11-06 10:19 ` Jan Beulich
2014-11-06 10:28 ` Paul Bolle
2014-12-09 10:16 ` Paul Bolle
2014-12-19 16:31 ` Jan Beulich
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=5458ED470200007800044DA7@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=yann.morin.1998@free.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