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

Re: svn_ver_check_list(): Why does it exist?

From: Branko ─îibej <brane_at_xbc.nu>
Date: 2004-12-07 00:41:42 CET

Max Bowsher wrote:

> 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.

Which OS, and which dynamic loader? And which minor number? Please try
to think in slightly broader terms.

> 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.

No they don't. Read them again. Or rather, see how they define "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.

You've missed a great deal. Go look at the compatibility checking code
again, and see what it actually does.

-- Brane

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 7 00:42:13 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.