From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 947601B5AD for ; Wed, 10 Oct 2018 15:13:04 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Oct 2018 06:13:03 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,364,1534834800"; d="scan'208";a="270133665" Received: from rhorton-mobl1.ger.corp.intel.com (HELO [163.33.179.30]) ([163.33.179.30]) by fmsmga005.fm.intel.com with ESMTP; 10 Oct 2018 06:13:00 -0700 To: Stephen Hemminger , Thomas Monjalon References: <20181009021858.19216-1-thomas@monjalon.net> <20181009021858.19216-2-thomas@monjalon.net> <20181009141406.rle54bpq6ictu3zd@bidouze.vm.6wind.com> <6562576.89BUxVsNiX@xps> <20181009081140.5c977ad6@xeon-e3> Cc: =?UTF-8?Q?Ga=c3=abtan_Rivet?= , dev@dpdk.org, ophirmu@mellanox.com, ferruh.yigit@intel.com, arybchenko@solarflare.com, olivier.matz@6wind.com From: Remy Horton Organization: Intel Shannon Limited Message-ID: Date: Wed, 10 Oct 2018 14:12:59 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <20181009081140.5c977ad6@xeon-e3> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 10 Oct 2018 13:13:05 -0000 On 09/10/2018 16:11, Stephen Hemminger wrote: > On Tue, 09 Oct 2018 16:31:24 +0200 [..] > This is getting complex enough that doing a real parser maybe necessary. I thought the same thing back in April with the port representor patchsets. Quickly run out of things to use as delimiters otherwise. > Why not lex/yacc? Think Yacc/Bison are vastly overcomplex and a bit of a pain to integrate. The sort of config grammar needed here will most likely be LL(1), so fairly easy to do by hand anyway. > Or better yet go to real syntax like JSON. >