From: Paul Bolle <pebolle@tiscali.nl>
To: Martin Walch <walch.martin@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [kconfig] results of some syntactical checks
Date: Thu, 18 Jul 2013 14:17:56 +0200 [thread overview]
Message-ID: <1374149876.14303.8.camel@x61.thuisdomein> (raw)
In-Reply-To: <98150748.1bixKSE5hB@tacticalops>
On Wed, 2013-07-17 at 15:07 +0200, Martin Walch wrote:
> All this can be avoided by quoting values, i. e.
>
> range "8260" "8272"
>
> and
>
> default "4711"
Documentation/kbuild/kconfig-language.txt even states
Constant symbols are always surrounded by single or double quotes.
But apparently the parser doesn't care. All "range" digits are unquoted,
and most "default" digits are unquoted.
> Also, avoiding integers (and hex values) as symbol names looks like a
> reasonable idea.
I was actually surprised that these were allowed, and only discovered
that when my local script generated a few false positives. But, anyhow,
in practice those symbol names seem to work just fine.
Paul Bolle
prev parent reply other threads:[~2013-07-18 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 22:34 Martin Walch
2013-07-16 23:18 ` Paul Bolle
2013-07-17 6:30 ` Paul Bolle
2013-07-17 13:07 ` Martin Walch
2013-07-18 12:17 ` Paul Bolle [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=1374149876.14303.8.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=walch.martin@web.de \
/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
all inboxes | Powered by JetHome®