From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: [PATCH libnftables] Add support for ct set Date: Fri, 10 Jan 2014 13:27:04 +0000 Message-ID: <20140110132703.GA8224@macbook.localnet> References: <1389359425-6837-1-git-send-email-kristian.evensen@gmail.com> <20140110131406.GA8088@macbook.localnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Netfilter Development Mailing list To: Kristian Evensen Return-path: Received: from stinky.trash.net ([213.144.137.162]:59187 "EHLO stinky.trash.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752361AbaAJN1H (ORCPT ); Fri, 10 Jan 2014 08:27:07 -0500 Content-Disposition: inline In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: On Fri, Jan 10, 2014 at 02:19:42PM +0100, Kristian Evensen wrote: > Hi, > > On Fri, Jan 10, 2014 at 2:14 PM, Patrick McHardy wrote: > > nftables uses statements for things that don't return a value. I think > > it would make sense to keep this consistent. An "set" expression (aka > > statement) can never be used in a match, so its something fundamentally > > different than an expression. > > Are you discussing the removal of the union? No, I'm refering to the (ab)use of the expression. Anything not returning data is not an expression but a statement.