search for: __clang_svn_revision__

...t what do others think? > These proposed solutions only help distinguish between clang trunk and a clang release branch, but does not help to distinguish between today's trunk and a month from now trunk, which people using snapshots might care more about. What about adding a define like __clang_svn_revision__ instead? -Tom > > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >

...gt; These proposed solutions only help distinguish between clang trunk and > a clang release branch, but does not help to distinguish between today's > trunk and a month from now trunk, which people using snapshots might > care more about. > > > What about adding a define like __clang_svn_revision__ instead? Another option would be to have the -version output include the svn revision by default for dev builds.

I'd like to propose that trunk always have a version number which is in between versions used by the previous release branch, and before the versions used in the next release branch. Right now, trunk is sharing the 7.0.0 number, which will also be used by the next release 4 months from now. Since some people use and release snapshots of clang from trunk (e.g. the Android NDK), it'd be