Repository navigation
Using versioned namespaces #1539
Description
-
Describe the feature in as much detail as possible.
In huge environments libraries and binaries might be compiled in different times. As this library is header only it has no dynamic linked library so from an ldd command the user is not able to detect which json library version is used in its dependencies. Using several version of json library accidentally might cause linking issues when the same function in the same namespace have different implementations. My idea is: the implementation namespace would contain the library version and we create an alias to it (so all currently implemented code could be the same while several versions of jsons could be used in the same binary silently). -
Include sample usage where appropriate.
We build a so, a file with json version 3.4.0, but the binary is built by 3.6.0. -
possible implementation:
namespace nlohmannshould be changed to
namespace nlohmann_json_3_6_0and the last line of the header should be:
namespace nlohmann = nlohmann_json_3_6_0;
Activity
nlohmann commentedon Mar 22, 2019
Related #1394
nlohmann commentedon Mar 23, 2019
I had a brief look and this seems to be a lot of work... Any volunteers?
naszta commentedon Mar 23, 2019
I’m happy to do.
naszta commentedon Apr 2, 2019
Hopefully on weekend I'll have time to do it.
stale commentedon May 2, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.