From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 861641B561 for ; Tue, 9 Oct 2018 16:31:27 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2153520E69; Tue, 9 Oct 2018 10:31:27 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 09 Oct 2018 10:31:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=va8D/1FhwHQ7Dxoek3u29eW8/iBUjd2VugjqhKfSL4M=; b=OfKj8jJAoHgm FZgoYz05YINmgCWtx6SbWqrVsou5aKtCDQQHJDhRDolsqOPl7Mur9yF/fZTBSZnh lZQ+2Hp9vxfAk3U7odRc8VU1CpzmuCYmaAp5MCbCyBHJNcLhvyFG7Y6sHt2Xg+5i VTKYlmEmfb2JDAp7jIDkcHFGU/eGuAI= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=va8D/1FhwHQ7Dxoek3u29eW8/iBUjd2VugjqhKfSL 4M=; b=t2pum3pX6EYG8G69V60wYg/WhYsl6UFWMinMFQMeQnJJsFBOoGtqROGTq Rkq93s8DvK+S5FmYhG4ti0JgkYcbTOBWLIydvCurU+HTkbhkCUAb5CIjp+wx213q NFdNPEm6lB+IuZPW5exZMj7I6GXYwEl7vfoy21wuqGYb3AfflA9fBnjlMseqIDiL hYYfa129rdgflsY1lXoCX0yAwvbFC9RaqR8ybr22DYSm01NxXALFpmSy8KehdMCj bCQ7ZBWqKIe+oFM5QUGafwD6/8zJeumAjodBEvSsmJULN9z4JmgvvN2nytKC3xXo dB6vxLGIna6IjF3I3GiBUI1Wnc0TA== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 48C01E4124; Tue, 9 Oct 2018 10:31:25 -0400 (EDT) From: Thomas Monjalon To: =?ISO-8859-1?Q?Ga=EBtan?= Rivet Cc: dev@dpdk.org, ophirmu@mellanox.com, ferruh.yigit@intel.com, arybchenko@solarflare.com, olivier.matz@6wind.com, remy.horton@intel.com Date: Tue, 09 Oct 2018 16:31:24 +0200 Message-ID: <6562576.89BUxVsNiX@xps> In-Reply-To: <20181009141406.rle54bpq6ictu3zd@bidouze.vm.6wind.com> References: <20181009021858.19216-1-thomas@monjalon.net> <20181009021858.19216-2-thomas@monjalon.net> <20181009141406.rle54bpq6ictu3zd@bidouze.vm.6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Subject: Re: [dpdk-dev] [PATCH 1/4] kvargs: support list value X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2018 14:31:27 -0000 09/10/2018 16:14, Ga=EBtan Rivet: > Hi Thomas, >=20 > On Tue, Oct 09, 2018 at 04:18:55AM +0200, Thomas Monjalon wrote: > > If a value contains a comma, rte_kvargs_tokenize() will split here. > > In order to support list syntax [a,b] as value, an extra parsing of > > the square brackets is added. > >=20 >=20 > Nice, I was actually planning to do this. >=20 > I think it could be useful to also support () and {}, as well as > recursive lists, but it is best to have a first version to support > representor and go from this. Yes, we have no usage of () and {} so far.