Subject: Re: [boost] Library for configuration file parsing
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2010-11-29 12:44:57
> -----Original Message-----
> From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]]
> On Behalf Of Denis Shevchenko
> Sent: Monday, November 29, 2010 7:18 AM
> To: boost_at_[hidden]
> Subject: Re: [boost] Library for configuration file parsing
> On 28.11.2010 10:40, sguazt wrote:
> > Said that, while the proposed library looks promising, I would avoid
> > to call it "configurator" since it seems limited to parse INI files.
> > Configuration file can be done in very different format.
> > INI is just a choice, but not the only one.
> Hi, sguazt!
> INI-file is a simplest format supported by my library (I understand that
> programmers is quite enough INI-files). But Configurator supports also:
> - option's default value and necessity,
> - arbitrary nesting of sections,
> - checks of value's semantic, "classical" (IPv4 and IPv6, path, email) and
> extended (file 'size' and 'time period'),
> - options with multi-values (something like in Apache httpd.conf),
> - reparsing with using initial default values of options (will be added in
> See example of advanced usage of Configurator:
This looks rather useful for those who need to do these things *with
(And who wants to leave the hapless user in a muddle because they didn't
check the IP address given isn't a valid IP address?)
So I would encourage getting it in the sandbox (and in the 'standard' Boost
This will allow potential users to give it a proper test drive.
BUT to be considered for a Boost Library, every file must contain the Boost
(IMO you can have the MIT licence too - since they say the same, but to keep
thing simple, we have decided we need to avoid any lawyers' doubt by
requiring the Boost license).
--- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow_at_[hidden]
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk