-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VERSION define(s) #948
Labels
solution: proposed fix
a fix for the issue has been proposed and waits for confirmation
Milestone
Comments
Related: #943 |
Ah didn't see that. |
I understand, and it is the second time within 3 days that someone is asking for this. I'll have a look. |
To illustrate, e.g.:
|
nlohmann
added a commit
that referenced
this issue
Jan 31, 2018
nlohmann
added
the
solution: proposed fix
a fix for the issue has been proposed and waits for confirmation
label
Jan 31, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be useful if there was a #define for the version of the package. This would make it easier to transition client code across breaking changes, e.g. the 3.x changes to operator<< and exception types.
Just something like
#define NLOHMANN_JSON_VERSION 30102 // v3.1.2
Some people prefer to use hex, and some split into separate VERSION_MAJOR/MINOR/PATCH, whatever you want.
The text was updated successfully, but these errors were encountered: