From: Michal Marek <mmarek@suse.cz>
To: Martin Walch <walch.martin@web.de>
Cc: Jan Beulich <JBeulich@suse.com>,
pebolle@tiscali.nl, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] kconfig: allow use of relations other than (in)equality
Date: Thu, 02 Jul 2015 22:06:26 +0200 [thread overview]
Message-ID: <559599C2.6090505@suse.cz> (raw)
In-Reply-To: <6743206.QpmKW5snMP@tacticalops>
Dne 2.7.2015 v 15:04 Martin Walch napsal(a):
> Hi,
>
>> 1: allow use of relations other than (in)equality
>
> I know it is a bit late for objections. Still, I want to point out that
> this looks to me like a major extension to the language.
>
> Kconfig is a configuration language, and as far as I can tell it is
> (intentionally) not Turing complete to keep the configuration simple and
> controllable. All relations that have been defined so far check for equality
> (or for being not equal). The new relations "<=", ">=", "<", and ">" add more
> expressiveness, potentially making the language actually more complex and
> reasoning harder.
The patch just adds four new binary operations of the same order as the
existing == and !=, with a the semantics that everybody expects. And the
grammar for kconfig expressions is so simplistic that you cannot even
write things like (A && B) == (C && D). So turing completeness is not a
topic here, neither before nor after this patch.
Michal
next prev parent reply other threads:[~2015-07-02 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 11:59 [PATCH 0/2] kconfig: allow use of relations other than (in)equality Jan Beulich
2015-06-15 12:18 ` Michal Marek
2015-07-02 13:04 ` Martin Walch
2015-07-02 20:06 ` Michal Marek [this message]
2015-07-03 9:18 ` Paul Bolle
2015-07-04 15:47 ` Martin Walch
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=559599C2.6090505@suse.cz \
--to=mmarek@suse.cz \
--cc=JBeulich@suse.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--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;
as well as URLs for NNTP newsgroup(s).