Regarding the write_xml routine used with the boost Property
Tree, it evidently does not utilize the underlying RapidXML tool? Said
differently, is it true Property Tree relies on RapidXML for the reading step,
but not the writing step? I ask because I may be swapping Property Tree’s
dependence on RapidXML, for a Unicode
branch of pugiXML instead, so that I get free conversions to-and-from
UTF-16/UTF-8. But if Property Tree does not use the underlying XML parser
for the writing step, then I won’t get that free conversion when writing
back to disk.
As for the read_xml func, is it also true that “twice”
the memory is needed, because RapidXML will load a document into a DOM, and
then the Property Tree will allocate more memory to convert the DOM content
into its own format?
Brent Arias
Software Architect
Lumension Security™
Tel ~ (480) 444-1607
Fax ~ (480) 970-6323