Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of brane@wandisco.com designates
 74.125.82.53 as permitted sender)
Message-ID: <54CF9DEA.2090700@wandisco.com>
Date: Mon, 02 Feb 2015 16:55:22 +0100
From: =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@wandisco.com>
Organization: WANdisco
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: dev@subversion.apache.org
Subject: Re: svn commit: r1656488 - in /subversion/trunk/subversion:
 include/svn_client.h
 libsvn_client/client.h libsvn_client/ctx.c libsvn_client/ra.c
References: <20150202152417.2C85CAC0043@hades.apache.org>
 <CABw-3Yf+2WJQeiw07cVvV7WNAopwjQOPv8aceiFGaVm1SBBnFQ@mail.gmail.com>
In-Reply-To: 
 <CABw-3Yf+2WJQeiw07cVvV7WNAopwjQOPv8aceiFGaVm1SBBnFQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 02.02.2015 16:33, Ivan Zhakov wrote:
> On 2 February 2015 at 18:24,  <brane@apache.org> wrote:
>> Author: brane
>> Date: Mon Feb  2 15:24:16 2015
>> New Revision: 1656488
>>
>> URL: http://svn.apache.org/r1656488
>> Log:
>> Introduce a private libsvn_client context structure that stores
>> context information that should not be part of the public API.
>>
>> * subversion/include/svn_client.h
>>   (svn_client_ctx_t): Remove the 'progress' field, which should be private.
>>
>> * subversion/libsvn_client/client.h
>>   (client_ctx_t): New; the private context struct.
>>    Contains the equivalent of the 'progress' field.
> I suggest svn_client__private_ctx_t name for client_ctx_t structure: I
> think it less confusing name and follow our guidelines for library
> private identifiers.

This is not really a library private identifier. It is a type name
private to the library, so it's never exposed from a (static or dynamic)
library and therefore cannot cause name collisions at link time.

We use similar type and macro naming shortcuts in many places for this
kind of thing.

I'll probably add a "private_" prefix, though, to avoid confusion where
both context types are used in the same function.

-- Brane