property tree library not in CVS?
Hello, I recall that Property Tree library has been accepted into boost: http://tinyurl.com/h5nlt I can find its documentation on the web and source to download, but I have downloaded current CVS: cvs -d:pserver:anonymous@boost.cvs.sourceforge.net:/cvsroot/boost login cvs -z3 -d:pserver:anonymous@boost.cvs.sourceforge.net:/cvsroot/boost checkout boost cvs -d:pserver:anonymous@boost.cvs.sourceforge.net:/cvsroot/boost logout And I cannot find it there. Anyone can explain why it's not there? (or maybe I'm just blind) -- Janek Kozicki |
Hi Janek, The result of the review stated that the library needs to fix several issues, including documentation, before the library is added to the CVS. The status at the moment is that the code and tests are ready (see boost-sandbox CVS), but I still need to update the documentation. cheers, Marcin Uzytkownik "Janek Kozicki" <janek_listy@wp.pl> napisal w wiadomosci news:20061005090825.49da045a@absurd...
Hello,
I recall that Property Tree library has been accepted into boost:
I can find its documentation on the web and source to download, but I have downloaded current CVS:
cvs -d:pserver:anonymous@boost.cvs.sourceforge.net:/cvsroot/boost login cvs -z3 -d:pserver:anonymous@boost.cvs.sourceforge.net:/cvsroot/boost checkout boost cvs -d:pserver:anonymous@boost.cvs.sourceforge.net:/cvsroot/boost logout
And I cannot find it there. Anyone can explain why it's not there? (or maybe I'm just blind)
-- Janek Kozicki | _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Marcin Kalicinski said: (by the date of Thu, 5 Oct 2006 10:28:29 +0100)
Hi Janek,
The result of the review stated that the library needs to fix several issues, including documentation, before the library is added to the CVS. The status at the moment is that the code and tests are ready (see boost-sandbox CVS), but I still need to update the documentation.
Hello, - did you use boost::multi_index as suggested in the review? - did you add support for boost::serialization? I'll start using your library (alredy downloaded from boost-sandbox) and possibly send some comments regarding the documentation. I hope that it will be included in 1.35 release? Thanks! PS: Sorry about writing on 'two channels' I didn't notice your response here :) So no need to reply on the other channel :) -- Janek Kozicki |
Hi Janek,
- did you use boost::multi_index as suggested in the review? - did you add support for boost::serialization?
No and yes. Multi index is not used internally, but boost::serialization is supported, and regressions that test if it works are present. You need to include <boost/property_tree/ptree_serialization.hpp> to get the support. cheers, Marcin
Marcin Kalicinski wrote:
Hi Janek,
The result of the review stated that the library needs to fix several issues, including documentation, before the library is added to the CVS. The status at the moment is that the code and tests are ready (see boost-sandbox CVS), but I still need to update the documentation.
cheers, Marcin
As I've done in the past, I'll really encourage you *not* wait to finish the 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 the cycle as possible. New authors tend to underestimate the amount of time/effort to resolve porting issues -- the key fact that there is often a 24 hour wait to see if fixes actually resolve issues. Jeff
Jeff Garland said: (by the date of Thu, 05 Oct 2006 06:34:00 -0700)
As I've done in the past, I'll really encourage you *not* wait to finish the 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 the cycle as possible. New authors tend to underestimate the amount of time/effort to resolve porting issues -- the key fact that there is often a 24 hour wait to see if fixes actually resolve issues.
Good point! Marcin, please put your code in CVS, so that you can fix the regression tests, and finish docs later! -- Janek Kozicki |
Hi Jeff,
As I've done in the past, I'll really encourage you *not* wait to finish the 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 the 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, Marcin
Hi Marcin, 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. ALSO: 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 line could they use the property_tree library to generate such command line as an string? Thanks Shams ----- Original Message ----- From: "Marcin Kalicinski" <kalita@poczta.onet.pl> Newsgroups: gmane.comp.lib.boost.devel 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 the 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 the 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, Marcin
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Marcin Kalicinski wrote:
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?
Please send your sourceforge id to the moderator list boost-owner@lists.boost.org and one of us will add you in. Jeff
Jeff Garland wrote:
Marcin Kalicinski wrote:
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?
Please send your sourceforge id to the moderator list boost-owner@lists.boost.org and one of us will add you in.
Before we get too far on: only reviewed and *accepted* libraries should be in Boost cvs. Work in progress should go in the sandbox: http://sourceforge.net/projects/boost-sandbox/ Or have I misunderstood the intent here? It happens often :-) John.
John Maddock wrote:
Jeff Garland wrote:
Marcin Kalicinski wrote:
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?
Please send your sourceforge id to the moderator list boost-owner@lists.boost.org and one of us will add you in.
Before we get too far on: only reviewed and *accepted* libraries should be in Boost cvs. Work in progress should go in the sandbox: http://sourceforge.net/projects/boost-sandbox/
Or have I misunderstood the intent here? It happens often :-)
Property Tree was accepted....somehow that didn't make the News on the front page, but it was recorded here: http://lists.boost.org/boost-announce/2006/05/0092.php Jeff
Jeff Garland wrote:
Property Tree was accepted....somehow that didn't make the News on the front page, but it was recorded here:
Oops, caught not paying attention, in that case lets get it in cvs :-) John.
participants (6)
-
Daniel Schlyder -
Janek Kozicki -
Jeff Garland -
John Maddock -
Marcin Kalicinski -
Shams