Re: [boost] Library for configuration file parsing

Subject: Re: [boost] Library for configuration file parsing
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-12-02 07:53:23

Joel de Guzman wrote:
> On 12/2/2010 5:25 AM, Mika Heiskanen wrote:
> > On Wed, 2010-12-01 at 22:59 +0200, Marsh Ray wrote:
> >> On 12/01/2010 11:08 AM, Robert Ramey wrote:
> >>>   I personally
> >>> would be suspicious of a library submission which could
> >>> use it but declines to do so.  Actually, parsing a JSON file
> >>> would best rendered as an example application for spirit.
> >>
> >> Yeah, I think it would make a great example.
> >
> > Once again:
> >
> >    http://www.codeproject.com/KB/recipes/JSON_Spirit.aspx
> >
> > Unicode support is lacking in features though.
>
> Spirit2 has unicode support. I'll most probably write a robust
> JSON parser very soon. It will play along perfectly with the
> S-expression example and the universal-tree AST (utree) Hartmut
> and I have been tinkering with for the past BoostCon.

Such non-trivial examples, developed as tutorials, would be tremendously useful to improve the experience of those trying to use Spirit for non-trivial problems.

> Our current goal is to 1) ease the learning curve 2) provide
> a clear and easy development cycle for incremental development.

These are excellent goals and will go a very long way to increasing the use of Spirit if met.

_____
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.