Re: svn commit: r15154 - in trunk: subversion/bindings/swig/ruby/libsvn_swig_ruby subversion/bindings/swig/ruby/svn subversion/bindings/swig/ruby/test tools/examples tools/hook-scripts

Hi,

In <df2177af05070504421758f16e@mail.gmail.com>
  "Re: svn commit: r15154 - in trunk: subversion/bindings/swig/ruby/libsvn_swig_ruby subversion/bindings/swig/ruby/svn subversion/bindings/swig/ruby/test tools/examples tools/hook-scripts" on Tue, 5 Jul 2005 07:42:58 -0400,
  David James <james82@gmail.com> wrote:

> I see you fixed this in r15257. Great! How do you deal with functions
> which allocate memory from pools, such svn_config_get_config? If a
> function allocates memory from a pool to create a variable, we must
> make sure that the pool exists as long as the variable does.

Ruby bindings keep pool reference in caller objects and
result objects. Those objects may be not allocated the pool
but the bindings can't check this. There are some wastes but
I think enough in this.

--
kou
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org