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

Re: svn commit: r24648 - in trunk: . subversion/include subversion/include/private subversion/libsvn_client subversion/libsvn_fs_base subversion/libsvn_wc subversion/tests/libsvn_subr

From: Joe Swatosh <joe.swatosh_at_gmail.com>
Date: 2007-04-23 23:35:58 CEST

Hi Daniel,

On 4/23/07, Daniel Rall <dlr@collab.net> wrote:
> On Fri, 20 Apr 2007, Joe Swatosh wrote:
>
> > Hi Dan,
> >
> > On 4/20/07, Daniel Rall <dlr@collab.net> wrote:
> > >On Thu, 19 Apr 2007, Joe Swatosh wrote:
> > >
> > >> Hi Paul,
> > >>
> > >> On 4/18/07, pburba@tigris.org <pburba@tigris.org> wrote:

> > >>
> > >> Are the private functions intended to be available to the bindings
> > >> implementations or only to subversion itself? If the bindings are
> > >> supposed to be able to use them, we will probably have to create a
> > >> proxy for this?
> > >
> > >I think that the bindings should be able to use this routine
> > >internally. Exposing, or at least publicizing it, outside of
> > >Subversion is more dubious...
> > >
> >
> > Thanks Dan, it sounds like headers in the private directory should
> > have swig proxies
> > generated for them, too? If yes, I'll start trying to figure that out....
>
> I suppose. But, this makes the APIs easily accessible outside of
> Subversion, which is questionable. Because these APIs are private to
> Subversion, there's no guarantee that they won't change in the future
> (no API compat).
>

kou fixed the issue in the Ruby bindings in a different way. So until
we have a good
reason to pursue this, I'm now planning on leaving this alone.

--
Joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 23 23:36:08 2007

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.