From: Shams (shams_at_[hidden])
Date: 2006-10-06 07:36:05
We are eargerly waiting, please post to this list when it is in CVS.
It is becoming a tiring task to collect "proposed" boost libraries
for usage when not in the main cvs.
1. What is the status on reading/writing environment variables?
2. Have you planned any support for writing command line arguments
as a string?
What I mean is that if a process wants to spawn another "written in-house"
process eg. something that uses boost.program_options to parse the command
could they use the property_tree library to generate such command line as
----- Original Message -----
From: "Marcin Kalicinski" <kalita_at_[hidden]>
Sent: Friday, October 06, 2006 11:57 PM
Subject: Re: property tree library not in CVS?
> Hi Jeff,
>> As I've done in the past, I'll really encourage you *not* wait to finish
>> docs to put the code in CVS. To help us avoid a repeat of 1.34 we need
>> libraries going into 1.35 to be in CVS and regression tested as early in
>> cycle as possible. [...]
> I agree it might be beneficial to put the library in the CVS, even though
> the docs are not up to date yet. But I don't yet have access to the main
> CVS, so how should we handle that?
> Thank you,
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk