From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id 5C5F55A93 for ; Thu, 2 Jun 2016 22:51:52 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id C82DBF5; Thu, 2 Jun 2016 13:51:51 -0700 (PDT) Date: Thu, 2 Jun 2016 13:51:51 -0700 From: Matthew Hall To: "Wiles, Keith" Cc: Neil Horman , Thomas Monjalon , Yuanhan Liu , "dev@dpdk.org" , "Richardson, Bruce" , "Tan, Jianfeng" , Stephen Hemminger , Christian Ehrhardt , Panu Matilainen , Olivier Matz Message-ID: <20160602205151.GA24543@mhcomputing.net> References: <20160602104106.GA12923@hmsreliant.think-freely.org> <2363376.b1CWhBpcZG@xps13> <75917C44-9CF7-4A0B-B8D3-CD7DC7425D49@intel.com> <20160602171120.GB12923@hmsreliant.think-freely.org> <7091836E-B9D5-4F99-ADDB-A47B4C7B5F7E@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7091836E-B9D5-4F99-ADDB-A47B4C7B5F7E@intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [dpdk-dev] [RFC] Yet another option for DPDK options X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 20:51:52 -0000 On Thu, Jun 02, 2016 at 07:41:10PM +0000, Wiles, Keith wrote: > Would this work better in the long run, does a fixed structure still make sense? This right here is why I suggested libjson-c as an example. It has a nice API like this already: http://json-c.github.io/json-c/json-c-0.12/doc/html/json__object_8h.html Matthew.