From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Legacy, Allain" Subject: Re: [PATCH v2 6/6] cfgfile: add support for empty value string Date: Mon, 27 Mar 2017 11:15:27 +0000 Message-ID: <70A7408C6E1BFB41B192A929744D8523968F7D95@ALA-MBC.corp.ad.wrs.com> References: <1488482971-170522-1-git-send-email-allain.legacy@windriver.com> <1489065060-98370-1-git-send-email-allain.legacy@windriver.com> <1489065060-98370-7-git-send-email-allain.legacy@windriver.com> <3EB4FA525960D640B5BDFFD6A3D891265277BE82@IRSMSX108.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "yuanhan.liu@linux.intel.com" , "dev@dpdk.org" To: "DUMITRESCU, CRISTIAN FLORIN" , "RICHARDSON, BRUCE" Return-path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by dpdk.org (Postfix) with ESMTP id A7F9DD59A for ; Mon, 27 Mar 2017 13:15:29 +0200 (CEST) Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > -----Original Message----- > From: Legacy, Allain > Sent: Monday, March 27, 2017 7:13 AM > To: DUMITRESCU, CRISTIAN FLORIN; RICHARDSON, BRUCE > Cc: yuanhan.liu@linux.intel.com; dev@dpdk.org > Subject: RE: [PATCH v2 6/6] cfgfile: add support for empty value string >=20 > We have a legacy file format that we need to support. Other parts of ou= r > system are able to handle a "key=3D" entry in the file so we are trying t= o gain > parity with those parsers. >=20 I should have also mentioned that I briefly considered changing rte_strspli= t() to be able to handle that case because in python the split function han= dles this scenario in the desired way: a =3D "key=3D" a.split('=3D') ['key', ''] But, I figured that change would be too intrusive and would likely be rejec= ted. Allain