RE: Hide internal data in svn_wc_entry_t struct
Sorry about top-posting.
> Do you mean use name "baton" or use baton syntax with "void *"?
void, because, introducing svn_wc_entry_private_t still leaves space for ABI revving, when we have svn_wc_entry_private2_t.
the word 'baton' because this would mean wc specific baton containing wc specific information... and the term is pretty well-known in svn-dev-land.
From: Ivan Zhakov [mailto:firstname.lastname@example.org]
Sent: Thu 12/28/2006 2:11 PM
To: Madan U S
Subject: Re: Hide internal data in svn_wc_entry_t struct
On 12/28/06, Madan U S <email@example.com> wrote:
> > -----Original Message-----
> > From: Ivan Zhakov [mailto:firstname.lastname@example.org]
> > Sent: Thu 12/28/2006 1:50 PM
> > To: svn-dev
> > Subject: Hide internal data in svn_wc_entry_t struct
> > Some data in svn_wc_entry_t is local and valuable only for libsvn_wc.
> > One of this exampe is new field keep_local which I've to introduce due
> > implementing svn rm --keep-local.
> > And I don't see reasons to publish such data and maintain it using ABI
> > policy, revv and etc.
> > So my idea is introduce private structure to store such data:
> > In include/svn_wc.h:
> > typedef struct svn_wc_entry_private_t;
> Sounds like a good candidate for a baton....
Do you mean use name "baton" or use baton syntax with "void *"?
Received on Thu Dec 28 09:57:44 2006
This is an archived mail posted to the Subversion Dev