Re: result_pool and scratch_pool

Are there any practical problems which are solved by a scratch pool and
a result pool?

Our old discipline was:

  * Pass a pool which is used for scratch and results.
  * If you're going to loop, use a subpool.
  * Be streamy (don't read whole files into memory).

So every scratch allocation should be constant. The memory usage from
this discipline is O(stack size), which is generally not all that large.

Passing around two pools is a lot of code noise. I wouldn't suggest
doing it unless it solves a real problem.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-07 17:35:26 CEST