Re:JSON for Modern C++ version 3.10.0
by beached_whale on Thursday August 19, 2021 @12:25AM
(#28230310)
The C++11 is still common enough that if you want a large usage group it's the target. However, it's parsing to a DOM and doesn't use features like PMR, so the language features needed won't be more than std containers and stuff.
[ Parent
| on HN ]
Re:JSON for Modern C++ version 3.10.0
by quietbritishjim on Thursday August 19, 2021 @06:58AM
(#28232359)
I think it makes sense to target C++11. Just that you shouldn't then call the library "modern".
There is also a SAX parser.
But to be honest, I have not yet played around with PMR.
Re:JSON for Modern C++ version 3.10.0
by beached_whale on Thursday August 19, 2021 @08:50AM
(#28233172)
I know when I was benching JSON Link, I saw 30-50% increase in perf at the time when using better allocators and PMR can help a lot there with things like bump allocators.
Specially among the C+ community groups.
Re:JSON for Modern C++ version 3.10.0
by beached_whale on Thursday August 19, 2021 @01:34AM
(#28230676)
It is changing and I saw some survey’s showing 17 around 1/2 the shops. I know for my JSON library it wouldn’t be possible without C++ 17 so it’s a loss of eyes
Yeah, thing is how much C++17 is actually used beyond the language version.
For example, C++/WinRT is a C++17 library, yet plenty of samples use C style strings and vectors.
Re:JSON for Modern C++ version 3.10.0
by beached_whale on Friday August 20, 2021 @10:06PM
(#28253438)
I use a lot of core C++17 isms. They make some things doable and others clearer. But I think C++17 really helped a lot in generic programming in addition to the containers it introduced.