David James wrote:
>
> There's no official conventions for writing "deep copy" functions, but
> I'd like to make some: If a type is named "svn_foo_bar_t", the "deep
> copy" function should be called "svn_foo_bar_dup". Further, all deep
> copy functions should normally return the new object as a pointer, and
> accept the following two arguments:
> 1. A const pointer to the object you want to copy (e.g. const svn_foo_bar_t *)
> 2. The pool to use to make the deep copy
>
> These conventions make it easier for us to automatically generate code
> that uses the deep copy functions in the SWIG bindings. See r16398 for
> an example. Maybe we should document this in hacking.html?
+1. Please find a good place for it in hacking.html and add this.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 11 01:23:27 2005