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
Remove build date support in favor of semantic versioning #148
Comments
I made the changes and pushed this. Also reverted An alternative would be to use Forgot to mention in the comments that I cleaned up some strings while I was at it to avoid mentions of "experimental" and "this fork", etc., as we near 5.0.0. I'll leave this issue open for discussion re: what to return from |
If no one cares what I'll leave it open for a few more days and cross-post to the three lists... Oh, I suggest that we add a deprecated flag to |
@balthisar have never tried it myself but found this reference Will get around to trying it in MSVC and see what happens ;=))
|
There was an idea to mark this function deprecated, such that if used the developer would see a warning. But this was never implemented in a cross platform way. So for now revert to circa Jan 2015 when Jim added a build date to the version.txt file. And now both LIBTIDY_VERSION and RELEASE_DATE macros are established in CMakeLists.txt, and picked up in version.h. The idea is the date will now march forward with the version number, side by side in version.txt. Although have left tidy.c only emitting the version on the --version command. After this function has been marked deprecated for several release periods, only then should consideration be given to potentially removing it.
See Issue #190 for comments on why this reversion to continuing support for |
For now continuing support for both version and date, although console tidy continues to only show only the version. Maybe the date could now also be added. But no further comments for a few weeks so closing this for now... Feel free to re-open, or post a new issue. |
Remove build date support in favor of versioning.
The text was updated successfully, but these errors were encountered: