What boost needs is a generic tree container library that can include as utilities some of the functionality in the proposed property-tree library. Some references: * Tree Container Library http://www.codeproject.com/library/tree_container.asp The author plans to submit it to boost . This should combine with the current proposed library * tree.hh: an STL-like C++ tree class (GNU) http://www.aei.mpg.de/~peekas/tree/ This library is well regarded and widely used in many GNU projects If some of the STL gurus can compare both libraries we could contact the author to encourage it to submit it to boost or just change the license. A key functionality for the new library is being able to load an XML file in memory and provide an easy-to-use DOM-like interface. Regards Jose On 4/11/06, Klaus Nowikow <nowikow@decomsys.com> wrote:
David Abrahams <dave <at> boost-consulting.com> writes:
"Marcin Kalicinski" <kalita <at> poczta.onet.pl> writes:
Property tree library revision 5 (review version) is now in the boost vault. Documentation can be viewed online at http://kaalus.atspace.com/ptree
What is the rationale for using the word "property" here?
Why is this data structure not a more generic tree? It seems as though forcing the data on a tree node to be a specialization of basic_string is needlessly limiting.
That reminds me of Dave Handley's implementation of a composite pattern library, see http://aspn.activestate.com/ASPN/Mail/Message/2301865
Maybe it would be harder to implement all the file read/write functions with this one, though.
-- Klaus Nowikow
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost