parse xml file:

c++ code:

std::locale utf8Locale(std::locale(), new std::codecvt_utf8<wchar_t>());
std::wifstream f(*path);
f.imbue(utf8Locale);
wptree tree;
read_xml(f, tree);

xml file content:

<?xml version="1.0" encoding="UTF-8"?>
<data>
<content>你好&#128549;</content>
</data>

result is: "你好😥"

other info: boost property tree v 1.68.0 VS 2017 15.9.4 Windows 10 17763.195

Fixes missing placeholder includes to boost::bind.

boost/property_tree/json_parser/detail/parser.hpp(217): error: identifier "_1" is undefined
boost/property_tree/json_parser/detail/parser.hpp(520): error: identifier "_1" is undefined

Reported in https://svn.boost.org/trac/boost/ticket/12841

boost::property_tree can have nulls as keys. In particular, json read typically generates child nodes with null keys as part of array processing. Place a nonce (3cb6534e-d358-4705-9e74-fee06453661e) as a unique tag name for null keys in write_xml.

json_parser/detail/parser.hpp includes <boost/bind.hpp> which causes a deprecation warning with boost 1.73.0.

..\boost\boost/bind.hpp(41): note: The practice of declaring the Bind placeholders (_1, _2, ...)
in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using
namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to
retain the current behavior.

This could for example be resolved by using #include <boost/bind/bind.hpp> and adding a using namespace boost::placeholders in the methods that use boost::bind with _1, etc.

wchar_t is an unsigned on Arm, therefore a promotion is necessary here to correctly perform the comparison

More information about Armv8 types on https://developer.arm.com/documentation/den0024/a/Porting-to-A64/Data-types

Hi, I want to parse below JSON data and get the "netconf-clients" available. Can someone help me on how to do it.

('{"o-ran-dhcp:dhcp": {"interfaces": [{"interface": "mPlaneVlan295", "dhcpv4": ' '{"client-id": "53148/473966A.101/L1174115125", "dhcp-server-identifier": ''"192.168.100.1", "interface-mtu": 1500, "domain-name": "nokia.com", ' '"domain-name-servers": ["192.168.1.1", "192.168.1.2"], "default-gateways": ''["192.168.100.1"], **"netconf-clients": [{"client": "192.168.100.1", ''"optional-port": 4334}, {"client": "xyz.com", "optional-port": 4334}], '** '"ca-ra-servers": [{"servers": "192.168.100.1", "port-number": 99, ' '"ca-ra-path": "var/opt/z", "subject-name": "radio", "protocol": "HTTPS"}], ' '"segw": [{"gateways": "1.2.3.4"}], "local-ip": "192.168.100.3"}, "dhcpv6": ''{}}], "m-plane-dhcp": {"private-enterprise-num": 53148, "vendor-class-data": ' '"o-ran/No125"}}}')

Br, Neeraj

Warning when Boost 1.72 is built with GCC 7.5 with -Wsuggest-override added to cxxflags:

./boost/property_tree/detail/rapidxml.hpp:61:29: warning: ‘virtual const char* boost::property_tree::detail::rapidxml::parse_error::what() const’ can be marked override [-Wsuggest-override]

BOOST_OVERRIDE was introduced in https://github.com/boostorg/config/commit/ffe4e0f5a448578cce14e3eed0cf7163333a81d9.

It's currently not possible to efficiently move nodes between ptrees.

Context/discussion: https://stackoverflow.com/a/29563086/85371

This PR is a DRAFT. It is meant to sollicit interest and quick review (is the idea "sane"? I do not believe any invariants are at risk, but maybe the core maintainers see more).

If there's interest, I'll flesh it out in full.

Multi Index splice overloads: http://www.boost.org/doc/libs/release/libs/multi_index/doc/reference/seq_indices.html#list_operations

reviewer suggestion: Joaquín M López Muñoz

Though correct, the documentation is misleading about the name of the "<xmlattr>" tag, because most readers will assume that the "<" and ">" are there to denote that it's a tag and the actual name is "xmlattr" only. Save hundreds of programmers an hour of debugging by making it clear.

In the root CML, this moves the options/folders outside the BOOST_SUPERPROJECT_VERSION case. In tests/CML, it attaches the tests to the tests target, which will be the Boost-wide convention for building the test executables. They are still left attached to the all target as well, because I didn't know if that was relied upon. If not, the test executables should use EXCLUDE_FROM_ALL.

I created CMakeLists.txt on the root, test, and examples directories to make this library managed by CMake.

Installation

$ mkdir build && cd build
build/$ cmake ..
build/$ make
build/$ make install

Running Tests

$ mkdir build && cd build
build/$ cmake .. -DBUILD_TESTING=ON
build/$ make
build/$ make test

Running Examples

$ mkdir build && cd build
build/$ cmake .. -DBUILD_EXAMPLES=ON
build/$ make
build/$ make example-${EXAMPLE_NAME}

multi_index_container provide typename Allocator, but basic_ptree doesn't provide it. How i can use custom allocator for basic_ptree?

I already use custom allocator for key and values.

<boost/bind/placeholders.hpp> should be explicitly included here, because <boost/bind/bind.hpp> may not include it depending on whether BOOST_BIND_NO_PLACEHOLDERS is defined or not.

Here's the second clang-modules issue I found (with this and #99 addressed, I could build ptree_serialization as a submodule).

It refers to some archive/basic_archive details.

''' -- a/1.77.0/src/boost_1_77_0/boost/property_tree/ptree_serialization.hpp +++ b/1.77.0/src/boost_1_77_0/boost/property_tree/ptree_serialization.hpp @@ -10,8 +10,8 @@ #ifndef BOOST_PROPERTY_TREE_PTREE_SERIALIZATION_HPP_INCLUDED #define BOOST_PROPERTY_TREE_PTREE_SERIALIZATION_HPP_INCLUDED

+#include <boost/archive/basic_archive.hpp> #include <boost/property_tree/ptree.hpp>

#include <boost/serialization/nvp.hpp> #include <boost/serialization/collections_save_imp.hpp> #include <boost/serialization/detail/stack_constructor.hpp> '''

This was discovered when enabling clang implicit modules (and by implication will affect C++20 header-units). property_tree/detail/file_parser_error.hpp uses stringstream without #including , and therefore is not self contained. Fixed thusly:

--- c/1.77.0/src/boost_1_77_0/boost/property_tree/detail/file_parser_error.hpp
+++ w/1.77.0/src/boost_1_77_0/boost/property_tree/detail/file_parser_error.hpp
@@ -12,6 +12,7 @@
 
 #include <boost/property_tree/ptree.hpp>
 #include <string>
+#include <sstream>
 
 namespace boost { namespace property_tree
 {

We are facing a weird issue on Windows, where a file move operation is not atomic: It seems to copy the file and sometimes it produces files that start normally, but then end filled with NULL characters. It looks as if a buffer was prepared, possibly memory mapped and then never filled.

Unfortunately the property_tree ini parser parses such files in many cases. Would it be possible to throw an exception on NULL characters, possibly as an option? Other characters below ASCII 32 excluding CR, LF, TAB may possibly be refused as well.