Boost logo

Boost Users :

From: Mikko Vainio (mivainio_at_[hidden])
Date: 2007-03-06 01:42:48


Saving configuration in a human-readable text file would certainly be
useful. It'd be nice to be able to write out a default parameter file
containing all possible options, their default (=current?) values, and
comments on each option (possibly including a list of permitted values).

//Mikko

Aljaz wrote:
> Also if you have lets say 30 program options, would that be stupid to write
> all in command line?
>
> It would be cool if I had GUI for user confguration, but its confusing if
> user wants to edit serialized config file by himself.
>
>
> "Robert Ramey" <ramey_at_[hidden]> wrote in message
> news:eshgoi$630$1_at_sea.gmane.org...
>> Hmmm - I'm wondering why you wouldn't use the seriailzation libary for
>> this.
>>
>> Here is the scenario:
>>
>> take a program which uses program options. Add one more option
>> e.g -i<file name>
>>
>> On startup, check for -i switch. If switch isn't used, process options
>> and store
>> them in a class intance. On program shutdown, save class instance toa
>> file
>> using serialization. If swith IS used, just load class instance from file
>> using
>> serialization.
>>
>> Seems to me that the two libraries complement each other in this case.
>>
>> Robert Ramey
>>
>>
>> Aljaz wrote:
>>> I wonder if there are any functions in boost program options libary
>>> to save them back to configuration file?
>>>
>>> Maybe any example?
>>>
>>> Thanks for help
>
>
>
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>


Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net