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

Re: [PATCH][merge-tracking]Maintain Back Compatibility with 1.x.y

From: Daniel Rall <dlr_at_collab.net>
Date: 2006-11-21 08:33:23 CET

On Tue, 21 Nov 2006, Kamesh Jayachandran wrote:

> Malcolm Rowe wrote:
> >On Mon, Nov 20, 2006 at 02:07:24PM +0530, Kamesh Jayachandran wrote:
> >
> >>>The public RA API does not depend on the svn_ra__vtable_t structure in
> >>>the private ra_loader.h header file
> >>>
> >>It depends indirectly through 'svn_ra_session_t'->vtable.
> >
> >But svn_ra_session_t is an opaque structure that we only expose a
> >pointer to, so no external caller will ever have visibility of the
> >vtable member.
...
> we won't ensure backward compatibility between
> libsvn_ra_dav of 1.4.2 with libsvn_ra of '1.5.x'.
> Am I correct?

Yes.

> To make it even generic.
> Backward compatiblity is ensured only with libraries of the name
> 'libsvn_wordwithnounderscore' like 'libsvn_client, libsvn_diff,
> libsvn_ra, libsvn_subr, libsvn_delta, libsvn_fs, libsvn_repos, libsvn_wc'?

Not exactly. Backwards compatibiliy is necessary for our public APIs,
regardless of how the module that they're defined in is named. I
wouldn't bother bending over backwards to allow users to mix and match
different versions of our modules, which depend on each other's
internal APIs.

  • application/pgp-signature attachment: stored
Received on Tue Nov 21 08:34:48 2006

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.