Open rh-m2 opened 1 year ago
In theory this can be done without harming performance when allow_comments=false. Or at least it will be no worse than how we currently support the C and C++ style comments.
Another workaround:
std::string
depython(std::string const &in)
{
static const auto reg = std::regex("^[ \t]*#.+(#\n|$)");
return std::regex_replace(in, reg, "");
}
auto val = json::parse(depython(json_text));
PLEASE DON'T FORGET TO "STAR" THIS REPOSITORY :)
When reporting a bug please include the following:
Version of Boost
1.81
Steps necessary to reproduce the problem
This JSON will be parsed by python's parser, but not by boost.json
All relevant compiler information
Any
Arguments for supporting this
I am writing a back testing and systematic trading engine. The engine is configured with JSON, picked up either off a config file or via a data bus such as RabbitMQ.
Some components of the system are written in C++ and some in Python. It would be useful to be able to add comments to config files that were parsed by both kinds of components.
Workaround:
But you know, yuk!