Re: [boost] Library for configuration file parsing

Subject: Re: [boost] Library for configuration file parsing
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-11-29 16:01:06

Denis Shevchenko wrote:
> On 29.11.2010 22:39, Stewart, Robert wrote:
>
> > Have you considered the ability to parse multiple files
> > thereby augmenting the data with each new file's content
> > rather than replacing what had been parsed already?
>
> Confess, I have not thought about it. Do you think this
> possibility is really useful?

Yes.  We use it constantly.  In one configuration system, files are segregated by user, machine, domain, etc., and appropriate files are selected at runtime, if found.  In another, the files are grouped by library or external entity for which configuration is needed and a list of files is applied to a given executable.

BTW, one must control overriding configuration data.  By default, I recommend that redefining a configuration value be an error.  Then, use some explicit syntax that indicates the desire to override/define a configuration value.  Having that, it can also be useful to have syntax that overrides a configuration value if it exists or ignores the override otherwise.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.