> -----Original Message----- > From: Allain Legacy [mailto:allain.leg...@windriver.com] > Sent: Thursday, March 2, 2017 7:29 PM > To: Richardson, Bruce <bruce.richard...@intel.com>; Dumitrescu, Cristian > <cristian.dumitre...@intel.com> > Cc: dev@dpdk.org; Jolliffe, Ian (Wind River) <ian.jolli...@windriver.com> > Subject: [PATCH 3/5] cfgfile: add support for unamed global section > > The current implementation of the cfgfile library requires that all > key=value pairs be within [SECTION] definitions. The ini file standard > allows for key=value pairs in an unnamed section. That section is > considered the [GLOBAL] section. > > This commit adds the capability of parsing key=value pairs from such an > unnamed section. The CFG_FLAG_GLOBAL_SECTION flag must be passed to > the > rte_cfgfile_load() API to enable this functionality. >
What is the motivation for the having key/value pair outside of any section? What would be the drawback of having the user explicitly define a GLOBAL section to host these key/value pairs?
