search for: xapian_major_version

...ION="\"$(PHP_MAJOR_VERSION)\"" \ version.rc - and here is the resource file I use (new file "version.rc" in win32): #include "winres.h" #include "xapian\version.h" #include "php_version.h" VS_VERSION_INFO VERSIONINFO FILEVERSION XAPIAN_MAJOR_VERSION,XAPIAN_MINOR_VERSION,XAPIAN_REVISION PRODUCTVERSION XAPIAN_MAJOR_VERSION,XAPIAN_MINOR_VERSION,XAPIAN_REVISION FILEFLAGSMASK 0x3fL #ifdef _DEBUG FILEFLAGS VS_FF_DEBUG #else FILEFLAGS 0x0L #endif FILEOS VOS__WINDOWS32 FILETYPE VFT_DLL BEGIN BLOCK "StringFileInfo" BEGIN...

...ssor checks to decide which function name to call if you really need to check the library version actually in use. These functions were added in 0.9.3, and deprecated in favour of names with "xapian_" removed in 0.9.6, so this code will work for any Xapian version from 0.9.3 onwards: #if XAPIAN_MAJOR_VERSION == 0 && XAPIAN_MINOR_VERSION == 9 && XAPIAN_REVISION < 6 string version_string = Xapian::xapian_version_string(); #else string version_string = Xapian::version_string(); #endif So I don't think there's a reason to keep these around longer than we would otherwise....

Olly and I have been discussing details of our policy for deprecating features, and we thought it would be useful to canvas users opinions on a particular aspect. From time to time, we remove features from the library (usually because we have a better replacement). To make life easier for users, we've been following a deprecation policy, so that users are given plenty of warning of