Re: svn commit: r40417 - in trunk: . subversion/include subversion/include/private subversion/libsvn_client subversion/libsvn_subr subversion/libsvn_wc

On Mon, Nov 9, 2009 at 05:50, Branko Cibej <brane_at_xbc.nu> wrote:
> Bert Huijben wrote:
>> The extractor.py changes were reverted, which added the functions back to
>> the public dll api.. but the functions itself were not defined in release
>> mode.
>
> That is a correct change. We should *always* have all functions defined
> and available in libraries, regardless of whether they're "disabled" by
> some macro or not. This allows, e.g., a debug build of some file to link
> with release libraries and not freak out in the process.

Yeah. Bert and I talked about this. Keep the functions in the public
API, but keep them hidden like our other private APIs. This could
happen if third-party developers wanted to be sneaky and use our debug
functions for their code, but against release libraries.

Cheers,
-g

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415786
Received on 2009-11-09 14:55:24 CET