Eric Gillespie <epg_at_pretzelnet.org> writes:
> Reimplementing all deprecated functions each time we rev it again
> is downright dangerous. We have NO TESTS of these rewritten
> functions. This is true even if we rewrite each one only once,
> leaving a chain of deprecated functions calling each other.
>
> One such rewritten deprecated function almost shipped in 1.5 in a
> completely non-working (segfault) state if I hadn't found it by
> accident (r31055). I wrote a test for it using the Python
> bindings, which is the easiest approach to unit testing.
> Subversion is mostly tested only in the way that svn(1) calls the
> APIs, and API use by anything else is strictly at own risk.
Note that some of our C test code continues to (deliberately) call
deprecated functions. But I think your point still stands; that's not
something we can depend on in general.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-02 19:28:29 CEST