[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn_ver_check_list(): Why does it exist?

From: Max Bowsher <maxb_at_ukf.net>
Date: 2004-12-04 18:19:30 CET

I can't work out why we have svn_ver_check_list().

Unless I'm missing something, it appears to be redundant:

Majors: Major numbers are ensured equal, since our shared libraries always
feature the major version as part of the name.

Minors: If an application uses a function new in the version of subversion
it is compiled against, then the "same or newer minor" check will be
enforced by the OS dynamic loader. If not, then there is no reason to
enforce the check! Our compatibility rules tell us that any app should work
against any minor release which contains the required APIs.

Patches: Patch versions are *always* compatible, no checks required.

Unless I've missed something, we should remove all uses of
svn_ver_check_list() and deprecate it.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 4 18:21:02 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.